Re: [android-developers] Same codebase, 2 apks, one free, another paid ?

2012-02-17 Thread Kostya Vasilyev
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.

Re: [android-developers] Same codebase, 2 apks, one free, another paid ?

2012-02-17 Thread Mark Murphy
Use an Android library project for the common code, and refer to it from the apps. On Fri, Feb 17, 2012 at 2: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 ap

Re: [android-developers] Same codebase, 2 apks, one free, another paid ?

2012-02-17 Thread TreKing
On Fri, Feb 17, 2012 at 1:55 PM, androidmediadeveloper < kamathaj...@gmail.com> wrote: > 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. > http://android-developers.blogspot.com/2011/07/multiple

[android-developers] Same codebase, 2 apks, one free, another paid ?

2012-02-17 Thread androidmediadeveloper
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