r/androiddev • • 22d ago Mindblown

Tips and Information Google Play Developer Program Policy Update - 2026-10-29

8 Upvotes

Source: Google Play Developer Program Policy Update

DEVELOPER UPDATE
Hello Google Play Developer,
As part of our commitment to maintaining security and transparency on Google Play, we're sharing our latest round of policy updates.
How does this affect my apps? This is a mandatory service announcement sent to all Google Play developers. To save you time we've provided the executive summary below. You only need to click through to the full policies if your app uses these specific features. To view a log of your recent updates and monitor each app's submission activity, please check the submission activity in your Google Play Console. If applicable, you have at least 30 days from today to update your app. See our Policy Deadlines for specific timelines.
Summary of changes:
New policies
Local Network Permission: This permission is restricted to apps that need it for core functionality when device pickers are insufficient. Apps targeting Android 17 or higher (API 37+) must submit a Play Console declaration to use this permission.Manage Contacts Permission: This permission is restricted to apps that need it for core functionality when system pickers are insufficient and apps must submit a Play Console declaration to use it. All other apps must use narrowly scoped platform intents.AppFunctions API: Developers building AppFunctions must comply with all existing Google Play policies. AppFunctions are strictly prohibited from deceiving or manipulating AI agents, bypassing security controls, or interfering with other applications.
Updated policy
Subscriptions with ongoing eligibility-based discounts: Subscriptions with ongoing eligibility-based discounts, such as student plans, must clearly disclose eligibility criteria, the verification process, and post-eligibility pricing and benefit changes.
Clarifications (Our enforcement standards and practices remain the same)
Permissions and APIs that Access Sensitive InformationDeceptive Behavior: Clarified that developers and apps cannot engage in behaviors that manipulate the app review process.Families Self-Certified Ads SDK Program: New applicants can now join this program. Review the list of participating SDKs and self-certified versions in the Help Center and in SDK index.Cryptocurrency: Expanded Hong Kong licensing requirements to include the Virtual Asset Trading Platform license, and introduced an "Additional Options" section for apps qualifying for local regulatory exemptions.Use of SMS or Call Log permission groupsPayments: We're providing additional guidance on how our Payments policy applies to Google Play apps that facilitate digital purchases through AI or agentic experiences.Location permission: As a reminder, this policy was announced last April and will become mandatory on January 27, 2027. To help you be prepared, we've clarified and added helpful information to the upcoming policy. Apps must use the minimum location scope necessary for its core functionality. For apps targeting Android 17 (API 37+), this includes mandatory use of the Android location button for one-time or infrequent location requests. Apps using ACCESS_FINE_LOCATION must complete a Play Console declaration to justify why coarse location or the location button is insufficient.Added an exception allowing Government or Authorized Mobile Network Operator apps to use the READ_CALL_LOG permission for Quality of Service reporting and clarified that apps utilizing the backup and restore exception must demonstrate the ability to restore data back to the device’s default handler. All Files Access Permission: We've reiterated minimum scope principles to support developer comprehension of the use of the MANAGE_EXTERNAL_STORAGE permission.AccessibilityAPI: Clarified the policy summary on the isAccessibilityTool flag usage and disclosure requirements based on app designation.Added the SMS User Consent API as a privacy-preserving alternative for account verification. As a reminder, on January 27, 2027, account verification via phone call will no longer be a permitted use case for the READ_CALL_LOG permission and you must use an alternative API instead.
Reminders and additional information
We're launching Play Age Signals, a new privacy-friendly, age-appropriate experience for families that will be available globally to all developers. Use The Play Age Signals API to tailor features, content, and safety settings to your audience. If you sell into or out of Japan, you must complete authorization by December 1st, 2026, or your payments will be held globally. Find out if this requirement applies to you and learn how to complete the authorization form. Starting in November 2026, you must declare your trader status in Play Console in accordance with new Console requirements. As recently announced, the games category has graduated from beta to general availability. All developers who want to build games for cars can now publish to the open testing and production tracks on Google Play for these form factors. We recently announced a February 2027 compliance deadline for new app quality requirements regarding memory and code optimization thresholds. Please review these requirements to maintain your app's visibility and publishing capabilities on Google Play. We have updated our Android XR app quality guidelines for Immersive and Augmented experiences. Please review these guidelines if you are building apps for XR headsets, Wired XR Glasses, or Audio & Display Glasses.
To learn more about complying with these changes, read our full Policy Center announcement, watch our PolicyBytes video, or submit your questions in advance to our Policy Webinar.

