I just discovered your excellent product today, months after this particular thread, but wanted to write (better late…). You’ve probably used Caretta Software’s GUI Design Studio, (http://www.carettasoftware.com), and they tackle navigation links with connection arrows that go from component to component, loading various mockup pages as necessary. Their one crime is the mockups/prototypes have too high fidelity, although you can dumb it down a bit through the presentation settings. They allow you to use the mockup page files as “component elements” that you can drag into your main workflow starting point. For example, if you have 5 dialogs that can all be spawned from one main part of the application, you just drag each page (that resides in a project tree) to the main page so you can see all five dialogs with the starting page. Then you use the line links to connect the calling elements (buttons, tabs, etc.) to each componentized page. I’m sure there’s talk of this somewhere in your forum but I’m new and have only scratched the surface. What their approach buys you is a full view of the application prototype (especially useful for iPhone apps) on one page with the line connections showing the links.
Again, you’ve no doubt explored their application, but I just wanted to mention that approach seems to work really well.

I am really impressed with how you guys run the company, manage the content of the site, and I’m delighted with the end result in your desktop product! Where do I sign up?

Cheers,
Ben

As a product manager and business analyst, I focus on HOW something is going to be used FIRST before I design the interface (though the overlap is substantial). Enabling flow and demonstration capabilities allows me to use Balsamiq to quickly SHOW the process and options of experiences with pictures rather than requiring my client/users to read use cases or stories.

I actually think that exporting to PDF or PPT with linking embeded might serve your audience more than building more capabilities into a presentation mode.

You may find that the greater opportunity is in simplifying the creation of the user’s flow rather than enhancing the presentation area where there are already tools that do that for you. My entire goal in the beginning of a application design is to dialog about what the user wants to accomplish. Low fidelity mockups with easy flow definition is ideal.

Thanks for the great application!!!

[Peldi: hey Dave, we're working on it: http://www.getsatisfaction.com/balsamiq/topics/presentation_mode - scroll to the end]

I’d love your input!

Peldi

How about two seperate applications, one for sketching and one for the advanced stuff.

P.S. I’m currently reading Sketching the User Experience, so I recognized your sample application in the movie instantly.

For those who need to demo their mockups (and who doesn’t?), you might try a solution we’ve been very happy with — create a screencast of a typical walkthrough. I actually prefer this solution to letting the client just click around aimlessly, since I can both control the flow and narrate the experience.

We use Macs, and the Screenflow application does a great job of capturing, and then letting you edit, a Balsamiq walkthrough.

That said, and even appreciating your focus in simplicity, having a way to demo a mockup project to our clientes sending it by email would be great!

Have you thought of making a “player”? just a stripped down version of the desktop edition with only the “Full Screen Presentation” option?

Please… (!!!)

What would be better is multipage mockups and the ability to link to different pages. This crutch is just a crutch.

[Hi Nate, we are actively working on multi-page Projects right now]

Also, I would agree that this could be a good opportunity for a Pro version.

I have been working with other prototype tools … and it do become very complicated – because prototyping is complicated (often pretty damn close to developing).

Just my 2 cents