Wireframing and the Reformed Cowboy Coder

Wireframing – sketching out the interface of your software with a focus on what it does rather than how it looks – was something I used to avoid.

I figured I’d end up laying out the interface in my programming IDE anyway, so why make extra work for myself? Just skip the wireframes and go straight to the IDE.

Besides, weren’t wireframes only used by teams in order to collaborate on design? I was a one-person company when I created HomeSite, TopStyle and FeedDemon, so wireframes seemed pointless.

But I was recently tasked with designing the next version of Glassboard, and I’m not the only one working on that so wireframes suddenly made sense.

And you know what? I should’ve relied on wireframes all along.

Sure, it’s extra work. And it can be pretty tiresome, too. It took me a lot longer to wireframe the app than I thought it would.

But once I was done, seeing an overview of every screen turned out to be enormously helpful. I better understand the relationships between those screens than I would have if I stuck with my "cowboy coder" ways and designed in the IDE.

Plus, writing out the purpose of every major area helped me clarify the UI and UX. I ended up re-thinking a lot of initial design decisions after I had trouble explaining them.

So consider me a reformed cowboy coder. I was wrong to think that only teams need to wireframe their software. The primary benefits I got from wireframing would’ve helped me even when I developed alone.

PS: I’ll probably be asked which wireframing tool I use, so I’ll say here that after trying a number of tools I chose Balsamiq Mockups. I like how its "lo-fi" approach reinforces the idea that you’re sketching out your design rather than deciding every last detail.

3 thoughts on “Wireframing and the Reformed Cowboy Coder

  1. Great read – concise but the message is very important. I believe in this message so much so that I’ve spent the last year building this: http://www.fluidui.com – next time your putting a mobile wireframe together, I urge you to give it a shot. Fast, simple and you can test on mobile with a click – I’d be honoured to hear your thoughts about it.
    Congratulations on your revelation!

  2. New name for the old storyboards, used from our beginning. Up-front project investment not only considerably minimizes clerk-typist coding drudgery but amazingly eases maintenance.

  3. An interesting story.
    I’ve just posted the tough question in the disucssion forums. Where and when will there be an updated, current version of FeedDemon?
    I look for an solid update on this the future status of FeedDemon.

Comments are closed.