Posted by Naheed Vora – Senior Product Supervisor, Android App Security
We perceive you need clear Play coverage steerage early in your improvement, so you possibly can deal with constructing wonderful experiences and forestall 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 steerage on insurance policies which will impression your app by lint warnings. You’ll see coverage summaries, dos and don’ts to keep away from frequent pitfalls, and direct hyperlinks to particulars.
We hope you caught an early demo at I/O. And now, you possibly can take a look at Play Coverage Insights beta within the Android Studio Narwhal Characteristic Drop Canary launch.
Find out how to use Play Coverage Insights beta in Android Studio
Lint warnings will pop up as you code, like whenever you add a permission. For instance, for those who add an Android API that makes use of Pictures and requires READ_MEDIA_IMAGES permission, then the Pictures & Video Insights lint warning will seem underneath 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 deciding on the venture scope to investigate. The scope will be set to the entire venture, the present module or file, or a customized scope.
Along with seeing these insights in Android Studio, it’s also possible to generate them as a part of your Steady Integration course of by including the next dependency to your venture.
Kotlin
lintChecks("com.google.play.coverage.insights:insights-lint:" )
Groovy
lintChecks 'com.google.play.coverage.insights:insights-lint:'
Share your suggestions on Play Coverage Insights beta
We’re actively engaged on this characteristic and wish your suggestions to refine it earlier than releasing it within the Secure channel of Android Studio later this yr. Attempt it out, report points, and cease by the Google Play Developer Assist Neighborhood to share your questions and ideas straight with our staff.
Be part of us on June 16 once we reply your questions. We’d love to listen to about:
- How will this modification 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 steerage, and what might be improved?
Builders have instructed 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 steerage all in one-place, decreasing the necessity to dig by coverage bulletins and subject 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 it will assist provide you with a greater coverage expertise and extra streamlined improvement.