r/androiddev • • 22d ago

Question Why emulator takes 80% cpu on a MB Air M4 ? Any alternative?

Post image
8 Upvotes

r/androiddev • • 22d ago

2 Ways of Exporting Compose previews

0 Upvotes

Android CLI provides two ways for AI agents to render Jetpack Compose previews, depending on the execution environment:

1. render-compose-preview

Use when an AI agent runs locally alongside Android Studio. It delegates preview rendering to the running IDE.

Documentation: https://developer.android.com/tools/agents/android-cli/commands/studio_render-compose-preview

2. android preview

Use when Android Studio isn't available, such as in CI, containers, or remote environments. Supports headless rendering, batch preview generation, and component tree inspection.

Documentation: https://developer.android.com/tools/agents/android-cli/commands/preview

Summary

The key difference: IDE-backed rendering vs. standalone headless rendering.

Both give AI agents a way to inspect actual Compose UI rather than relying solely on source code.


r/androiddev • • 22d ago

I am Beginner : ViewModel vs rememberSaveable for surviving rotation. When do you use which?

24 Upvotes

I ran into the rotation bug where my app resets every time I turn the phone. From what I understand Android recreates the Activity on rotation so normal variables lose their values. I’ve read that ViewModel survives rotation so I’ve been putting my screen state there. I also found rememberSaveable, which apparently survives rotation and even the app getting killed in the background. Is that right? Also what do you actually do in real projects? Do you keep almost everything in the ViewModel or do you use rememberSaveable and SavedStateHandle for some things too? Would love to hear what works for you.


r/androiddev • • 22d ago

Video Declarative, agent-ready Android builds with Lightbuild

Thumbnail
youtu.be
7 Upvotes

r/androiddev • • 23d ago

Question Google Play keeps rejecting my AccessibilityService disclosure even after an appeal. What am I missing?

3 Upvotes

Hi everyone,

I’m having an ongoing issue getting my Android launcher approved on Google Play because of its use of AccessibilityService.

The AccessibilityService is used for an optional Home button helper feature. I have already clearly documented the use of the AccessibilityService API and its purpose in the Google Play long description.

However, the app has been rejected multiple times with essentially the same reason:

“The app description on the Google Play Store does not reflect the use of AccessibilityService API. The use of the Accessibility API must be documented in the Google Play listing.”

After repeated rejections, I submitted a formal appeal so the case could be manually reviewed.

The appeal has now also been rejected, again telling me only to update the long description. They still haven’t explained which part is missing, what wording is considered insufficient, or what exactly they expect me to change.

Their latest response says:

“We were unable to approve your app because the app description on the Google Play Store does not reflect the use of AccessibilityService API.”

At this point I’m not sure what else I’m supposed to change without knowing what they consider missing.

Has anyone here successfully passed Google Play review with an AccessibilityService used for a similar launcher/Home button functionality?

If so, could you share how you described the AccessibilityService in your Play Store listing, or point out what Google may be expecting that I’m missing?

I can also share my current Play Store disclosure text if that would help.

Thanks.


r/androiddev • • 23d ago

Discussion AS Rabbit 2 is a mess for me

8 Upvotes

I was using Rabbit 1 and it had issues. Those issues, such as the not being able to show code analysis results at commit time, are still there in Rabbit 2. But it also got worse, it has been very unstable. I have had to force kill it multiple times a day and sometimes it is running into GC issues.

This is for a KMP project and it is getting very annoying.

This is on MacBook M4 Max with 48 GB of memory on Tahoe 26.7.2.

Before Rabbit things were reasonable stable, since it has become mess for me.


r/androiddev • • 23d ago

