I think this is less important on the web than native. Iterative releases feel natural on the web. If something solves a real problem I'll use it while they work out design kinks.
I completely agree, one of the reasons that we've been reluctant to release is that we've been developing a native app. Considering how long it takes to push a bug fix, with Apple approving and all, you can expect 4 days of downtime if you really screw up.
If you compare that with web, as many pointed out my article had a lot of spelling errors but that was easily corrected.
The real challenge is testing your assumptions without ever releasing an app or website :)
