I've been tempted to drop 1.5, partly because it tends to be installed on low-end devices where people will not have a very good experience of my app, but recently my percentage of 1.5 users has gone up instead of down on some apps.
There's a big difference between dropping (loyal) 1.5 users and never having them in the first place, so for new apps my default assumption is I will target 1.6+ or even 2.1+. SJ On Mon, Jan 17, 2011 at 8:52 AM, TreKing <[email protected]> wrote: > On Mon, Jan 17, 2011 at 7:07 AM, String <[email protected]> > wrote: >> >> For my own apps, I don't have a problem supporting 1.5, and I figure that >> an extra 5% is nothing to sneeze at. But then, I've yet to run into anything >> that was really problematic for me to support on 1.5. Some of the resource >> handling is kind of annoying, but not really a big deal. >> If I had some core feature that I just couldn't make backward-compatible, >> then yes, I'd drop 1.5 too. But probably not until then, or until the >> install percentage drops a few more points. > > This. (Thanks for writing my post for me :-) ) > > ------------------------------------------------------------------------------------------------- > TreKing - Chicago transit tracking app for Android-powered devices > > -- > You received this message because you are subscribed to the Google > Groups "Android Developers" group. > 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-developers?hl=en -- You received this message because you are subscribed to the Google Groups "Android Developers" group. 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-developers?hl=en
