To build separate APKs while maintaining a more-or-less common code
base, look into using an Android Library project:
http://developer.android.com/guide/developing/projects/index.html
Market lets you upload multiple APKs for the same package name,
targeting distinct API levels or screen sizes. I'd recomment the latter,
given that Android 4.0 supports both phone class and tablet class devices.
All of those are presented to the user as a single application, so I
don't think you'd be able to charge just for the tablet version - unless
you used in-app billing.
Alternatively, you could give the tablet version its own package name,
essentially creating a separate paid app.
-- K
On 02/17/2012 11:55 PM, androidmediadeveloper wrote:
We are trying to come up with a tablet optimized pro product that we
only want shipped in the market as a paid app. We currently do have a
free app in the market which is doing fairly well. I understand there
are package naming restrictions and even if we build multiple apks
(phone and tablet), we wont be able to host them separately. From a
tech perspective we want to just maintain one codebase given both
flavors are going to share a majority of the functionality.
That leaves us with some "preprocessor" type step where prior to
building the tablet apk, we create a new manifest, change the package
name, change package names on all sources, and then produce separate
apks. This is undesirable as is obvious.
Any ideas here ? Any lessons learnt ? Any advice ?
--
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
