I am in the early stages of scoping an app that will be used within a specialised vertical market. It is not consumer orientated, but it would be convenient to use the Play app store to distribute it. The publisher of the app offers other web-based services and has an existing billing infrastructure.
The app would have some core functionality, and optional modules that could be enabled for individual users. Use of these modules would be billable. I am looking for clarification on how charging for these modules intersects with Google's policies for the Play store. The policies [1] state that "*Developers offering additional content, services or functionality within an application downloaded from Google Play must use Google Play's payment system as the method of payment*". This seems clear enough, but it lacks detail and I've been unable to find anything that expands on it. I have two questions: 1. If the *app itself* provides the facility to enable optional features, then I can see how that would require billing through the play payment system. But if the optional features are enabled *outside *of the app (for example, via a customer's profile page on a web site), does this require billing through Google? 2. The app allows the user to create items of content, and creating an item would be billable, An analogy would be a bug tracking system that charges for creation of a bug report. Does this require billing through the play payment system? Can anyone point me to definitive statements from Google that address these scenarios? Thanks, Andy [1] https://play.google.com/about/developer-content-policy.html -- You received this message because you are subscribed to the Google Groups "Android Discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/android-discuss?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
