title: Maintaining both free and pro versions of an application
body: <p>I want to create a PRO version of my application for Android and was wondering how to structure my repository.</p>
  
  <p>For know I have a trunk and feature branches. I'd like to put a pro version in another branch but maybe there is a better way? For example, maybe I should create two branches - one for free version, the other for pro?</p>
  
  <p>Pro version will have additional features and will be ads-free, so eg. I don't want to include AdMob libraries in the pro version.</p>
  
  <p>Do you have any experience or suggestions as to what would be the best way to structure the repository in this case?</p>
  
  <p>EDIT:
  I think I've found the best solution (for my app) in this thread: <a href="http://groups.google.com/group/android-developers/browse_thread/thread/4ad3d67f735f16d7/948b4f9eee2490a3" rel="noreferrer">http://groups.google.com/group/android-developers/browse_thread/thread/4ad3d67f735f16d7/948b4f9eee2490a3</a></p>
  
  <p>The trick discussed there is about having another application that only serves the purpose of unlocking PRO functionality in the actual application. The unlocking app is paid in the market and the actual app merely checks for the existence of it on the device.</p>