Yea, I think I was a little overzealous with my upgrades (hence the 40 versions), because I would find a bug and want it fixed as soon as possible. Also, and this might not be the best way to think about it, I tend to use the Play Store as a "beta" test, in that I will upload more version to the Play Store because there is no approval process, then when I feel it's stable, send it to Amazon's App Store. It's hard to balance wanting to fix issues/annoying the users.
On Tuesday, May 22, 2012 11:58:14 AM UTC-4, John Coryat wrote: > > In my experience, users upgrade quickly to the latest release. Within a > week of our last release, more than 2/3rds of the active users had updated. > Then there are those who never upgrade. 1/10th of our users are still many > versions behind. > > Again, from my experience, if you offer an upgrade that contains useful > features and not just a tiny tweak, they are more likely to upgrade. Also, > if you continuously bother the users with upgrades, most likely they will > ignore them and stick with what they have. That's just typical human > behavior. > > My best advice: Keep upgrades to a minimum, not more than once a month or > two and make them solid, tested and contain at least one feature that is > useful to the average user. > > -John Coryat -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
