Microblog
7/7 Finally, I’ve gotten some comments suggesting this is targeted at Amazon to force them to sell e-books via in-app purchase in the iOS Kindle app. Nope. “Reader apps” fall under a different guideline – 3.1.3(a) – which doesn’t have the same IAP requirement that 3.1.3(b) has.
6/ That said, it seems like it might be tough (and time consuming) for App Review to investigate and judge whether an app is or isn’t multi-platform. I anticipate that lots of apps that are iOS-only will slide through.
5/ Additionally, 3.1.3(b) is very clear that it applies only to “apps that operate across multiple platforms.” Apps that are iOS-only need not apply. They don’t qualify to sell features through their website.
4/ The wording of 3.1.3(b) seems designed to require these SaaS products to offer their subscriptions via in-app purchase as well. We’ll have to see if this interpretation is consistently enforced.
3/ Realize that guideline 3.1.3(b) cuts both ways. It will be a great option for some apps, but there have been some SaaS that have gotten a “free companion app” on the App Store that requires a subscription that is only available on the SaaS’s website.
2/ First, this is a great new option for mobile apps that has the potential to really increase revenue for developers. But only if you can get customers to visit and purchase through your website. This will be a marketing challenge for small indies, but that’s business. ?♂️
1/ There’s a lot of excitement in my timeline about Apple’s new App Store review guideline 3.1.3(b) that allows sales through a developer’s website (thereby avoiding Apple’s 30% cut) for multi-platform apps. A couple thoughts:
