Posted by Naheed Vora – Senior Product Supervisor, Android App Security
We perceive you need clear Play coverage steering early in your improvement, so you may concentrate on constructing superb 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 that will influence your app by means of 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 may take a look at Play Coverage Insights beta within the Android Studio Narwhal Function Drop Canary launch.
The way 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 the event you add an Android API that makes use of Photographs and requires READ_MEDIA_IMAGES permission, then the Photographs & Video Insights lint warning will seem underneath the respective API name line merchandise in Android Studio.
You may as well get these insights by going to Code > Examine for Play Coverage Insights and deciding on the venture scope to research. The scope could be set to the entire venture, the present module or file, or a customized scope.
Along with seeing these insights in Android Studio, you too can 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:<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 characteristic and need your suggestions to refine it earlier than releasing it within the Secure 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 immediately with our workforce.
Be a 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 could possibly be improved?
Builders have informed 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, decreasing the necessity to dig by means of coverage bulletins and difficulty emails.
- Simply discussing potential points with their workforce, now that everybody has shared info.
- 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 it will assist provide you with a greater coverage expertise and extra streamlined improvement.
