We have an app that schedules tutoring sessions and delivers post-session progress reports to parents via physical means, and we're moving to a SaaS pricing model for the entire business. Having worked with Apple IAPs before, I'd love some confirmation from the forum that this user flow will pass review, especially since we seem to fall under the "reader" exception:
3.1.3 “Reader” Apps: Apps may allow a user to access previously purchased content or content subscriptions(specifically: magazines, newspapers, books, audio, music, video, access to professional databases, VoIP, cloud storage, and approved services such as educational apps that manage student grades and schedules), as well as consumable items in multi-platform games, provided that you agree not to directly or indirectly target iOS users to use a purchasing method other than IAP, and your general communications about other purchasing methods are not designed to discourage use of IAP.
Our user flow includes:
0. plan selection and subscription payment via a web flow that doesn't touch the app
1. registration and onboarding via an embedded webview
2. scheduling sessions/setting up payouts from parents (available for everyone)
3. available features (progress reporting, on-demand chat assistance, etc) for paying customers, paid through an exterior gateway.
4. "manage your account" button from within the app that allows a user to cancel or update their plan as one of many options.
I'm concerned about providing any access whatsoever to an outside payment gateway, even if it's never being communicated via the app and users are never upsold on features. There's also the question about whether some of our physical features (progress reports are physically mailed, for instance) make the rest of the subscription exempt from IAP in full.
Thoughts? Thanks!
