That's a good point. I recently added ActionBarSherlock, which requires Android 2.1 or above, but a majority of my users were on Android 2.1+ anyhow and I added ABS in version 38 or 39. Can't think of anything else that would cause half my users not to be able to upgrade. I've pretty much had the same permissions since version 1.
On Tuesday, May 22, 2012 12:24:35 PM UTC-4, Ben Sandee wrote: > > On Tue, May 22, 2012 at 11:06 AM, FiltrSoft <kri...@gmail.com> wrote: > > 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. > > I'm not sure if you've already considered this, but it could be that > they are not eligible to upgrade. Make sure that you haven't > accidentally enabled a feature or requirement in your manifest that > would strand a large number of users at version 10 because of SDK > version or other feature requirements. > > Ben Sandee > tbsan...@orangebikelabs.com > -- 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