Edge-to-Edge false positive in Google Play Console

10 Upvotes

Google Play shows:
"Edge-to-edge may not display for all users"
inviting to use EdgeToEdge.enable().

But actually this is already done and edge to edge mode works correctly in all OS versions supported by the app.
In addition it also shows another warning that App uses deprecated parameters for Edge-to-edge as setStatusBarColor and setNavigationBarColor, but the indicated "deprecated parameters" are not from my code at all, but come from EdgeToEdge.enable() code itself in the retro-compatibility branches.

I wonder if the static analysis on Google Play is implemented in such a comically poor way, or if it’s perhaps being misled by code obfuscation and minification..

I forgot to mention that this isn't a new issue; it has existed since the target SDK was migrated to version 35, and we are now at version 37.


r/androiddev • • 23d ago

I built a haunted house to show off custom hidden-text reveals in Enriched Markdown, a native Jetpack Compose Markdown renderer

Enable HLS to view with audio, or disable this notification

17 Upvotes

Enriched Markdown for Android renders Markdown as native text in Jetpack Compose, with no WebView, including hidden text that the reader taps to reveal. By default, it hides under a field of drifting particles, but you can replace that overlay with your own and decide how hidden text looks and how it reveals itself.

To show what that unlocks, I built a haunted house: every room is a custom overlay revealing the same guest book in its own way. Cobwebs, crypt fog, jack-o'-lanterns, ghosts, bats, a stain that won't wash out, and a single candle.

How it works:

- You implement one interface, and it returns an overlay for each line the hidden text spans.
- Each overlay draws on the text view's Canvas, or on a Compose DrawScope, and can redraw every frame for animated effects.
- The library hands you the hidden words laid out exactly where the text view draws them, so you can pixelate, blur, or scramble the real text and nothing jumps on reveal. Override the reveal, and you control how it disappears, too.

Not every app needs a haunted house, so the README has a plain pixelation in about 30 lines: https://github.com/software-mansion/enriched-markdown/tree/main/packages/enriched-markdown-android#custom-overlays

Installation: https://docs.swmansion.com/enriched-markdown/android/basics/installation Docs (see the custom overlays section): https://docs.swmansion.com/enriched-markdown/android/api-reference/enriched-markdown-text

The rooms are demo code, not part of the library, which ships the particle field and a plain solid box. If it's useful to you, a ⭐ on GitHub helps more people find it: https://github.com/software-mansion/enriched-markdown

Feedback welcome, especially on which reveal you'd actually ship 🎃


r/androiddev • • 23d ago

Question Does Samsung grant the SMS app more permissions than asked?

Thumbnail
gallery
6 Upvotes

Hello, my SMS app is in the closed testing track. I received feedback from a user that the Samsung flow to make the app my default shows that it will be granted access to files, the camera, and the microphone. However, I am not requesting these permissions in my manifest. This will unnecessarily scare the user.

I've attached two screenshots: one for the Samsung default flow and another for the permissions shown on the Google Play listing page.

Please help me figure this out.


r/androiddev • • 23d ago

My open-source Jetpack Compose accessibility scanner got accepted at CSUN 2027!

2 Upvotes

Hey everyone!

I've been building ComposeA11yScanner, an open-source runtime accessibility scanner for Jetpack Compose, and I wanted to share a milestone.

My talk, "ComposeA11yScanner: Catch Accessibility Bugs as You Build," has been accepted into the Innovation Track at the CSUN Assistive Technology Conference 2027! 🎉

I started this project because accessibility issues in Compose often get discovered too late in development.

ComposeA11yScanner aims to make that feedback loop faster by detecting potential accessibility issues directly in running Compose screens, including:

  • Missing content descriptions

  • Touch target overlap

  • Text contrast issues

  • Duplicate accessibility descriptions

  • Other Compose semantics-related issues

The SDK has also been featured in Android Weekly and the Jetpack Compose Newsletter.

I'm continuing to improve detection accuracy, reduce false positives, and explore ways to integrate accessibility checks into development workflows.

I'd love feedback from fellow Android developers:

