{"id":30081,"date":"2020-09-11T15:27:20","date_gmt":"2020-09-11T19:27:20","guid":{"rendered":"https:\/\/mjtsai.com\/blog\/?p=30081"},"modified":"2020-09-11T20:50:27","modified_gmt":"2020-09-12T00:50:27","slug":"new-apple-store-guidelines-for-reader-apps","status":"publish","type":"post","link":"https:\/\/mjtsai.com\/blog\/2020\/09\/11\/new-apple-store-guidelines-for-reader-apps\/","title":{"rendered":"New Apple Store Guidelines for Reader Apps"},"content":{"rendered":"

Apple<\/a>:<\/p>\n

3.1.3(a): Reader apps may offer account creation for free tiers, and account management functionality for existing customers.<\/p>\n<\/blockquote>\n

I wonder whether Netflix will start offering a free tier.<\/p>\n\n

\n

3.1.3(f): Free Stand-alone Apps: Free apps acting as a stand-alone companion to a paid web based tool (eg. VOIP, Cloud Storage, Email Services, Web Hosting) do not need to use in-app purchase, provided there is no purchasing inside the app, or calls to action for purchase outside of the app.<\/p><\/blockquote>\n

I’m not sure whether this changes anything for apps like HEY, Fastmail, and WordPress, except to more explicitly allow them. They already don’t have to use IAP if they don’t sell anything within the app. And they’re already not allowed to mention or link to the world outside the app. Presumably, they will still be required to “work<\/a>” if the user doesn’t already have an account.<\/p>\n\n

Michael Love<\/a>:<\/p>\n

The old bit about ‘must not directly or indirectly target’ for discouraging IAP has been greatly pared back; now it only applies to communication within the app or ‘communications sent to points of contact obtained from account registration within the app.’<\/p>

This is a most welcome change, since it means we can say whatever we like on our websites \/ newsletters (if you don’t tie those to accounts, which thankfully I don’t) \/ etc. (just have to be careful how we link to the website within the app, I guess)<\/p><\/blockquote>\n\n

Previously:<\/p>\n