Notes on u-ISV

From Mac Software Business podcast “MacSB (001): Getting Started as a Mac Indie Developer”

  • Copy: Adding features write description for later cut and paste
  • Licensing
  • Payment processing: paypal, ecellerate
  • Marketing
  • Sparkle (updates)
  • Forums, email lists
  • Help book
  • Support hours
  • Bug database (omni-outliner, trac, fogbug)
  • Lost registration codes
  • Source control


  • Experimenting in code base to be shipped (one proj in Xcode)
  • Don’t be stingy about free licenses
  • Release


  • Put it up on Version Tracker, MacUpdate.
  • Blogs helped
  • Google add words (waste of money)
  • Press releases good
  • Apple’s download site

From podcast “Mac Software Business: MacSB (008): Becoming a Micro-ISV” which is an interview with Bob Walsh

  • You have to work on something you’d like to work on for the next three years
  • You may not be an expert in the area but remember you’ll be working with
    people in the area so you better like those people!
  • Blogging is the simplest and most effective way to connect to your market and
    even just improve your professional career.

The downside of a u-ISV

Here’s an article that’s closer to the truth of doing a u-ISV:
The Software Product Myth

In our completely un-contrived scenario you’re now making $2500/month from your product, which doesn’t allow you to quit your day job. So you work 8-10 hours during the day writing code for someone else, and come home each night to a slow but steady stream of support emails. And the worst part is that if you’ve built your software right the majority of the issues will not be problems with your product, but degraded OS installations, crazy configurations, a customer who doesn’t know how to double-click, etc&