I'm developing an application that will have some features that the user must pay to use. I was planning to use a Lite and Pro version for this, but the release of In-App Billing have got me thinking...
If I use In-app billing is there any need to implement the licensing (http://developer.android.com/guide/publishing/licensing.html) policies suggested by Google? Or is it enough to implement the Billing stuff?
The application is available for free, instead some features will be enabled using in-app billing. Hence I don't really care if someone "copies" the application as long as they cannot copy purchased features.
BR,
Rasmus
If both applications will be free, you should implement only In-App Billing. You can read Billing best practices for more information.
I have found that the inapp billing and licensing code don't play well together, crashing the app in certain scenarios, like when attempting a purchase when not online.
I don't think it would be worth the risk and overhead to use licensing for a free app even with inapp purchase options. I believe the licensing documentation even mentions licensing can't be used with free apps.
Related
Is there a way to check from code is in-app billing supported for user?
My app is free but i want to do some monetization. But due Google Play limitation when i enable in-app purchases users from countries without billing support can't get new versions.
So i want to detect such situation and suggest them switch to separate free version.
Hi can someone point me in the right direction to implement an in-app purchase to unlock the ad free version on android apps?
You should check these:
In app billing overview
Implementing In-app Billing
Alternatively, you may create a paid app simply as an authenticator, and communicate with the the free app and the paid authenticator, with your own protocol.
These two methods provides different advantages.
I have a free app running on google play store.
I want to add In-app billing feature in my application.But still I want to keep my app free(i.e.,Not paid apps).So is it possible.I have google merchant account.
You can add in-app billing but if you have existing users you will not want to restrict features that are already available to them for free. The usual use of in-app billing is to have a free app with a basic tier of features that remain free indefinitely, and then to create a value-added tier of features that can be accessed by making an in-app payment. If you deviate from that model by charging for features that people were told they could obtain free, then you will have lots of angry users and bad reviews. I don't know whether Google would also look askance at it, but the effect on users should be enough to make you avoid it.
The one exception would be if you offer a timed free trial up front, and all of your users were told from the start that the trial would expire and could only be continued by making an in-app payment.
Yes, you have to worry about Google's policies, but treating your users well should be just as important, and will certainly affect the perception of your app.
Yes i think there is but it needs evualated/approved by Google before you can use it
I have created a free app that includes a in-app billing in order to unlock some features
and I need to use it. I need to buy it?
I have another app, that's not freeware and i have introduced my email address in the developer console in order to use it for free, but it doesn't work with in-app billing. why? I need to purchase my own app? :crazy:
thank's
You don't have to buy your own stuff :)
See Testing In-app Billing
I plan to use in-app billing but the docs say about the limitation.
In-app billing can be implemented only in applications that you publish through Android Market.
I plan to release my app on publisher sites like Amzaon, getjar etc, in addition to Google Market.
How should I handle in-app billing on these 3rd party publishers? Should I use totally separate code for 3rd party publishers (for purchases)? Seems ridiculous.
you can use paypal mpl sdk instead.