Posted by Naheed Vora – Senior Product Supervisor, Android App Security
We perceive you need clear Play coverage steering early in your growth, so you may concentrate on constructing superb 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 steering on insurance policies which will impression 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 may try Play Coverage Insights beta within the Android Studio Narwhal Function Drop Canary launch.
How one can use Play Coverage Insights beta in Android Studio
Lint warnings will pop up as you code, like whenever you add a permission. For instance, should you add an Android API that makes use of Images and requires READ_MEDIA_IMAGES permission, then the Images & Video Insights lint warning will seem beneath the respective API name line merchandise in Android Studio.
You can too get these insights by going to Code > Examine for Play Coverage Insights and deciding on the mission scope to investigate. The scope could be set to the entire mission, the present module or file, or a customized scope.
Along with seeing these insights in Android Studio, you may also generate them as a part of your Steady Integration course of by including the next dependency to your mission.
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 need your suggestions to refine it earlier than releasing it within the Secure channel of Android Studio later this yr. Strive it out, report points, and cease by the Google Play Developer Assist Neighborhood to share your questions and ideas straight with our staff.
Be a 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 growth 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 might 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 challenge emails.
- Simply discussing potential points with their staff, now that everybody has shared data.
- Repeatedly checking for potential coverage points as they add new options, gaining confidence in a smoother launch.
For extra, see our Google Play Assist Middle article or Android Studio preview launch notes.
We hope options like this can assist provide you with a greater coverage expertise and extra streamlined growth.
