possibly a simple question, but I couldn’t find definitive answer (see below for excerpt from HIG) myself that would state below scenario as ‘unacceptable’ and will result in app being rejected:
- On 1st application launch after installation user will see an alert
asking to activate the app. - Tapping “Activate” will open Safari and display a web page with
“Activate” button. - Tapping it will launch my app via URL-scheme, pass some server
generated data and allow user to enter main UI. - The application will be locked until user activates.
If you need more context on why and how, please see this answer.
Mobile HIG (as of 2011-10-12):
“If possible, avoid requiring users to indicate their agreement to your EULA when they first start your application. Without an agreement displayed, users can enjoy your application without delay. However, even though this is the preferred user experience, it might not be feasible in all cases. If you must display a license agreement within your application, do so in a way that harmonizes with your user interface and causes the least inconvenience to users.”
Well there’s similar cases where an app is almost useless until the user registers to some service, take Instagram as an example.
I’d suggest however that you solve this by not forcing the user to leave your app. Instead, present the user with a web view within your app where you politely describe why it is necessary for the user to go through the activation process.
We’ve done something similar before (EULA presented modally within a web view on first launch, which could only be dismissed by accepting it) and it was approved right away.