Tips and best practices to help you comply with Broken Functionality policy requirements
お知らせ
We wanted to provide some extra guidance to help you comply with our Broken Functionality policy.
To provide the best possible experience for Google Play users, it's important that your app installs and runs smoothly. Our Broken Functionality policy prohibits apps that crash, force close, freeze, or otherwise function abnormally.
Use the checklist below to make sure your app is compliant with the Broken Functionality policy! You should be able to answer “yes” to each question.
- Does your app install properly?
- After installing, does your app load properly?
- After loading, does your app work properly (and not crash, force close, or freeze abnormally)?
- Are the icons and buttons in your app responsive, e.g. after clicking an icon or button, does your app return appropriate content?
- Do the features in your app function properly, e.g. if your app offers a translation feature, does it show translated content properly?
Make sure that your app does not have any empty or blank pages that lack appropriate disclaimers or error messages.
We’ll reject apps that do not function as expected, so we highly recommend testing your app thoroughly before submitting to identify and fix any issues and to make sure that everything works as intended. And, to help new developers ensure compliance with this policy, we require them to thoroughly test their apps with a variety of users before submission.
Here are some resources that can help you test and monitor your app’s functionality:
- Test tracks: Use test tracks to help you identify and fix issues before launch.
- Play Console: Monitor crashes and ANR (Application Not Responding) errors in Play Console to assess your app's stability.
Think of a user trying to install and navigate the app for the first time. If a user encounters buttons or features that don't work as expected, or an overall experience that doesn't align with the app's description, it can significantly impact their satisfaction. Ideally, these types of issues are found by one of your testers before releasing it on a production track!
Remember, by catching issues early, you can help prevent your app from getting rejected (since multiple rejections may lead to your app getting suspended).
Still have questions? Post your question to this Help Community so that we can help!
情報の通知.
この質問はロックされているため、返信は無効になりました。
コミュニティのコンテンツは、確認されていない場合や最新ではない場合があります。詳細
最終編集: 2024年11月25日