Re: [android-developers] Best practice for changing min SDK
On Wednesday, March 16, 2011 2:43:16 AM UTC, Robert Massaioli wrote: everything below v7 of the SDK is only about ten percent of the market which I think means that app developers will ditch those platforms in the future. (If not right now) I don't know about you, but I'm disinclined to unilaterally chop 10% off my sales. After the recent Market ranking shenanigans, they're shaky enough as it is. String -- 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
Re: [android-developers] Best practice for changing min SDK
Actually I made that comment a little flippantly; 10% still translates to a whole bunch of users when you are talking about an OS like Android. I have changed my mind and I will suffer a little bit of that Backwards Compatibility pain in order to cater for every user. -- 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
Re: [android-developers] Best practice for changing min SDK
Use reflection or check the build version to determine if you can use newer APIs. If I simply update the application with a new min SDK version, will 1.5 and 1.6 users be prompted to uninstall? Or will they just not see the update? I assume they will not see the update. There's no reason to do this though. Just out of interest though does anybody know what would happen if you just did this anyway? What happens when you bump the min SDK version up? Thanks, Robert -- 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
Re: [android-developers] Best practice for changing min SDK
On Tue, Mar 15, 2011 at 7:15 PM, Robert Massaioli robertmassai...@gmail.com wrote: Just out of interest though does anybody know what would happen if you just did this anyway? What happens when you bump the min SDK version up? AFAIK, your app disappears from the Market for those people that don't have the right OS version, though they keep the app. They cannot update and if they uninstall, they cannot redownload the app. Tread carefully. - TreKing http://sites.google.com/site/rezmobileapps/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 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
Re: [android-developers] Best practice for changing min SDK
Thanks for the response. That makes sense, in that case I was considering releasing my app so that it supported version 3 of the SDK because that would be easy to do, however I really want the android.accounts package so maybe I will just make the min SDK level be 5 and ignore those on old phones. (And then I don't have to do that backwards compatibility reflection mess to get the android.accounts package) They only make up a really small segment of the market anyway: http://developer.android.com/resources/dashboard/platform-versions.html Thanks, Robert -- 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
Re: [android-developers] Best practice for changing min SDK
On Tue, Mar 15, 2011 at 8:03 PM, Robert Massaioli robertmassai...@gmail.com wrote: They only make up a really small segment of the market anyway: http://developer.android.com/resources/dashboard/platform-versions.html That says 3.0%. The new Developer Console stats say 5.1%. Personally, I wouldn't trust either since they come from the Market app which has proven to be completely unreliable in reporting these statistics. Add your own analytics if you can and base your decision on that. - TreKing http://sites.google.com/site/rezmobileapps/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 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
Re: [android-developers] Best practice for changing min SDK
Well that is annoying, cannot even trust the statistics pages. Now I actually have to debate what to do. Not as fun as I was planning. Ah well, I guess that is the price that people pay for newer and better versions of Android. Though Google really needs to get ontop of those statistics then; I hope they are working on that now. Thanks for letting me know though. Actually...can you please post the statistics that the developer console gives you for device distribution? I don't have an account yet or an app online and I would really appreciate it. Thanks again, Robert -- 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
Re: [android-developers] Best practice for changing min SDK
On Tue, Mar 15, 2011 at 8:34 PM, Robert Massaioli robertmassai...@gmail.com wrote: Actually...can you please post the statistics that the developer console gives you for device distribution? First value is from the console, second from the chart linked, blanks are not available. 2.1 is the only one that's even remotely close. Android 3.0 0.2% Android 2.257.1% 61.3% Android 2.129.3% 29.0% Android 1.67.0% 4.8% Android 1.55.1% 3.0% Android 2.3.3 0.6% 1.0% Android 2.30.2% 0.7% Android 2.0.1 0.1% Android 1.10.1% Android 1.00.1% Android 2.00.0% - TreKing http://sites.google.com/site/rezmobileapps/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 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
Re: [android-developers] Best practice for changing min SDK
Thankyou, these are really useful statistics though it is really confusing that they tell different stories. However it does say that everything below v7 of the SDK is only about ten percent of the market which I think means that app developers will ditch those platforms in the future. (If not right now) -- 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
Re: [android-developers] Best practice for changing min SDK
On Mon, Aug 2, 2010 at 12:23 PM, Warren warrenba...@gmail.com wrote: I want to update the apps to take advantage of some of the newer features offered in Android 2.0 and greater. What is the best way forward so I don't break things for my current 1.5 and 1.6 users? Use reflection or check the build version to determine if you can use newer APIs. If I simply update the application with a new min SDK version, will 1.5 and 1.6 users be prompted to uninstall? Or will they just not see the update? I assume they will not see the update. There's no reason to do this though. What about future development that I want to apply for everyone, say a bugfix. Will I have painted myself into a corner? Not if you do it correctly. Another solution would be to fork and create a new app for 2.0 users, but that is undesirable for several reasons. Yeah, don't do that. This must be a somewhat common problem. Have you seen any good ways to handle it? Repeat: use reflection or check the build version to determine if you can use newer APIs. There's a blog post on this subject. Go find it =) - TreKing http://sites.google.com/site/rezmobileapps/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 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
