Can i distribute an unfinished iOS app for closed beta with the Apple Store?

We would like to do some closed beta tests of our application using the App Store.

We know about the ad-hoc method, but for testing UDIDs, it is necessary that the testers UDIDs be collected in advance and built into the training profile, which is not ideal, because we would like to avoid polling 100 testers for their UDIDs.

Another way is to use Enterprise Distribution, which does not need to collect and store UDIDs, but let me talk about another possibility ...

The user must log in when the application starts. User accounts cannot be created from the application, so we are thinking about creating some beta testers on the server, sending the beta version of the application to the Apple Store and sending the credentials to beta testers by e-mail.

The only question is whether it is recommended to present the incomplete application of the Apple Store. After sending, all iOS users will be able to download the application, but only beta testers will be able to log in. This also has the added benefit that Apple feedback previously knew, so any issues could also be addressed earlier. Do you think Apple will approve the unfinished application?

Also, is it possible to disable application verification for an application sent to the Apple Store? We don’t want to receive bad reviews from users during beta tests ...

Thanks Michal

+8
source share
5 answers

The simple answer is No.

Detailed response. No, Apple requires apps in the app store to be end products. You can try to slip through it until you call it a beta version or make a link to the fact that it is not complete. When using this method, you bypass Apple policies that could lead to revocation of the developer’s license.

Further information can be found HERE -> https://developer.apple.com/app-store/review/guidelines/ <- HERE

Edit to add: No, you cannot disable reviews in the app store.

+10
source

Now you can use TestFlight Beta Testing with a current limit of 1000 invitations and without having to request and register UDIDs.

+13
source

Beta applications are clearly prohibited by the recommendations of the Apple App Store.

However, if you do not explicitly paste or advertise the application as a beta test, and the application appears to be fully functional and unacceptable, Apple may approve the submission.

In fact, quite often, developers can send incomplete applications and put them in the application store (see the "minimum viable product" style of development). However, incomplete functions should not be obvious and are not mentioned anywhere in the description of applications or documentation, so that the application looks fully functional for reviewers (for example, if any function is missing, then hide the button and documentation for it so that no one knows what something is missing). I have an app in the app store that has only 5 or so of the many dozens of features in my original design specification. Nobody knows (still :)

It is impossible to limit application downloads to specific testers (other than using Ad Hoc, Enterprise or B2B accounts) for closed testing, and there is no way to prevent bad reviews and ratings. You can limit the availability of applications by country and day and do not send any search keywords to limit exposure. You can try to rate your application too high and donate the application to your testers if you are willing to give Apple 30% of the high price per copy.

+5
source

I'm 99% sure that Apple will not allow this, mainly because you forbid most people to use the application. Also because you are sending an incomplete application.

+1
source

If I understand the rules of Apple Developer correctly, you cannot distribute your beta application to any external entities (public clients, friends, etc.), except for using the TestFlight test suite. Many people (and your question mentioned it) talk about AdHoc as about it. If you look at the Apple Developer website and try to add the device to your dev account, they give a pretty clear warning ( see the image from the SO question here) , which says that Ad Hoc can only be used to organize internal , or if You are the legal agent (i.e., a consulting firm hired to create an application for the company) of this organization. Based on this, I do not think that AdHoc will force you to abandon the use of TestFlight for external beta testing.

+1
source

All Articles