Nick Brawn launched his microISV product, Shinobi Scanner, last week for the Mac OS, and already he’s passing on info you can use in your company:

  • Cut, cut, cut to get 1.0 out the door: If it isn’t essential, leave it out.
  • Don’t call it 1.0 Beta if you’re going to release 1.1 next. Just call it 1.0.
  • Everybody loves screenshots: My screenshots page has the most hits so far.
  • Don’t be afraid of getting feedback. Be afraid of getting NO feedback.
  • Figure out the biggest point-of-pain and document it.

Nick’s off to a great start – and I’m keeping my eye on him because he’s good good information to share at his blog.

1 Comment

  1. Thanks for the comments Bob.
    To be honest, what I’ve said in that article isn’t really new or original. Over the years I’ve been able to learn from a lot of great resources, most of which are freely available.
    These resources included
    – MicroISV – Vision To Reality (just realised this is your book!)
    – Business of Software (Eric Sink’s book on ISVs)
    – Getting Real (37 Signals development mantra, read it free on their website)
    – Founders at Work (interviews with developers behind things like Flickr,, Hotmail)
    – E-Myth Revisited (talks about the different roles you have to perform when starting and running your own business)
    – The Business of Software forums over at
    Mailing Lists:
    – Mac Software Business (MacSB) mailing list
    – Business 2.0
    – Entrepreneur
    – Fast Company
    – Fortune
    Business-ish Podcasts
    – CocoaRadio (Mac-specific, several interviews with mac developers)
    – PomCast English version (Apple-specific, several interviews with mac developers)
    Too many to list here. I track about 280 news feeds with Bloglines. I have 27 feeds in my business, startup and marketing categories.
    Probably one of the biggest things that made me want to learn Cocoa and write Mac-specific apps was Wil Shipley’s WWDC 2005 presentation (slides and podcast available at
    Even if you’re not developing for the Mac, there’s some good stuff in there about making the jump from full-time worker to independent developer that’s worth a read.

Write A Comment