Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 9 years ago.
Improve this question
There's a service without free registration or something like that. Clients of this service have login and password. This service wants to develop an iOS app and distribute it in the App Store. This app won't be useful for regular users. Is it possible to submit this app in the App Store?
I understand that there are options like enterprise developer account, but for some reasons the developer wants to use regular account and regular app store.
I've read App Review Guidelines and didn't find any restrictions which require application be useful to anyone.
Of course test login will be provided for reviewer.
It is possible, look at concur & office 365 as examples
Related
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 6 years ago.
Improve this question
I am currently making an app using Tinder API. It's very similar to those auto-liker apps that leverage Tinder API as well.
My app was rejected on the ground that the user is not presented Terms of Use Agreement before accepting to send login info to Facebook for use of Tinder token.
Now that is fine, but Apple also called me and said that
"There are rules not written in guidelines, and we do not accept apps that use unofficial APIs and scrapes websites that you do not own."
I checked the guidelines, and only things written there are that
Do not use unofficial API - I interpret as non documented iOS API.
Do not scrape Apple websites
Furthermore, there are dozens of Tinder auto-liker type apps, and yet more apps that scrape third party websites.
Why is the Apple review team telling me those things?
Has anyone else ever heard from the AppStore review team that:
We can only use "Official" APIs
We cannot scrape third party websites
There are rejection rules that are not written in the guidelines.
Any feedback is appreciated.
EDIT
The point here is that is there an unofficial non-written rejection
guidelines. I believe that is a gray issue since it can be grounds
for lawsuits and I want to get experiences of other developers if
they have received similar explanation over voice calls.
From my experience, any app that provides login-registration to users, needs to have a Terms of Service and a Privacy Policy page displayed to user before registration. Just add these 2 and resubmit the app for review.
Ok so after three phone conversations with Apple, the rejection reason was made more clear. It has nothing to do with "non-written" guidelines... there is no such thing. I am not sure why the reviewer mentioned in one of the conversations.
Basically I was exposing some data for Tinder users gained for API in a certain way, and Apple thought that I needed to gain their consent. Now, the other Tinder users are not users of my app, so it is impossible to gain their consent. That was the real rejection reason.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 7 years ago.
Improve this question
I have a website that hosts online courses for registered users.
I am now creating an app that will:
Ask users to login,
Allow the user to navigate their courses,
Allow the user to play course content.
My question is, will Apple accept an app that:
Requires a user to login before gaining any value?
Does not allow users to register on the App (you have to register on
the website, there is a link on the app login page to the website
registration - the registration is free).
The Apple guidelines do not explicitly say that you have to be able to register on the app. Does anyone have any experience with this?
As per my experience Apple will allow, I have 3 apps in App Store that have similar workflow you mentioned.
My App Works like:
When app is opened it ask for a PIN
User can get the PIN by registering to our web-site
After entering the PIN my app allow the user to continue
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 9 years ago.
Improve this question
I am developing an iOS app that basically allow people to donate money to charities. This app will be free on the App Store.
Apple guidelines state the following:
21.Charities and contributions
21.1 Apps that include the ability to make donations to recognized charitable organizations must be free
21.2 The collection of donations must be done via a web site in Safari or an SMS
i want to use PayPal mobile sdk (MPL library) to charge the user and pass the money between his PayPal account and the charity's PayPal account.
Is this comply with apple rules (especially 21.2)? will my app be rejected by apple?
must i use a web-view in my app for the implementation of the payment stage? is PayPal mobile sdk apply to their rules?
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 10 years ago.
Improve this question
My App is rejected by the reason :
"We found your app inappropriately unlocks or enables additional functionality with mechanisms other than the App Store, which is not in compliance with the App Store Review Guidelines"
"It may be appropriate to revise your app to use the In App Purchase API to provide content purchasing functionality. "
What I have done is as below:
As this app is for my specific customer companies to use, I only want the companies who get the Invitation Code from me to use my app. There is no charge. I don not know is it necessary to use the In App Purchase API instead? if it is true , can you give me some tips?
Your application cannot be used by members of the general public, and thus does not belong in the App Store.
If you only intend your application to be made available to a few specific people, you should use Ad-Hoc Distribution to make it available to them.
Explain the purpose to the review team, sometimes they listen.
Also, maybe have that message as a "login page" instead. Have a username and password rather than a verification code. The verification code message may look more like you are selling the app behind the AppStore. Also provide the review team with an access code / login details if you haven't already so they can actually review the app.
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 10 years ago.
Improve this question
I developed an app for the company who sells professional e-books by their website. In order to keep the content in sync with web data, app enforce login/registration and without that doesn't provide any functionality.
This is the reason why it has been rejected for Review Guidelines 17.2 Apps that require users to share personal information, such as email address and date of birth, in order to function will be rejected
My question is: is there a way to convince Apple to accept an app?
It is directed to the very specific proffessionals.
In the future the company want to add the possibility to sync books available on their website.
Also the books bought by in app purchase would be available on their website for the user account.
Isn't that enough reasons for Apple to accept this app? My client strongly want to have an account based app, the whole system was designed for that.
There is possibility to track user by udid but still it is not good solution because it is deprecated and Apple rejects apps using UDID for tracking reasons.
Does anyone have similar situation recently?
You say:
"app enforces login/registration and without that doesn't provide any
functionality."
Apple says:
"Apps that require users to share personal information in order to
function will be rejected"
So the answer is kinda obvious.
The app should provide (at least) some basic functionality without sharing personal data.
Maybe some book previews? 1 or 2 free books? App info? Why not apple's-bookstore? Does the website (before seeing anything) force you to signup too? Otherwise just make a web-app.