>> I know what you mean. Until now, every semi-major released I've made >> (including a few weeks of work) has broken something significant for some users, requiring one or two point releases within 48h. Users are absolutely merciless with regressions.
You might consider creating a "beta" release version of your app. That's what we do. Before releasing a major update (about once a month) we post the beta to the market and ask for comments. If there's a problem, we'll know within a day or two and can fix it easily. People are a lot more forgiving of a problem when the app is a beta than a production app. Both the beta and production app can reside together (different package names) so there's little risk to the user if a problem does arise. On average, we get between 1000 and 5000 beta testers so by the time the beta goes to production, it's pretty bullet proof. -John Coryat -- You received this message because you are subscribed to the Google Groups "Android Discuss" group. To view this discussion on the web visit https://groups.google.com/d/msg/android-discuss/-/2Ngod_O12sQJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/android-discuss?hl=en.
