7/26/2016: https://developer.apple.com/app-store/review/guidelines/#other-business-model-issues
"......
3.1 Payments
- 3.1.1 In-App Purchase: If you want to unlock features or functionality within your app, (by way of example: subscriptions, in-game currencies, game levels, ...Apps distributed via the Mac App Store may host plug-ins or extensions that are enabled with mechanisms other than the App Store.
- 3.1.2 Subscriptions: Auto-renewing subscriptions should only be offered using in-app purchase and may only be used for periodicals (e.g. newspapers, ...
the app is available. You may offer subscriptions that are shared across your own apps, but these subscriptions may not extend to third party apps or services.
- Note: We will update these guidelines in the coming weeks for the subscription changes launching this fall.
_____________________________________
I have the following Mac App Store questions:
I want to start selling a new productivity product today that can best transition to a subscription model in the future?
For now, I want to try to do that using a single bundleID.
Start selling today:
- free to download - this triggers a 7 day subscription to the ‘Full Version’
- current in-app purchase to unlock the ‘Full Version’
- a future in-app purchase, sometime this fall, that will unlock subscription based access to new and broader functionality also available in the fall.
Clarifying Questions
Is ‘Save to Disk’ a sufficient feature to make the ‘Full’ version? Is '10 Saves' better for some reason?
Is there a reason ‘Save to Disk’ should not be an in app purchase or be the sole distinguishing feature to a ‘Full’ version?
If a customer does not elect this future subscription: this customer simply retains either free or ‘Full’ functionality in perpetuity. Yes?
freeloadersDown continue to receive product enhancements in perpetuity, yes?
can the available set of in app purchases change over time for these freeloadersDown?
If a customer does elect this future subscription:
Auto renew will usually manage the customer’s view - requesting acknowledgement in/around renewal date.
A browser-style interface will continue to allow more hardy souls to self examine.
If the custom does terminates a subscription:
- Can I offer an in app purchase that locks in the current subscribed functionality in perpetuity?
- Auto renew continues until the customer acts to stop it, yes?
e.g. a developer might not issue new functionality for multiple subscription periods, the custom decides when the relationship is over…
I'm looking for all feedback!!
Is this an efficient product strategy?
Steve