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 wrote:
> T
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 wrote:
> You may use minSdkVersion=3, and within the code, use reflection or
> ot
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 wrote:
> You may use minSdkVersion=3, and within the code, use reflection or
> other means to determ
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 de
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
5 matches
Mail list logo
