Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 7 years ago.
Improve this question
Is it possible to make cross-platform subscription using native APIs and manage those subscription on own backend?
Example:
Make subscription on iOS change device and downgrade(cancel) subscription(plan) on android device.
Spotify for example does cross-platform subscription through PayPal and other payment methods but I'm not sure if our app will be rejected considering in-app guidelines for the both platforms.
Disney did this with their digital content offering and like you said even Spotify did it. The problem here is there are many apps rejected in the appstore( especially Apple's appstore), if one is not given a way to purchase those digital items using the native in app purchase method. Ofcourse,one could have other modes of accepting the money. But it is mandatory to have in-app purchase in place for the app to get accepted(especially with Apple's appstore).So make sure you also implement in-app purchase modules of each native platform. Otherwise, if your offering is too grand(like Disney or Spotify) for the appstores to reject they will accept it. All the best!
Related
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 2 years ago.
Improve this question
After reading several threads on Stackoverflow / Reddit it's still quite confusing what is allowed on Android / iOS regarding payments.
I have a an app available for iOS and Android and a web app dashboard. The iOS / Android / Web app uses a API where your profile and statistics are stored.
To cover the costs of the server I want to add a premium membership feature.
Users can subscribe on a monthly / yearly base.
This allows the user to get more statistics available in the app (iOS, Android and Webapp).
The idea is the same as Spotify (free account / paid account) with the difference that you get music
without ads with Spotify and here you will get access to more statistics data / more filter options in the API.
If you are using subscription method you need to use apple In-App purchase which you are using.
Regarding mentioning the payment provider, you can write in the description about how your app let users use the in-app purchase feature and list out the plans for more clarifications.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 3 years ago.
Improve this question
I need to make around 1000 android apps with same code base but different names, logos, splash screens,images . using android library will solve the issue? One google developer account is sufficient?
Google has recently cracked down on template apps, and you will likely have apps rejected and get your account banned if you attempt this under a single account:
Apps that are created by an automated tool, wizard service, or based on templates and submitted to Google Play by the operator of that service on behalf of other persons are not allowed. Such apps are only permissible if they are published by an individually registered developer account belonging to the user of the automated tool, not the operator of the service.
You may be able to make this work for now if you create a new account for each app that you publish; however, there is no guarantee that Google won't change the Play Store terms of service to prohibit this as well.
It is not a good practice to do so.
If each app uses the same source code but different ressources, you should offer customization options within the main app.
You won't have good dev feedbacks by polluting the market this way.
With customizations, you can reach as much users as you would with a 1000 apps, because you could meet their needs properly.
Take a look at Inn-Apps billing in the official Android developer documentation...
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
I have published free to download apps to google play store before. Now I'm going to publish a app, which users need pay to download and use it.
Is there any additional steps to complete in my application to launch my app as a priced app?
I have little bit confused regarding this because when I'm searching about this, I found about Google Play In-app Billing. for In-app Billing programmer should import library and do some coding part. so I have confused about launching my app as a priced app.
What are the additional steps I should complete before launching the app as a priced app?
What are the best practices to follow when launching the app as a priced app?
When the users dont have to be able to buy stuff in app you can ignore this.
This is related just to those applications which need to manage payments inside the app. If you want just sell your app through Google Play ignore that part.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 9 years ago.
Improve this question
I'm from country where you can buy apps from Google Play Market, but you can not sell, e.g. if I create an app for android, I can only publish it to download for free. Can anybody suggest any alternative services or methods, how I can sell my apps?
Please think/suggest how would you do it?
Something like user downloads the app, pays through PayPal, app checks if payment was made and then app start...
Thanks in advance!
It is against Google Play's ToS to use third party billing vendors like PayPal etc. You run the risk of having your account suspended if you do.
I started selling apps from India before it was officially supported. To do this, I registered an LLC in USA. I paid LegalZoom ~$200 to take care of the registration etc. So far, its worked out pretty well for me, and I haven't felt the need to change this method even though India is now supported as a direct merchant.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 11 years ago.
Improve this question
I need some clarification on the (ambiguous) Android Terms of Service regarding In app purchases with a subscription model.
We are creating a content-based Android app that we would like to sell in the Market using recurring subscriptions.
Here are my questions:
If we use the Android Market in-app billing model, would we need to confirm the purchase every month with the user when we bill their account? Or can we simply ask them when they initially subscribe and then charge them on a monthly basis without a confirmation?
Ideally, we really would like to use the Paypal Mobile Payment Library to collect the monthly fee (saves money). If we are collecting our recurring subscription payment each month using Paypal, does this violate the TOS for Android and will our app be pulled by them? Also, we do not want the user to confirm each month that they agree to the charge. We have already have an iphone app released that charges the user on a monthly basis -- we do not need to ask them each month to confirm. The user is simply charged via Apple Subscriptions. We are trying to recreate the same model using Android.
I have looked on various forums for an answer to my second question, but there is so much ambiguity and no one in the Android Community seems to have clearly addressed the answers to these questions.
Thank you in advance....
If you put this on the Amazon Market you can use the Amazon in app billing api. I believe this is also allowed to be used outside the Amazon market