Thanks. I found this post for others who are looking:
http://android-developers.blogspot.com/2009/04/backward-compatibility-for-android.html Warren On Aug 2, 12:42 pm, TreKing <treking...@gmail.com> wrote: > 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
