review: Balsamiq Mockups

The short and sweet: Balsamiq Mockups offers a way for folks to quickly throw together wireframes – no experience necessary. You don’t need to be a wizard with Fireworks, for example, to quickly create and edit a wireframe in front of a client. It took me, as a ‘first time ever’ user of Balsamiq, about two hours to complete a wireframe I had sketched up on paper in a few minutes. My first Balsamiq WireframeThat’s a plus – I doubt anyone besides myself can read the wireframe I sketched by hand,hand sketched wireframe much less make heads or tails of it, while the one I made with Balsamiq is quite legible, while still lo-res such that it should impress upon the client that this is indeed a mockup not meant to communicate any sense of the look & feel of the application. My other thoughts for this particular wireframe were to do it either in FIreworks or in Flash Catalyst. The benefit of doing it in Catalyst was that the end result is actually an interactive motion wireframe. The downside of using Catalyst, though, was that (a) its still very much in the raw beta stage, and (b) the time to develop the interactivity in a way that would justify using Catalyst in the first place, would have also been much greater. For example, if you want to edit the text in a label, something you take for granted in most other applications that can be done simply by double-clicking on the text, in FC you must click on the label, and then edit the text in the property inspector rather than directly. This and other quirks are part of the beta nature of Catalyst – it just isn’t fully baked yet, which is to be expected for a beta. We’ve been waiting eagerly for Catalyst since it was first announced at MAX ‘07, and are still quite eager for a release version.

Back to the topic of Balsamiq – one feature I found I would have really liked would be the ability to create my own components – currently you can only use the ones that are given by Balsamiq – or even to have more control of the customization of the existing components. To their benefit, though, they do offer to make more if the use is general enough, if you just ask, and they say they update the application (which is an Adobe AIR app, btw) on a weekly basis. I think I would have also liked a freehand draw tool – I use a Wacom and would have liked the luxury of being able to write on top of the mockup as I wished. On the other hand, Balsamiq exports and saves to an XML format – so I can see the need to limit components to a pre-defined set of components. You can also re-use user defined components, which are really just Balsamiq Mockups themselves. The place to get those is Mockups to Go. I’m not sure if it was just the time I happened to be trying to access that site, but it seemed incredibly slow to me. Three of the ‘portlets’ on the right side of my wireframe are sourced from there…that definitely saved me a bit of time.

The best intro to Balsamiq I can recommend is to watch the intro video on their site, where they quickly make a mockup of iTunes. There is also an application called Napkee that lets you turn your Balsamiq Mockups into an interactive flex app – I guess that would kind of be on par with Catalyst, except you wouldn’t get the kind of round tripping you get between the CS4 suites and Catalyst. I didn’t play with Napkee but I get the impression it can’t export to the FXP format that is standard in Catalyst, Flex 4 and CS4.

Other features I would like to see implemented in Balsamiq:
-double-clicking on a group should let me edit the group. I guess that’s something I’m used to seeing from some of the Adobe apps such as Flash. A little irritating to me to find that doesn’t work here
-ugh! that purple color when I select a group – is there a way to customize the color prefs? It hurts my eyes…
-I would like the ability to zoom in and out of the mockup. There are no resolution settings, rulers, or guides. So you can imagine that a wireframe done quickly on a 30″ cinema display doesn’t always make for easy viewing on a 15″ MPB screen…or in an Adobe Connect Session, for that matter, where everyone’s got a different screen resolution
-’icon’ assets in Balsamiq can’t be resized by dragging resize handles – they can only be set to one of a few preset sizes (L, M, S, XS…). This really breaks when an icon is in a group – if you resize the group, the icon doesn’t resize with it.

Finally, I found this review of Balsamiq was also helpful. Coincidentally I reviewed iPlotz a while back here

review: Creating Visual Experiences with Flex 3.0 by Juan Sanchez & Andy McIntosh

The short version: Juan & Andy rock, Addison Wesley SUCKS.

Sometime after MAX ‘08 I decided to get Juan Sanchez’s flex book, Creating Visual Experiences with Flex 3.0. Juan’s background is in User Experience Design (UXD), so it was refreshing to get a flex book with some UXD perspective for a change – so many of the flex community are ex-Java guys, and no offense guys (some of our best Flex developers came from the Java world), but the Java perspective can get a bit, ahem, dry after a while. As far as the content of the book goes, Appendix A, Skinning and Styling Diagrams, by itself is valuable enough to make this book a must-have reference on any flex developer’s bookshelf. Juan mentioned somewhere (his blog?) that a lot of folks were requesting posters to be made of these diagrams and that he was in fact planning to make these available. (What I want to know is, can I get mine framed?)

The level and approach of this book is the epitome of what a lot of us wish the Flex docs from Adobe would be closer to. Having this book about thirty projects ago would really have made our lives easier in quite a few places. Then again, when has there ever been a comprehensive resource for an alpha product? That’s where we found ourselves when we made the transition from developing RIA’s in Flash to developing them in Flex. According to the team handling the Adobe documentation for Flex, they have been short-handed, and understandably so as flex developers are still in incredible demand yet very short supply. At least, that’s what they told me in ‘07; I have to wonder what the status of the situation is after the massive layoffs by Adobe in between MAX events. Regardless, even after having to learn a lot of these things the hard way in Flex, there was still quite a lot of good information in this book even for advanced developers. Animation, easing, skinning – just a few of the topics that are covered in depth.

Juan and Andy also took care to include lots of colorful images in their book, which they make heavy reference and use of. Ahem. The book is printed in BLACK AND WHITE. Not a drop of color anwhere, except for some sickening purple tint on the front cover. Almost every chapter, I found myself grimacing as the authors write, for example, “…in this case, red projects a negative relation…”. Red? Where? It seemed like they had no clue from the publisher that their book was going to be published in B&W, and, after asking Juan about it over Twitter, that was indeed confirmed – they only found out at the last minute. Oh, sure, they offer a free TRIAL subscription to the book on Safari when you buy the hard copy, and supposedly in the e-version on Safari the images are in color. If I wanted to read it online, I wouldn’t have bought the hard copy! I’ve done the Safari trial run before when I got a year subscription for purchasing Komodo for my perl development needs. Honestly the model of paying continuous rent for my books, especially in this case where I’ve already paid for the book in full, just doesn’t jive with me.

At the end of the day, the content of the book makes it a worthwhile buy, despite my feelings of being ripped off by the publisher. But this kind of experience definitely gives good argument for self publishing. I bought the book because of who the authors were – I would have still bought it, at the same price or even more, had they self-published….
With all the media coverage on the downfall of the newspaper industry, and the publishing industry in general, I feel companies like Blurb are well positioned while companies like Addison Wesley are doomed to failure as long as their only concern seems to be maximizing their profit margin whilst ignoring the needs of their consumers.

update: According to sources at Adobe, they’ve been having issues with the MXNA feed aggregator not automatically updating feeds. This update is a test to see if updating the blog entry is enough to force an update to MXNA using the ping URL mechanism…
And, apparently using the ping URL works.

Flasher Magazine issue #1

Lee Brimelow released the first issue of Flasher Magazine, a video magazine focused on the Flash Platform. Interviews include Ryan Stewart on Flash Catalyst and a ‘making of’ with tips on making your on video tutorials at the end. Check it out online or download it to your iPhone for your commute…