Did you know that the Flowchart aspect has multiple connector methods? These help you connect objects faster based on how they are connected.
The three connector modes are:
This method lets you connect two objects by clicking on the first object and then on the second object. Nothing is selected afterwards so you can create another connection by repeating the steps.
This method also lets you connect A and B by clicking on them in order. However, B remains selected after clicking B. This allows you to chain objects together in sequence. If you click C you will create a connection between B/C in addition to A/B.
This method once again lets you connect A to B by clicking on them sequentially. However, in this case A remains selected. If you click C you will create a connection between A/B and A/C.
Use these tools to connect flowcharts much more efficiently!
Many users of JumboLogic use Dropbox to store files for their projects since they can be easily accessed, edited, and uploaded from their staff’s computers. We’ve added a Dropbox aspect that will let you do this much easier.
- “Bookmark” a folder in your Dropbox account to provide quick access to necessary files for this project.
- Download from/Upload files to your Dropbox account
- Users must log in to Dropbox so it still provides security
The ContentCub aspect is now available on the JumboLogic AppMarket! This aspect helps streamline the process of collecting content (text, taglines, images, audio, videos, etc.) from your customers.
First, define the pages in your web/mobile app or pull them directly from an interface or sitemap aspect. Second, define what content is needed on each page. Third, add your customer as a collaborator and they will be able to upload content. Once complete you will be able to download all content in one consolidated zip file containing content divided into folders by page.
** Approve or reject content based on stated requirements.
** Save up to 5GB of data per licensed account
Available for $20/month
We added Interface Snapping a few weeks ago and we’re following that up with Interface Spanning. If you recall, Interface Snapping helps you snap objects to an edge or corner of its parent. Interface Spanning lets objects “span” across a parent such as the interface. This means that objects can size themselves automatically to the width or height (or both) of an interface.
The options for spanning are “Left” – from its current location to the Left border. “Right”. ”Left & Right” – from its current location to the Left border and Right border”. ”Top”, “Bottom”, and “Top & Bottom”.
If you use Spanning in conjunction with Snapping you can make more complex interfaces.
It sure does! We use JumboLogic every day and we find it really useful to be able to have multiple windows open at once. You can copy/paste between windows on interface and flowchart speeding up spec creation and editing. Keeping multiple windows open for reference purposes is great too since everything in an app is intertwined.
This is a pic of one of the workstations we use at our office. Neat huh?
One of the drawbacks of the interface aspect was that when you had pages that were different sizes it was tough to keep the footer on the bottom of the page or menus locked to the right side locked to the right.
We have added a feature called “Interface Snapping” that allows you to “snap” objects to its container The container is just the object’s parent.
This means you can snap objects to its parent or the page. This is useful when you need to place a footer at the bottom of your interfaces or need to “float” objects to the right side of your interface.
The tour video is finally up on the JumboLogic website! Check it out!
Our founder, Eric, gives you a tour of JumboLogic and how it can be used on a real project.
As we’ve been starting to market JumboLogic, we’ve gotten a few recurring questions and I wanted to share with you our thoughts on some of them.
Q: JumboLogic seems to limit me to designing rough interfaces without all the interface interaction and simulation abilities I seem to have with programs like Axure, iRise, etc.
A: Theoretically, if you create a good enough simulation of the interfaces then the customer and your team will fully understand how the interface will work. In practice this is never the case. To create a full simulation of your app before you build it is either not possible or will take so long that it is no longer worth it. Interface designers resort to “and it will do <this>… just use your imagination” and “trust us”. Some go so far as to quickly program an interface to demonstrate it to a client if they can’t see it. JumboLogic acknowledges this limitation and gives you what is really useful.
Q: Interfaces made in other programs are prettier!
A: Yep. This is a planning tool not a graphic design tool. We found that the graphics limitations of pretty much all interface layout tools hardly ever meets the need of graphic designers. Clients are left asking the question “Why does it look like that? I thought it would be better looking?” instead of concentrating on layout and function. Even if you tell clients that this is just a mockup they have a really hard time getting past how it looks. With the basic look of JumboLogic interface layouts customers are able to focus on whats important.
Q: Is JumboLogic just another interface layout tool?
A: Nope. What makes JumboLogic special is it gives you the ability to plan and design more than just the layouts. Layouts only tell you a sliver of the story – what it looks like. JumboLogic gives you tools like flowcharts, sitemaps, documents, slideshows, screenshots, image markup, etc. so you can also explain how users will use it, how it interacts with the real world, how it functions, how it evolves, how its laid out, etc. It’s also the only tool where you can add additional tools that you might need on a particular project via the JumboLogic AppMarket such as for programming planning, marketing planning, etc.
Q: Why say “definition” when JumboLogic lets you creates “requirements”?
A: We feel the term “Requirements” is too formal and tired. We want users to use JumboLogic to work together to define their apps. We like how it also means “to make clearer where its not” since this is 9 times out of 10 – a group effort.
Q: Why not use UML tools?
A: In short, UML tools are made for developers. JumboLogic is made for interaction with customers and the people on your team who don’t know UML but may or could provide valuable insight into a project – in other words – not just developers.
As part of our rebranding/redesign we got our marketing flyers redone to match our site design. We can’t wait to start handing these out. (It’ll make explaining what JumboLogic does a whole lot easier!)
This is our general flyer:
This is our sell sheet:
It’s all starting to come together. We’re excited!
You can drag and drop multiple files onto the project view now. If you drag it onto a folder you can quickly move several files into your project.
Once you drop the files a dialog will appear asking you how you want those files added. You can pick to add them as Files, Interfaces, or Webshots.
- JL Files – If you want to store them as basic files
- JL Interface – If you want to use them as interface backgrounds (great for editing/reorganizing existing interfaces)
- JL Webshots – If you want to mark the interface up with markers, highlighters, or notes (annotation)
We wanted to make it easier to edit and define changes to existing web/mobile applications.