https://blog.kandji.io/in-app-purchases-for-enterprise-buyers
Thank you Caleb and #Kandji for a couple of ideas about how app developers could better support enterprise and education customers.
Are they really long-term "solutions" though, or just short-term work-arounds?
(1 / 6)
For example, both proposals introduce extra risk of being rejected by App Store review. Both potentially violate guideline 4.3 ("Don't create multiple Bundle IDs of the same app"), and the second one also potentially violates guideline 4.2.6 ("Apps created from a commercialised template will be rejected").
Not to mention that both proposals burden app developers with more development work.
(2 / 6)
Trying to change app developers' behaviour is obviously easier than trying to change Apple's behaviour, but a conversation about this issue seems incomplete without at least mentioning some of the things Apple could be doing to actually solve it.
Examples follow...
(3 / 6)
Subscriptions in the Apps and Books program.
Why force app developers to implement work-arounds when Apple could "just" implement the missing feature?
(4 / 6)
Upgrade pricing.
Many app developers only switched to convoluted in-app purchases or a subscription model reluctantly in the first place, and would have preferred to use upgrade pricing if such a thing existed in the App Store.
(5 / 6)
Third-party sales channels.
Open up to competition. Not just in the EU. Not with fees that make the business model unsustainable. Make space for innovation. Apple doesn't have to implement alternative payment methods if third-parties can.
(6 / 6)
Damian Lettie