3 ms·
I agree mostly with this, but I would emphasize that your first release must be usable. I've seen a few promising products get released too early by people pus
by freedomben 8y ago
I agree mostly with this, but I would emphasize that your first release must be usable. I've seen a few promising products get released too early by people pushing to "ship early, ship often," etc, only to crash and burn because they quickly developed a reputation for being buggy pieces of crap. Once you have a slate of bad reviews on an app store, it's difficult to fix.
- TravHatesMe 8y agoI agree. If users have a poor experience, they'll be less likely to try it again after you've polished it. I'm sure there's a balance between the two, but "if you're not embarrassed" is too strong of a statement (I suppose it's an exaggeration to send a message). Plus, embarrassment is subjective.
- happybuy 8y ago> Once you have a slate of bad reviews on an app store, it's difficult to fix. Not really. Take note of what the bad reviews say, fix the issues, release a new version and repeat. Once you've got to the point that you've resolved the majority of the problems noted, release a version in the App Store which resets all your ratings. If you keep going - from that point on - you should be getting better reviews and ratings which will make it a more popular app and these later reviews will eventually overwhelm the earlier lower ratings. Also once the app is actually objectively good, use SKStoreReviewController.requestReview to prompt for reviews from users to encourage more and more good ratings. It could be said that a poorly rated app is simply one which hasn't listened to feedback and focused on constant improvements.
- toast0 8y agoIf your reviews are that bad, and you've actually built something decent, you can just change the name, and get a clean slate (although depending on the app store, maybe just a new version number is good enough)