Posted by Naheed Vora – Senior Product Supervisor, Android App Security

We perceive you need clear Play coverage steering early in your improvement, so you possibly can give attention to constructing wonderful experiences and stop surprising delays from disrupting launch plans. That’s why we’re making it simpler to have smoother app publishing experiences, from the second you begin coding.

With Play Coverage Insights beta in Android Studio, you’ll get richer, in-context steering on insurance policies which will influence your app by means of lint warnings. You’ll see coverage summaries, dos and don’ts to keep away from widespread pitfalls, and direct hyperlinks to particulars.

We hope you caught an early demo at I/O. And now, you possibly can try Play Coverage Insights beta within the Android Studio Narwhal Characteristic Drop Canary launch.

Methods to use Play Coverage Insights beta in Android Studio

Lint warnings will pop up as you code, like once you add a permission. For instance, in case you add an Android API that makes use of Pictures and requires READ_MEDIA_IMAGES permission, then the Pictures & Video Insights lint warning will seem below the respective API name line merchandise in Android Studio.

You too can get these insights by going to Code > Examine for Play Coverage Insights and choosing the undertaking scope to research. The scope will be set to the entire undertaking, the present module or file, or a customized scope.

Along with seeing these insights in Android Studio, you may as well generate them as a part of your Steady Integration course of by including the next dependency to your undertaking.

Kotlin

lintChecks("com.google.play.coverage.insights:insights-lint:<model>")

Groovy

lintChecks 'com.google.play.coverage.insights:insights-lint:<model>'

Share your suggestions on Play Coverage Insights beta

We’re actively engaged on this function and wish your suggestions to refine it earlier than releasing it within the Steady channel of Android Studio later this 12 months. Strive it out, report points, and cease by the Google Play Developer Assist Group to share your questions and ideas instantly with our staff.

Be part of us on June 16 after we reply your questions. We’d love to listen to about:

• How will this transformation your present Android app improvement and Google Play Retailer submission workflow?
• Which was extra useful in addressing points: lint warnings within the IDE or lint warnings from CI construct?
• What was most useful within the coverage steering, and what may very well be improved?

Builders have advised us they like:

• Catching potential Google Play coverage points early, proper of their code, to allow them to construct extra effectively.
• Seeing potential Google Play coverage points and steering all in one-place, lowering the necessity to dig by means of coverage bulletins and problem emails.
• Simply discussing potential points with their staff, now that everybody has shared info.
• Constantly checking for potential coverage points as they add new options, gaining confidence in a smoother launch.

For extra, see our Google Play Assist Heart article or Android Studio preview launch notes.

We hope options like this may assist provide you with a greater coverage expertise and extra streamlined improvement.