Hello,
I'm looking to get some clarification about the right way to go about ensuring an iOS app we want to create for a festival will be approved.
The app is part of a ticketed transmedia art project, combining live events, SMS/email/phone communication with the audience, the app and other components. The app will only be available during the festival period and is only relevant to people attending the greater festival. The project would run throughout the festival and culminate at the finish of the festival. The app is not functional until details for the ticket for the larger event has been entered.
The app will require the audience member to enter personal information so that they can be contacted via the other mechanisms throughout the performance period. At the end of the festival period the app will be removed from the store.
Reading over the App Store Review Guidelines it seems there are a number of points which conflict with what we want to do.
ie. These seem to conflict with the desire to require a ticket to become a member of the audience:
11.1 Apps that unlock or enable additional features or functionality with mechanisms other than the App Store will be rejected
11.2 Apps utilizing a system other than the In-App Purchase API (IAP) to purchase content, functionality, or services in an App will be rejected
11.13 Apps that link to external mechanisms for purchases or subscriptions to be used in the App, such as a "buy" button that goes to a web site to purchase a digital book, will be rejected
This seems to conflict with the desire to have the app only available and functioning throughout the festival (and performance) period:
11.9 Apps containing content or services that expire after a limited time will be rejected, except for specific approved content (e.g. films, television programs, music, books)
This seems to conflict with the requirement to collect user information so that we can communicate with them via these channels:
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
These restrictions seem fairly strict in the context of our purpose. If we submit the app, designed the way we've discussed, will it be rejected for the reasons I've mentioned? What workarounds should we consider?
Many thanks,
Chris