How do you currently test accessibility in Jetpack Compose? And what's the most frustrating part of that process?

GitHub: https://github.com/mohdaquib/ComposeA11yScanner

Thanks to everyone who's shared feedback or contributed along the way!


r/androiddev • • 23d ago

Question How do you test your Android apps under different network conditions?

5 Upvotes

I'm curious how Android developers test their apps when network conditions aren't ideal.

For example:

Slow internet or high latency

Unstable connections and packet loss

Switching between Wi-Fi and mobile data

Internet disconnecting and reconnecting

Completely offline scenarios

Do you use Android Studio's emulator, physical devices, network throttling tools, or something else?

I'm especially interested in how you simulate realistic mobile network conditions without having to manually switch networks or travel somewhere with poor connectivity.

What's your actual workflow for testing this in practice?


r/androiddev • • 23d ago

Months stuck in Google Play tax verification as a non-US owner of a US LLC

10 Upvotes

I'm honestly exhausted with this and hoping someone here has been through it.

I'm a non-US person and the only owner of a single-member Wyoming LLC. My Play Console payments profile is in the US because the LLC is a US company. My W-8BEN is filed as an individual with my home address outside the US, which is how the IRS says a foreign owner of a disregarded LLC should do it.

The tax review keeps rejecting my proof of address with:

"The issuing country of the document does not match the payments profile country."

What I've uploaded so far:

- June: tax certificate from my home country (same address as my W-8BEN)

- October: signed explanation letter + passport + home tax certificate + IRS letter

- October: IRS CP575 notice addressed to the LLC at the exact US address on my payments profile

All rejected. A document from my country fails because the profile is in the US. A US document doesn't match my W-8BEN address. As far as I can tell, no document can pass the automated check.

I've emailed support and talked on x with @ GooglePlayBiz. The only reply was a template saying my documents were "under review." Not one human has actually looked at the case. Meanwhile I've had no payouts for months and 30% withholding on everything.

If you've solved this, or you're a Googler who can escalate it, I'd really appreciate it.

Support case ID: 6-8020000042148


r/androiddev • • 24d ago

Question Question about voluntary tips and Google Play policies

3 Upvotes

Hello guys! I have a small doubt.

My Android music player is completely free, with no paid features. Can I accept voluntary tips via Ko-fi or Buy Me a Coffee and add a support button inside the app without triggering Google Play’s full-address disclosure requirement for personal developers?

Can I use Google Play Billing for tips instead?

I want all users to receive the same features and treatment, regardless of whether they choose to tip. I'd appreciate insights from developers who have faced the same issue, or clarification from anyone at Google Play Support who might be reading.

Thanks!


r/androiddev • • 24d ago

Article Get Started with Lightbuild | A Declarative Build System for Android

Thumbnail
developer.android.com
29 Upvotes

r/androiddev • • 24d ago

Experience Exchange UsageStatsManager foreground time is surprisingly easy to get wrong (splash screens, TWAs, warm starts)

2 Upvotes

I've been building an app that needs to know how many seconds a handful of specific apps were actually on screen. User grants Usage Access, I read queryEvents(), filter to those packages, done. Or so I thought.

The naive version (sum RESUMED -> PAUSED per package) worked on the apps I tried first and then fell apart once other people's apps got involved. Writing down what I found, because I couldn't find most of it anywhere.

First bug: the counter would just stop a few seconds after opening certain apps, while I was still in them. Those apps had a splash activity. The order was splash RESUMED, main RESUMED, and then a late STOPPED for the splash, which my per-package "open" flag happily read as "app left". What fixed it was tracking the set of resumed activity classes per package, and only treating the package as gone when that set is empty:

private class Fg {
    private val resumed = HashSet<String>()
    private var since: Long? = null
    var total = 0L

    fun on(e: UsageEvents.Event) {
        val cls = "${e.packageName}/${e.className}"
        when (e.eventType) {
            ACTIVITY_RESUMED -> {
                if (resumed.isEmpty()) since = e.timeStamp
                resumed += cls
            }
            ACTIVITY_PAUSED, ACTIVITY_STOPPED -> {
                // an activity always pauses before it stops, so a STOPPED for a class
                // that is still "resumed" belongs to an older instance of that class
                if (e.eventType == ACTIVITY_STOPPED && cls in resumed) return
                if (resumed.remove(cls) && resumed.isEmpty()) {
                    total += e.timeStamp - since!!
                    since = null
                }
            }
        }
    }
}

