[android-developers] Re: Be Careful of Upgrading App with New SDK Version
I think you have to manage yourself different editions of your app in the market. jeffro a écrit : I thought I would just post this to let other devs know about this issue. You should think carefully before posting a new version of your app that uses new features from Android 1.6 or Android 2.0. I have released a new app version that takes advantage of new Android 1.6 features. Because of this I have set android:minSdkVersion=4. This means now that devices that are still running Android 1.5 (HTC Hero and the upcoming Samsung Behold II) do not see my app at all. Ideally, the Android Market should allow the previous version of my app to remain in the market so that Android 1.5 devices can still purchase the older version until these devices are upgraded. I guess this is some of the device fragmentation issues folks are talking about. If someone knows a workaround, please post. -- 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
[android-developers] Re: Be Careful of Upgrading App with New SDK Version
You may use minSdkVersion=3, and within the code, use reflection or other means to determine the capabilities of the device, and use only supported API on the device. Check the android blog related post (http://android-developers.blogspot.com/2009/04/backward-compatibility- for-android.html) for details. This mean extra works, and it seems the only way to go. -- 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] Re: Be Careful of Upgrading App with New SDK Version
Yes, exactly. This fat binary method is the simplest to maintain as well because you can keep just one codebase. SoftwareForMe.com Makers of PhoneMyPC On Mon, Nov 16, 2009 at 10:19 PM, siuying siu.y...@gmail.com wrote: You may use minSdkVersion=3, and within the code, use reflection or other means to determine the capabilities of the device, and use only supported API on the device. Check the android blog related post (http://android-developers.blogspot.com/2009/04/backward-compatibility- for-android.html) for details. This mean extra works, and it seems the only way to go. -- 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.comandroid-developers%2bunsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -- Warm regards, The PhoneMyPC Team -- 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
[android-developers] Re: Be Careful of Upgrading App with New SDK Version
Thanks for posting that. Man, that's ugly. The best solution would be for Android Market to support multiple app version rather than having the dev add all this extra inefficient code. On Nov 16, 10:19 pm, siuying siu.y...@gmail.com wrote: You may use minSdkVersion=3, and within the code, use reflection or other means to determine the capabilities of the device, and use only supported API on the device. Check the android blog related post (http://android-developers.blogspot.com/2009/04/backward-compatibility- for-android.html) for details. This mean extra works, and it seems the only way to go. -- 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
[android-developers] Re: Be Careful of Upgrading App with New SDK Version
I just submitted an issue for this so that the market can support multiple versions of an app in order to support multiple SDK versions. If you agree that this is a better solution, please vote for it: http://code.google.com/p/android/issues/detail?id=4851 On Nov 16, 11:13 pm, jeffro j...@trackaroo.com wrote: Thanks for posting that. Man, that's ugly. The best solution would be for Android Market to support multiple app version rather than having the dev add all this extra inefficient code. On Nov 16, 10:19 pm, siuying siu.y...@gmail.com wrote: You may use minSdkVersion=3, and within the code, use reflection or other means to determine the capabilities of the device, and use only supported API on the device. Check the android blog related post (http://android-developers.blogspot.com/2009/04/backward-compatibility- for-android.html) for details. This mean extra works, and it seems the only way to go. -- 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
