Would Apple allow in-app-purchases which give access to a web app or online service? If, for example, I build a native iOS app version of an online service (say, a paid service similar to Readability, Squarespace etc.) would Apple allow me to use in-app-purchase to allow users to buy a subscription which would give users access to both iOS and web version of the service?
I'm asking this because, after initially thinking that this would be allowed, I found that https://developer.apple.com/in-app-purchase/In-App-Purchase-Guidelines.pdf contains: "In-App Purchase items cannot be shared across applications or platforms." which seems to disallow this. However, in the same pdf, Apple explicitly say that services like buying VoIP minutes are allowed to be dealt with in in-app-purchases. Additionally, in the past Readability was rejected for not providing in-App-Purchases, seemingly suggesting that this is allowed.
Put simply, do Apple allow that after an in-app-purchases for an in-app-service is made, the same service access is given through a web version of the iOS app?
I think it is provided the service is consumed majorly through the iOS app itself. Subscriptions can work the way you are suggesting but only if if you also provide the same service as on the web in your app.
Related
Good day,
I wanted to know how possible it is to have in app purchases/billing in a PWA app? if so can I get a reference to how to implement it?
Thanks in advance.
Godfrey
In short answer, yes.
It is completely possible make purchases available in Progressive Web Apps (PWA) because of the Payment Request API or if you are looking for a service, you could implement PayPal or something similar.
I don't understand how you couldn't figure this out on your own. It seems like you do not understand PWAs very well. A PWA is "a web app that uses modern web capabilities to deliver an app-like experience to users" so basically there's no reason why any feature that is not available on the web could not be available on a PWA.
You always have the capability make your web app a PWA but it is impossible to make your PWA a web app because it already would be.
Read More about PWAs at https://ionicframework.com/docs/intro/what-are-progressive-web-apps
I got an offer to develop a simple iPhone app that would call a web service with user's credentials. An user would get the list of files that can be downloaded (.pdfs) and could then download the wanted file. Simple enough...
Now, I've had bad experience with publishing on AppStore. Basically, they refused one app because according to them our RSS reader for a online newspaper wasn't in accordance with their guidelines. They said that the application was a simple web aggregator which I won't argue now. Not now :)
So, back to the new app problem :)
I would like to know what are the options for distributing the new app. The client has a web page and wants to give it's visitor this app to get that data from their phones too.
Technically, the app doesn't have to be a native app. It can be a phoneGap solution too since it's quite simple regarding the functionality. Sincerely, I am afraid that there is no way that Apple will allow this app to be uploaded to their store being native, phoneGap...
P.S.
I would also like to know is there a way to distribute an "internal" (not publicly available) iPhone app? For example, a company needs an internal tool for their 500 employees, but can't afford to go through the process of conecting each device and compiling the app for each device individually...
If you want to sell customized apps to companies, you should consider the B2B program.
if you are in an enterprise that wants to deploy apps inside your company, the Enterprise Developer Program is a good choice.
For internal:
100 test devices.
alot of iphones with the distribution profile after the 100 devices
with the enterprise:
https://developer.apple.com/programs/ios/enterprise/
Is it possible to create an iPhone app which just redirects the user to my HTML5 mobile website? If it is possible, do you know if Apple can refuse my app? (Maybe it is written somewhere in their Terms & Conditions?)
The aim is to be present on the App Store, but to only have one version of my website to maintain.
If you have a web app, you should make an iOS app that is nothing more than a UIWebView that points to your URL. A lot of apps do this, and in most instances, you really wouldn't know it's not native unless you are a developer. For example, the Discover card app uses this technique. The only caveat is it should be a web app and not just a web site, i.e. it should do something useful and look like a native app instead of just being a web page with general information. Otherwise, you will be subject to this:
2.12 Apps that are not very useful, are simply web sites bundled as apps, or do not provide any lasting entertainment value may be
rejected
Yes you CAN create such an application. However, apple WILL reject such an application because of their Guidelines.
2.12 Apps that are not very useful, are simply web sites bundled as apps, or do not provide any lasting entertainment value may be rejected
The key to this would be Not very useful, since all it does is open a web browser and direct to your site.
my app is like an iPod for web articles.
You can listen to the web articles. http://lisgo.org/
I am working on a free version with in-app-purchase now.
But, I'm not sure if I can do subscriptions model for a upgraded version on app store.
There is no web version for my app, even though it needs to connect to the internet for
article parser.
For example, I want to do like this.
Free version = ads, voice speed 1x only, no offline mode.
Premium version (subscriptions) = no ads, multiple voice speeds, offline mode.
I have not seen apps which unlock their features on subscriptions unless it has been
provided as a web SaaS service. And, my friend told me it is against apple's guide line,
but I couldn't find the page states that rule.
Any advice will be appreciated so much!
Thanks.
Apple said to me that auto-renewable subscriptions are only allowed to publishers, not for web service vendors.
It seemed that I can try non auto-renewable subscriptions because they suggested it, but I haven't tried it yet. I believe one time in-app-purchase is good for my model for the moment.
The author of Instapaper also talked about this on his podcast, and he needs to use non-renewable subscriptions for his additional subscription model.
I need to create an app for a large company.
Their aim is to distribute this app to all of their customers (who themselves are companies - not individuals) and the end-user will be able to query their relevant information through this app.
The app will receive all of its data through webservices and will require login on every use.
On the one hand a web application might be suitable as all the data is anyway online and also distribution of such an app would be trivial.
On the other hand, they might want features in the long term which use the camera etc. and also the administration of the website (in addition to the existing web services) might be a problem - which means a native app working with web services is the solution.
The next question is the preferred way of distribution for this app if it is a native app.
I know Apple have the Enterprise program (which seems to have changed - I no longer see the reference to >500 employees or 250 device limit).
In my case there is one main company distributing the app to many customers so I don't know whether this program is appropriate.
Any advice would be appreciated.
I once had a similar problem... we ended up with the application in the store and an authentication mechanism inside the application. Most likely, customers would have to provide the user credential they use to authenticate at the web application to the iPhone app as well.
For the decision whether to build a native application or use a web application, I would recommend using a hybrid approach. This way you can start with an application which is based on an UIWebView and extend it with features only available to native applications...