I'm developing one android application which needs to support Android
OS 1.5, 1.6, and 2.0.
I've three different .apk files for all three SDK.
How can i upload three different .apk files on Android Market Place
for single application?
I would like to have all 3 versions available under one application
name. is this possible ?
> I've three different .apk files for all three SDK.
You should probably be using the latest SDK with your minSDK set to 3 (for
1.5) and using reflection to do things that are different across the API
levels.
How can i upload three different .apk files on Android Market Place for
> single application?
They all have to have a different package name, which means you would have
to make (and maintain) 3 copies of your source code. You probably don't want
to do this.
> I would like to have all 3 versions available under one application name.
> is this possible ?
Technically, yes. They can all have the same name via the "label" attribute
in your manifest, and they can appear with the same name in the Market (you
set this in the Developer Console). But, again, they have to have different
package names.
I would highly recommend you look through the blog posts for the one about
targeting different platform versions and seriously rethink publishing and
maintaining 3 different versions of the same app for each SDK.
What happens when 2.1 comes out? 2.2? 3.0? 43.67? Are you going to keep
making a new version of your app for each new version that comes out?
--------------------------------------------------------------------------- ----------------------
TreKing - Chicago transit tracking app for Android-powered devices
http://sites.google.com/site/rezmobileapps/treking
On Wed, Dec 16, 2009 at 2:11 AM, lk <vaish.alo...@gmail.com> wrote:
> Hi,
> I'm developing one android application which needs to support Android
> OS 1.5, 1.6, and 2.0.
> I've three different .apk files for all three SDK.
> How can i upload three different .apk files on Android Market Place
> for single application?
> I would like to have all 3 versions available under one application
> name. is this possible ?
> So, users with any SDK can use my application.
> Thanks.
> --
> 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+unsubscribe@googlegroups.com<android-developers%2Bunsubs cribe@googlegroups.com>
> For more options, visit this group at
> http://groups.google.com/group/android-developers?hl=en
> > I've three different .apk files for all three SDK.
> You should probably be using the latest SDK with your minSDK set to 3 (for > 1.5) and using reflection to do things that are different across the API > levels.
> How can i upload three different .apk files on Android Market Place for
> > single application?
> They all have to have a different package name, which means you would have > to make (and maintain) 3 copies of your source code. You probably don't want > to do this.
> > I would like to have all 3 versions available under one application name. > > is this possible ?
> Technically, yes. They can all have the same name via the "label" attribute > in your manifest, and they can appear with the same name in the Market (you > set this in the Developer Console). But, again, they have to have different > package names.
> I would highly recommend you look through the blog posts for the one about > targeting different platform versions and seriously rethink publishing and > maintaining 3 different versions of the same app for each SDK.
> What happens when 2.1 comes out? 2.2? 3.0? 43.67? Are you going to keep > making a new version of your app for each new version that comes out?
> --------------------------------------------------------------------------- ---------------------- > TreKing - Chicago transit tracking app for Android-powered deviceshttp://sites.google.com/site/rezmobileapps/treking
> On Wed, Dec 16, 2009 at 2:11 AM, lk <vaish.alo...@gmail.com> wrote: > > Hi,
> > I'm developing one android application which needs to support Android > > OS 1.5, 1.6, and 2.0.
> > I've three different .apk files for all three SDK.
> > How can i upload three different .apk files on Android Market Place > > for single application? > > I would like to have all 3 versions available under one application > > name. is this possible ?
> > So, users with any SDK can use my application.
> > Thanks.
> > -- > > 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+unsubscribe@googlegroups.com<android-developers%2Bunsubs cribe@googlegroups.com> > > For more options, visit this group at > >http://groups.google.com/group/android-developers?hl=en
An Android developer has to develop the habit of untraining management that is used to J2ME. If you release multiple different APKs you technically can fork your codebase, into different packages, to target different firmware. But you don't want to compete with yourself for market listings, you don't want to fork your code, you don't want to have to maintain different branches.
Mind you, I don't want to use reflection, it frightens me a bit, and it's annoyed me and made my app harder to debug every time I've used it. Eventually though we'll really want to use a feature not in 1.5.
I'm curious, what happens if you release an application that requires Android 1.5 or higher on the market, and then you update it with a version that requires 1.6 or higher? Will 1.5 users simply no longer be able to download the application? What is their user experience?
Thanks, -MK
On Dec 18, 2:42 am, lk <vaish.alo...@gmail.com> wrote:
> Thanks for your reply. I was not aware of reflection.Now I am > learning about reflection.I will seriously follow your > recommendations.
> thanks > Alok
> On Dec 17, 12:20 am, TreKing <treking...@gmail.com> wrote:
> > > I've three different .apk files for all three SDK.
> > You should probably be using the latest SDK with your minSDK set to 3 (for > > 1.5) and using reflection to do things that are different across the API > > levels.
> > How can i upload three different .apk files on Android Market Place for
> > > single application?
> > They all have to have a different package name, which means you would have > > to make (and maintain) 3 copies of your source code. You probably don't want > > to do this.
> > > I would like to have all 3 versions available under one application name. > > > is this possible ?
> > Technically, yes. They can all have the same name via the "label" attribute > > in your manifest, and they can appear with the same name in the Market (you > > set this in the Developer Console). But, again, they have to have different > > package names.
> > I would highly recommend you look through the blog posts for the one about > > targeting different platform versions and seriously rethink publishing and > > maintaining 3 different versions of the same app for each SDK.
> > What happens when 2.1 comes out? 2.2? 3.0? 43.67? Are you going to keep > > making a new version of your app for each new version that comes out?
> > --------------------------------------------------------------------------- ---------------------- > > TreKing - Chicago transit tracking app for Android-powered deviceshttp://sites.google.com/site/rezmobileapps/treking
> > On Wed, Dec 16, 2009 at 2:11 AM, lk <vaish.alo...@gmail.com> wrote: > > > Hi,
> > > I'm developing one android application which needs to support Android > > > OS 1.5, 1.6, and 2.0.
> > > I've three different .apk files for all three SDK.
> > > How can i upload three different .apk files on Android Market Place > > > for single application? > > > I would like to have all 3 versions available under one application > > > name. is this possible ?
> > > So, users with any SDK can use my application.
> > > Thanks.
> > > -- > > > 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+unsubscribe@googlegroups.com<android-developers%2Bunsubs cribe@googlegroups.com> > > > For more options, visit this group at > > >http://groups.google.com/group/android-developers?hl=en
Matt Kanninen wrote: > Mind you, I don't want to use reflection, it frightens me a bit, and > it's annoyed me and made my app harder to debug every time I've used > it. Eventually though we'll really want to use a feature not in 1.5.
FYI, reflection is an option here, but it is not the only solution. You can also:
-- Implement an interface/abstract class representing your wrapper around the APIs you're concerned about
-- Create two implementations, one using the long-term API, one using whatever you're getting by with (e.g., for 1.5)
-- Create a singleton of the appropriate implementation based on the SDK level reported by the device, and use that singleton (via the interface/abstract class)
On a 1.5 device, it will never load the implementation of the new-API class, and so it will never complain with a VerifyError and such.
