Geek Answers Handbook

Best approach for free and paid versions of Android apps?

I developed an Android application that I want to get in both the free and paid versions. What is the best approach?

I can present three solutions:

  • Divide the project into two branches and save both of them.
  • Create a library project and add two additional projects: one "free" and one "paid" version.
  • Use billing in the application.

Q: Which solution is better? And why?

Some things to consider:

  • My application is about 1.5 MB (excluded AdMob).
  • I am currently configured on Android 2.2 (Froyo).
  • I have some server APIs that would benefit from knowing if the client is paid or not.
  • I am trying to avoid hacking an application. Not sure if this is a real problem these days ...
+5
source share
3 answers

I am not a big fan of using advertising in applications, because if your market share is already large enough, the money you receive will be tiny compared to the amount you annoy your users.

I prefer the model of creating a basic application with all the basic functions, and then adding additional functions to the paid application and charging for it (of course, using the android library project for sharing the main part of the code). This way, people who use your application and how it can support you by paying for it, and then get a bonus of additional features.

( : - , , )

+3

, . , Android- . = ( , ).

:

, "" , Android, .

:

Google

:

Android () , 2 Android Project, . strings.xml ( ) `

  • : project- > Properties- > Android- > .
    • , /,

  • Android
  • - > Android- >
  • , : (jar) !
    • - > - > - > - > Jars- > , - > libs- > libary (.. libGoogleAnalytic) → OK- > → → ok
  • : , RE , ,
    • ie: android: name= "com.blah.appname.library.MainActivity" ( / )
  • , lib vs library project! , .
  • /java!
  • , .
  • res\drawable \,
+4

, In-app, , (, , ).

: .

APK , .

+2

More articles:


All Articles