Geek asks and answers

Android project structure for RC, Lite and full application

I am planning an application for the Android Marketplace.

First I want to publish it for public testing as a free RC in order to collect some feedback before publishing the Full app as a paid application. When RC is replaced with the full version, I will publish the free Lite edition with some limitations.

The plan is to add a basic feature set without any restrictions for RC

Will be later

  • Full paid version with many features.
  • Free Lite version with the same features as Full, but with certain limitations.

I am looking for some tips on how to plan my project structure in order to avoid a lot of refactoring / moving code as the application develops.

Does something like this look reasonable?

  • Main branch
  • The free RC application comes from the main branch and is published on the Market when ready
  • When the RC life cycle ends, all changes with RC merge into MAIN, and the RC branch terminates. The RC application is now also withdrawn from the Market.
  • The free Lite application is obtained from the main branch, some restrictions apply to the Lite branch
  • The MAIN branch is now a branch for a fully functional application. When new versions of the Full application are ready, the changes are merged into the Lite branch, so new features are added without any restrictions.
+3
source share
2 answers

I faced the same problem once, I decided to go with the following structure. (I have an application with LITE / PAID output).

, maven. , .

My Maven (pom.xml) , , , AndroidManifest, , , APK :

mvn install -Dedition=lite -P release

, , , pom.xml(, maven).

,

+1

() / Eclipse ADT, (lite, full) . firstlightassociates donnfelker.

  • com.example.myapp - Android / .
  • com.example.myapp.full - Android. .
  • com.example.myapp.lite - Android. , .
0

More articles:


All Articles