Show Notes
Today I wanted to take a quick run through the App Review Guidelines. Love ‘em. Hate ‘em. They are one of the most core parts of creating and distributing apps for the App Store. I will give some high level thoughts about the state of App Review and then walk through some of the recent changes Apple published.
I’ll also touch on the new page Apple published listing the Common App Rejection reasons.
I went ahead and organized the changes into a more readable format.
Accessibility Note: A less color oriented version of this diff is available here.
Preamble
We have over a million Apps in the App Store. If your App doesn’t do something useful, unique or provide some form of lasting entertainment, or if your app is plain creepy, it may not be accepted.
2. Functionality
2.9 Apps that are "beta", “demo”, “trial”, or “test” versions will be rejected. Beta Apps may only be submitted through TestFlight and must follow the TestFlight guidelines
2.25 Apps that display Apps other than your own for purchase or promotion in a manner similar to or confusing with the App Store will be rejected, unless designed for a specific approved need (e.g. health management, aviation, accessibility, etc.) or which provide significant added value for a specific group of customers
Update: Section 2.26 still includes much of this language and reads “Apps may display and recommend apps other than your own only if the collection is designed for a specific approved need (e.g. health management, aviation, accessibility, etc.) or provides significant added value for a specific group of customers, or they will be rejected” Thanks @Padraig
3. Metadata
3.3 Apps with names, descriptions, screenshots, or previews not relevant to the content and functionality of the App will be rejected
3.6 Apps with App icons, screenshots, and previews that do not adhere to the 4+ age rating will be rejected
3.14 App previews may only use video screen captures of the app, voice-overs, and textual and design overlays, or the app will be rejected
3.15 Apps with previews that display personal information of a real person without permission will be rejected
3.16 App previews may only include music that is licensed for that purpose in all selected territories
3.17 App previews that include content played or streamed via the app (e.g. iTunes playlist, YouTube streaming video) that is not licensed for use in the preview will be rejected
14. Personal attacks
14.3 Apps that display user generated content must include a method for filtering objectionable material, a mechanism for users to flag offensive content, and the ability to block abusive users from the service
17. Privacy
17.5 Apps that include account registration or access a user’s existing account must include a privacy policy or they will be rejected
22. Legal requirements
22.10 Apps that use iTunes music previews in an unauthorized manner will be rejected
25. Extensions
25.1 Apps hosting extensions must comply with the App Extension Programming Guide
25.2 Apps hosting extensions must provide some functionality (help screens, additional settings) or they will be rejected
25.3 Apps hosting extensions that include marketing, advertising, or in-app purchases in their extension view will be rejected
25.4 Keyboard extensions must provide a method for progressing to the next keyboard
25.5 Keyboard extensions must remain functional with no network access or they will be rejected
25.6 Keyboard extensions must provide Number and Decimal keyboard types as described in the App Extension Programming Guide or they will be rejected
25.7 Apps offering Keyboard extensions must have a primary category of Utilities and a privacy policy or they will be rejected
25.8 Apps offering Keyboard extensions may only collect user activity to enhance the functionality of their keyboard extension on the iOS device or they may be rejected
26. HomeKit
26.1 Apps using the HomeKit framework must have a primary purpose of providing ho
More from Developing Perspective
Gone are the days of map-and-compass development, now if we can imagine it and see a line of sight to it we can build things nearly instantly. Which totally changes the cognitive and structural tradeoffs we need to make in our development process…and how we take care of ourselves in that.
I walk through the history of Apple developer platforms over my history as an app developer and grade them, then think a bit about what has made them worthwhile.
I’m bringing Developing Perspective back. This first episode wrestles through why being an indie app developer right now feels so “pivotal”, in both senses of the word. There’s the constant, week-by-week change in our tools and workflows, and there’s the bigger structural shift in what it even means to “make” apps.
I tend to think of my app business in terms of revenue per day. Breaking it down to that level helps me keep a close eye on it and know how well or poorly I’m doing. Today I walk through the reasoning for this as well as do a thought experiment of what the numbers might look like for a new business.