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 <[email protected]> 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 [email protected] > To unsubscribe from this group, send email to > [email protected] > For more options, visit this group at > http://groups.google.com/group/android-developers?hl=en -- Mark Murphy (a Commons Guy) http://commonsware.com | http://github.com/commonsguy http://commonsware.com/blog | http://twitter.com/commonsguy Warescription: Three Android Books, Plus Updates, One Low Price! -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
