Question

Hello I am a beginning android developer using windows and the eclipse IDE to develop java android applications.I have published one game but there is a free version of the game and a paid version. The google market insists that the different versions must have different package names. So far i have been refactoring the package with 2 different names and changing the R resource file import each time i build the different versions. The code is 99% the same for both versions.Is there a better way?

Answer 1

You have various discussions on this topic here and there, but basically the solution is akin to duplicate the project.

For instance (not based on eclipse):

It is difficult to answer this, since we don’t know what the difference is between the free and not-free versions of your app.

I’m going to assume that the differences could be handled by some sort of global free/not-free flag. By that, I mean that the same code would make up both versions of the app, and which portions are enabled or used would be dependent on some public static data member somewhere:

if (SomeClass.IS_PAID_APP) { 
        // add more stuff to menu, etc. 
} 

If you can organize your app that way, then you only need one code base.
Have it set to build your app one way (free or paid, your choice) and with the proper package in your manifest for that version of the app.
Then, add an Ant task that does the following:

1. Makes a tree copy of your project dir to a temporary location
2. Switch the copy of the manifest to the new package name via a
   search-and-replace
3. Switch all import statements for your old package’s edition of R to
   the new package, again via search-and-replace, and again on the copy,
   not your original
4. Change your IS_PAID_APP (or whatever) to the opposite value
   (search-and-replace in the copy)
5. Executes an Ant build for the copy of the project
6. Copies the binaries from that build to the main project’s bin/
   directory under a distinct name (so it doesn’t clobber your other copy
   of the APK)
7. Deletes the tree copy made in step #1

If Java had a pre-processor, this would be somewhat simpler. However, the basic technique that I describe above has been used for a couple of decades now. It’s clunky, but it works, and it means you only have one set of source code to deal with.
Note that the Ant <replace> task would handle your search-and-replace stuff nicely.