android - Best Practice for releasing 2 versions of app -


i'd release 2 versions of app, pro version have pay , free version. difference (so far), free version has ads , pro version doesn't, few lines of code difference. still want able give away pro version free (for example beta-testers). best practice that? have following questions:

  1. should give them .apk of pro version? don't idea of giving .apk away. btw: can somehow .apk of installed paid app? assume can't because wouldn't these shared then?
  2. an idea give both versions identical code including boolean pro. in free version false, in paid version true. additionally in free version can set true after entering secret code. has disadvantage if secret code gets leaked somehow, gets pro version easily. how if make code depend on device specific constants?
  3. do need change package name if release 2 versions?

thank in advance answers!

you can publish 2 different apks, pro , free, lot of developers in google play, example, follow way. don't need boolean going stored in setting modifiable in rooted phone.

to handle development of 2 version can use branches (managed software versioning tool, such git or svn) , directly merge changes 1 (pro free, example).


Comments

Popular posts from this blog

android - Get AccessToken using signpost OAuth without opening a browser (Two legged Oauth) -

org.mockito.exceptions.misusing.InvalidUseOfMatchersException: mockito -

google shop client API returns 400 bad request error while adding an item -