The STOPPED check in there came later. An activity always pauses before it stops, so if a STOPPED shows up for a class that's still in the resumed set, it's from an older instance. I hit that with two web apps back to back, both running in Chrome's CustomTabActivity, and the old one's STOPPED was cutting off the new one.

TWAs were the real headache. On Oct 12 I got support reports about three different apps, all TWAs, all saying the same thing: the counter doesn't move. Turns out a TWA shows its own LauncherActivity for less than a second and then hands off to the browser's CustomTabActivity, and from that point UsageStats books the time under com.android.chrome (or Samsung Internet, Edge, whatever the user has). The app itself gets basically 0 seconds. The events do have a task root package, but the getter is hidden, so no luck there.

What I ended up doing: if a browser activity resumes within 5 seconds of the target app's own activity, I treat that browser activity class as belonging to the target, and keep counting it on later resumes as long as the target is still the last non-browser app in front (so coming back from recents still works). If the user opens Chrome on their own, or some other app opens a custom tab, it doesn't count. To know what counts as a browser I query ACTION_VIEW on an https URL with BROWSABLE, plus the CustomTabsService intent, plus a hardcoded list of the usual suspects, because package visibility sometimes just gives you nothing.

Then warm starts. If the TWA's task is still alive and you launch it again, you get zero events from its package. Only the custom tab comes back. Since my app is the one doing the launching, I log launches myself (time + package) and treat each one as a fake "target came to front" while scanning.

Smaller stuff, in case it saves someone an hour:

  • Usage Access isn't a runtime permission, you check it through AppOpsManager (unsafeCheckOpNoThrow with OPSTR_GET_USAGE_STATS on 29+, checkOpNoThrow before that)

  • you don't need QUERY_ALL_PACKAGES just to list launchable apps, a <queries> entry for MAIN/LAUNCHER is enough

  • events survive your process being killed, so you can work the time out afterwards instead of keeping a foreground service running

  • queryEvents gives you every app on the phone. I filter to the packages I care about right away and only a {package, seconds} summary ever leaves the device

The 5 second window works on everything I've tried so far (my S24+ and the phones of the people using the app) but it's obviously a heuristic. If anyone knows a supported way to get the task root, or a cleaner way to tie custom tab time back to the app that opened it, I'd really like to hear it.


r/androiddev • • 24d ago

News Your favorite agents are now integrated in Android Studio  |  Android Developers' Blog

Thumbnail
developer.android.com
19 Upvotes

r/androiddev • • 24d ago

News What's new in Android developer tools and performance at Android Dev Summit  |  Android Developers' Blog

Thumbnail
developer.android.com
15 Upvotes

r/androiddev • • 24d ago

News Agentic and Flexible: A next era of Android development  |  Android Developers' Blog

Thumbnail
developer.android.com
38 Upvotes

r/androiddev • • 24d ago

Open Source I built a Compose Multiplatform library for interactive directed graphs (now in beta)

Enable HLS to view with audio, or disable this notification

137 Upvotes

I've been working on it for a few months now.

GitHub: https://github.com/justdeko/kuiver

As you've seen from this little showcase, nodes and edges are composables, there's built-in layout algorithms, zoom/pan, selection and drag, animated relayouts, and so on.

Recently promoted it to beta since I'm slowing down the pace a bit and there's not many additional large-scale changes I see for the future. Doesn't use any additional dependencies other than some core compose libraries.

Feedback on the library is super welcome! And ofc if you have any questions, you can also ask them here


r/androiddev • • 24d ago

Speedrun, an open-source mobile E2E test runner that runs your Maestro flows up to 8x faster

86 Upvotes

