Jun 11, 2025

💬 Join us for Q&A on June 16: Play Policy Insights beta is here!

Announcement
TL;DR - We’ve launched Play Policy Insights beta and our Play product team will be here to listen to your feedback and answer questions!

Looking for more predictable app reviews? Today, we shared more about Play Policy Insights beta in Android Studio. This new beta feature gives you richer, in-context guidance on policies that may impact your app through lint warnings. You’ll see policy summaries, dos and don'ts to avoid common pitfalls, and direct links to details.
 
Here’s what it’ll look like:

 
To try it out, install the Android Studio Narwhal Feature Drop Canary release. Once it’s installed, there’s two ways to see the insights.
  1. Lint warnings may pop up as you code, like when you add a permission. For example 
    1. if you add an Android API that uses Photos and requires READ_MEDIA_IMAGES permission, then the Photos & Video Insights lint warning will appear under the respective API call line item in Android Studio.
    2. if you add either SDK or an Android API that uses Advertising Identifier API, then the Advertising ID Insights lint warning will appear under the respective API call line item in Android Studio.
    3. if you add an Android API that uses Background Location permission, then the Background Location Insights lint warning will appear under the respective API call line item in Android Studio.
  2. You can also get these insights by going to Code > Inspect for Play Policy Insights, then click “Analyze” in the pop-up.
For more, see our Help Center article.
 
Now, we’d like to give our community the floor! We’re actively working on this feature and want your feedback. We’re curious:
 
  • How will this change your current Android app development and Google Play Store submission workflow?
  • Which was more helpful in addressing policy issues, the lint warnings in the IDE vs lint warnings from CI build?
  • What was most helpful in the policy guidance, and what could be improved?
 
Drop a comment below, and our Play product team will respond on Monday, June 16. 
 
To ensure a focused and productive conversation, please note that we are only responding to comments and questions about Play Policy Insights beta. We will not be able to address personal support questions nor inquiries concerning Play policies generally or other Google products. Additionally, comments that do not comply with Google's Communities Content Policy may be subject to removal.

While we may not be able to address every single question directly, we promise to carefully review all submissions and share your valuable feedback directly with the product team. We can’t wait to hear from you! 
Locked
Informational notification.
This question is locked and replying has been disabled.
Community content may not be verified or up-to-date. Learn more.
Last edited Jun 11, 2025
Update
Jun 11, 2025
So far, developers have told us they like:

  • Catching potential Google Play policy issues early, right in their code, so they can build more efficiently. 
  • Seeing potential Google Play policy issues and guidance all in one-place, reducing the need to dig through policy announcements and issue emails. 
  • Continuously checking for potential policy issues as they add new features, gaining confidence in a smoother launch.

If you can’t see the Android Studio Canary release, here’s more examples of what it’ll look like:



Helpful?
All Replies (2)
Jun 11, 2025
So far, developers have told us they like:

  • Catching potential Google Play policy issues early, right in their code, so they can build more efficiently. 
  • Seeing potential Google Play policy issues and guidance all in one-place, reducing the need to dig through policy announcements and issue emails. 
  • Continuously checking for potential policy issues as they add new features, gaining confidence in a smoother launch.

If you can’t see the Android Studio Canary release, here’s more examples of what it’ll look like:



Jun 16, 2025
Thanks for your comment User 13168567540360168181! Please feel free to share additional feedback as you continue using this feature.

- Naheed, Product Manager
Last edited Jun 16, 2025
Jun 28, 2025
I am writing to bring to your urgent attention a fraudulent app listed on the Play Store named **PawramLoan**. This app is falsely advertised as a loan provider but engages in malicious practices i had see the all the  review you can also go through..ther are scammers..
 
I, along with many others, have been harassed and threatened after taking a small loan. The app takes access to sensitive data like contacts, gallery, and other personal details and misuses them. This is a serious violation of privacy and security.
 
Please investigate and take necessary action to remove the Creditlens app from the Play Store to protect other users
 
App Name: PawramLoan
Jun 12, 2025
Does Android 16 affect existing Google Play policies? If so, it would be important to have Play Policy Insights to build apps easier and efficient (and in the event if one or more of the policies on Google Play changes).
Jun 16, 2025
You're spot on! These are types of helpful insights we plan on incorporating to add to the full feature. We will show you specific Play policy insights related to your app's target API level.

Right now, Android Studio already has a lint check that warns you if the target API is too low to meet Target API Level policy.

- Naheed, Product Manager
false
14928299656755166041
true
Search Help Center
false
true
true
true
true
true
92637
false
false
Search
Clear search
Close search
Main menu