Getting your app approved on Google Play and the App Store can be tricky if you don’t know all the rules. This detailed guide, complete with examples, will help you navigate the world of app publishing.
Here are the basic things to look out for:
Privacy Policy and User Agreement
First, your app needs a Privacy Policy and User Agreement (also known as Terms & Conditions). Most Android apps require a Privacy Policy. The rare exception is if your app doesn't handle any personal or sensitive data. Generally, it's best to assume your app needs a Privacy Policy to comply with global privacy laws.
You can post the Privacy Policy within the app or on your store page. If you link to a company website, ensure the link works and the page is accessible. You can also place the Privacy Policy on a separate page and add a link to it under each data collection form in the app. If the app includes in-app purchases, the Privacy Policy must be available inside the application.
Data Collection
When your app asks for permission to access data or device functions, you need to explain why. If your app requests permissions without a clear reason, it's likely to be rejected. For example, apps that ask for the user’s location without a clear necessity are highly likely to be declined by the stores. Both users and app reviewers need to understand what’s happening with their data.
Account Management
Starting June 30, 2022, apps submitted to the App Store that support account creation must also let users delete their accounts within the app. Deleting an account removes it from the developer’s records, along with any associated data that the developer isn’t legally required to maintain. The same rule applies to Google Play. You can choose whether to allow users to restore their profiles, but you must provide an option for account deletion.
System Functions
It’s important not to interfere with system functions or gestures. For example, on Android, you can't disable the back button because users expect certain behaviors, and changing them can lead to rejection. The same applies to volume and lock buttons on both iOS and Android. You can assign additional functions to some buttons, but generally, their primary functionality should remain unchanged.
In-App Purchases
For in-app purchases, all digital content like subscriptions, music, books, or extra features must be sold exclusively through the In-App Purchase (IAP) system. While buying jeans on Shein and digital books may seem similar, you cannot implement the purchase of digital content in mobile apps using the same methods as physical goods. Attempting to do so, or linking to an external payment site, will get your app rejected by Google Play and the App Store. For instance, buying a premium account in Flo, a subscription to Microsoft OneDrive, and all payments in games like Among Us are implemented via In-App Purchases.
Users should see all the information about the app’s pricing, terms, and any in-app subscriptions offered for purchase. They shouldn’t be forced to perform additional tasks to unlock content or features, like rating the app or installing another app.
Additionally, ensure users can restore their purchases if they switch devices. There should be a “Restore purchases” button that works with the same Apple ID or Google Account.
Physical Objects Purchase
While digital items must be bought through IAP, physical purchases can be completed using third-party payment systems (like PayPal or Stripe) or directly through the app. This includes items like clothes on ASOS, supplements from iHerb, and anything from Amazon.
For third-party payment systems, the user should be redirected to the app’s website to complete the purchase through an external payment processor. Payment or refund issues must be resolved through the third-party provider and not through the app or app store.
For direct purchases through the app, payments can be made by entering card details into the app, such as paying for a taxi ride with Uber or ordering takeout from GrubHub. The card information can be entered within or outside the app.
Gaming Rules
If your app involves any kind of games of chance, like lotteries or casinos, you must display the rules for participation and winning before the user starts to play.
Loot boxes, a special element of such games, must disclose the chances of obtaining different categories of items. In some countries, loot boxes are considered a form of gambling and are regulated accordingly. To get your app approved on Google Play or the App Store, you must disclose these chances.
Age Restrictions
Ensure all content in your app matches the age rating you’ve set. This is important to avoid getting flagged or rejected. Restrictions for most countries are as follows: dating apps 16-18, shooters 16, gambling 18, horror and violent games 18 years old. But better check twice before the app release. Ads must also be consistent with the age rating.
Users should see age restrictions before accessing the app functions. To verify age, you can display a form asking for the user’s birth date. If they are not old enough, show a message like: “You are welcome at our service when you turn 18,” as seen on Tinder.
The Kids category in the App Store and Google Play includes separate types of applications and is divided into three subcategories: up to 5 years old, 6-8 years old, and 9-11 years old. Apps for kids should not contain external links, shopping, or other distractions. Such elements require additional protection and separation from functionality that children use, except for parental control options. Laws regarding the protection of children's privacy online should be followed. Additionally, the app should not have third-party analytics and advertising. Only services that do not transmit any identifying information about children (e.g., location, name, date of birth, email address) are allowed.
Copyright and User-Generated Content
Copyright violations are a common reason for app rejections. You can use content created by someone else only if you have official permission.If your app contains user-generated content, you should have an admin panel. The admin should be able to block and unblock users and their content. For example, YouTube regulates content that does not comply with its rules by blocking or reducing views of violent or racist content. Similarly, Instagram and many other platforms remove content about COVID-19 that doesn't align with the platform's official position.
Additional Requirements for iOS
In addition to general requirements for both the App Store and Google Play, there are two requirements specific to iOS systems: Apple ID authentication and Wallet integration for loyalty cards.
Apple ID Authentication
For apps that allow social media logins, iOS apps must offer Apple ID login if they’re targeting iOS 13 and newer.
Wallet integration
If you’re including loyalty cards in your app, ensure they come with contact information when integrated into Wallet, such as location, phone number, and email address. This is a minor detail but an important one.
To sum up
Getting your app approved might seem like a lot of work, but by following these guidelines, you’re setting yourself up for success. Be transparent, respect user data, and stick to the rules. With a bit of diligence, your app will be ready to hit the stores.
Interested in developing your mobile app? Contact us or book a quick call for a free personal consultation.
.avif)
Comments