Programmers don’t use launch-fast-and-iterate out of laziness. They use it because it yields the best results. By obstructing that process, Apple is making them do bad work, and programmers hate that as much as Apple would.
Programmers don’t use launch-fast-and-iterate out of laziness. They use it because it yields the best results. By obstructing that process, Apple is making them do bad work, and programmers hate that as much as Apple would.
Launch fast and iterate... Whilst I agree that with information delivery systems (eg - websites) it's worth the pain of a half-finished product if it gets the content out, I think this ideology is a disaster for productivity apps that expect the user to pay for them.
Adobe are the prime example of this. Would there be so many blogs and user-groups like adobegripes.com if they actually bothered to carry out a decent QA process before launch? Or how about Firefox's constant updates every time you fire it up?
Quality control is what sets Apple products apart and allows Steve to take his 60% profit margins. It's also why users *like* Apple products. Don't expect them to set aside their entire design philosophy so that you can rush your half-finished, two-dollar Twitter app to market a couple of weeks before it's ready.
MarkH - 20th November 2009 11:47 - #