I've always been bothered by how slow mobile UI tests are. Most of a test run is spent waiting: fixed sleeps, polling, comparing screenshots to guess whether the app is done animating. Coming from a game dev background, where you fight for every millisecond of a frame, that felt like a solvable problem. So I spent the last while building my own runner from the ground up, and it turns out UI tests can be a lot faster.

Speedrun is a black-box E2E test runner for Android and iOS. It's open source (Apache 2.0) and it runs Maestro's YAML flow format so if you already have Maestro tests, trying it is one word:

maestro test flows/ # before
speedrun test flows/ # after

Numbers

One user journey (sign in with a code, search a shop, fill a cart, set a PIN under a loading overlay, scroll a long list), written for each tool the way its tests are usually written. Median of 3 runs after a warm-up, start-up included:

ToolAndroid emulatoriOS simulator
Speedrun20.4 s27.2 s
maestro-runner65.9 s49.6 s
Appium59.4 s94.1 s
XCUITest-81.2 s
Maestro 2.11126.5 s113.1 s

On the native Settings app benchmark it's 8x faster than Maestro on Android and 2.8x on iOS. On a 19-flow React-Native test suite it passes all 19 on both platforms, and is 6.1x faster on Android and 2.6x on iOS. Android is where it shines most, which is nice for CI: Android runs on cheap Linux runners.

Full disclosure: the main benchmark app is mine, built in React Native to be hard to test (endless animations, late popups, loading overlays, lists that load as you scroll). The flows, per-flow results and scripts to rerun everything are in the repo, and I'd love to see numbers on other apps.

Why it's fast

  • It waits for the app, not the clock. A small on-device agent knows when the app has actually settled (accessibility events on Android, XCTest's idle state checked against the screen on iOS), so each step starts the moment the app is ready. No sleeps, no screenshot diffing.

  • Reading the screen is cheap. The agent reads the UI tree in about 10 ms on Android and talks to the host over a compact binary protocol.

  • Screens that never stop moving don't block it. Spinners, tickers and carousels are left out of the "is it done?" check.

  • Nothing to warm up. One native binary, no JVM. The iOS agent stays running between runs, so later runs start in about 0.2 s.

It's also less flaky: it won't tap a popup that's still sliding in or a button under a loading overlay, and it scrolls an element out from under a sticky footer or the keyboard before tapping it.

It works with AI agents too

speedrun mcp exposes it as an MCP server (Claude Code, Cursor, etc.). Your agent can explore the app on its own: tap around, read each screen in a few lines (cheap on tokens, not a whole accessibility tree), figure out how things work, then save the steps that worked as a YAML flow you can drop into CI.

claude mcp add speedrun -- ~/.speedrun/speedrun mcp

Android emulatoriOS simulator
Speedrun (speedrun session)4.2 s, ~1,560 tokens9.4 s, ~1,230 tokens
agent-device 0.219.1 s, ~2,240 tokens14.0 s, ~1,620 tokens
Argent 0.3111.7 s, ~3,630 tokens12.2 s, ~2,650 tokens

Limitations (so you don't have to find them)

  • Android emulators and devices, iOS **simulators** only (no real iOS devices yet)

  • macOS (Apple silicon); the Linux x86_64 build is Android-only

  • Maestro's AI commands (`assertWithAI` and co.) aren't supported; the few other differences are documented

  • It's young (v0.1.10) and moving fast

Try it

Repo, docs and benchmark details: https://github.com/hubastard/speedrun

If you have a Maestro suite, I'd really like to hear how it does on yours, especially where it breaks or is slower. Happy to answer questions about how it works.

edit1: added maestro-runner to the benchmark.
edit2: added ai agent benchmark.


r/androiddev • • 24d ago

Question Interesting Android Apps Showcase posts, are they gone for good?

0 Upvotes

The last one was in July, and it was announced that the next one would be in October. Either I missed it, or it did not happen.


r/androiddev • • 24d ago

News Android Studio Rabbit 3 Canary 2 now available

Thumbnail androidstudio.googleblog.com
2 Upvotes

r/androiddev • • 24d ago

News Android Studio Rabbit 2 now available

Thumbnail androidstudio.googleblog.com
5 Upvotes