3 ms·

I think these kinds of posts are a bit deceptive: "You can keep your day job. Just two months of nights and weekends. Then launch it. Maybe it’s not perfect ye

I think these kinds of posts are a bit deceptive: "You can keep your day job. Just two months of nights and weekends. Then launch it. Maybe it’s not perfect yet. But get it out there." I mean I'm all for releasing early and often, but it actually does take a lot of work to make a good application. From the Tapbots guys themselves: "We are going to write simple but incredibly polished applications that are created specifically for the iPhone/Touch devices. Two guys, lot’s of passion and a lot of hard work..." How do you reconcile this? These guys want to spend a lot of up-front time building polished apps whereas the 37signals guys are saying get something out there even if it's not perfect. Seems like a contradiction to me.

mileszs 18y ago
In defense of 'release early and often', the 'often' part is more difficult (from what I understand) on the iPhone. Each update must go through the approval process. That takes time -- time during which you are getting no feedback about the updates you've made. "Release early and often" is a lot easier when you're talking about a web app on server that you control. I do agree that the 37s post seems contradictory in light of that.
- tophat02 18y ago
  It's actually not that bad. I updated my little game "Recall" coughshameless plugcough and it only took a few days from submitting the new binary to getting it pushed through.