I can see this idea causing a world of confusion for users. Users shouldn't have to try and work out why, when they get your app, sometimes they get an old version which may have more bugs and other differences. Most user probably couldn't tell you their OS version number, and almost all of them don't really care.
So you have a sensible choice; Support older devices or make your app unavailable to them, and, from a users perspective (which is the only really important one), that makes a lot more sense. Al. -- * Looking for Android Apps? - Try http://andappstore.com/ * ====== Funky Android Limited is registered in England & Wales with the company number 6741909. The views expressed in this email are those of the author and not necessarily those of Funky Android Limited, it's associates, or it's subsidiaries. On 30 Nov 2009, at 07:02, Jeff wrote: > Unfortunately, you will need to write some special code for backwards > compatibility if you are using features that are only available in > Android 1.6. > > http://android-developers.blogspot.com/2009/04/backward-compatibility-for-android.html > > I have submitted an Android Market enhancement request. The Android > Market should allow the previous version of an app to remain in > the market so that Android 1.5 devices can still purchase the older > version > until these devices are upgraded. This would make it easier for the > dev so they don't need to write special code to handle backwards > compatibility. > > If you agree, please vote for the issue: > > http://code.google.com/p/android/issues/detail?id=4851 > > Jeff > http://www.trackaroo.com > > > On Nov 28, 1:47 pm, snctln <[email protected]> wrote: >> Hello all, I am sorry if this has been asked before, I haven't been >> very active on these boards in the last 6 months or so. >> >> A few months ago I was contacted by a phone manufacturer urging me to >> update my applicaitons to use the Android 1.6 sdk so that QVGA and >> WVGA devices could properly use my existing applciaitons. I did so >> and was able to test them perfectly fine on a QVGA device, however now >> that there are phones here in the U.S. that use 1.5, 1.6, and 2.0 it >> appears that my applications made with sdk 1.6 are not usable on 1.5 >> devices. >> >> I have experienced a very nice surge in sales since the droid has come >> out, but I now know that I am losing a lot of opportunity because my >> applications are not available to the 1.5 users (sprint hero, droid >> eris...) >> >> What is the best practice for supporting all of these devices? Do I >> have to choose between an apk that supports 1.6 and 2.0, and an apk >> that only supports 1.5? This just seems like bad planning if that is >> the case. >> >> snctlnwww.snctln.com > > -- > > You received this message because you are subscribed to the Google Groups > "Android Discuss" 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-discuss?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Android Discuss" 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-discuss?hl=en.
