Setting up a new Android phone currently means signing back into a few dozen apps one at a time. Google Play is about to make that Google’s problem to fix rather than yours: from April 2027, any app on the Play Store that supports sign-in — optional or mandatory — will be required to restore your logged-in state automatically when you move to a new Android device, or lose full publishing rights and store visibility.
The requirement is called Zero-Tap Sign-In and it was announced on 26 August alongside a second, separate set of rules about how much memory apps are allowed to use. Both are Play Store policy, which means the enforcement mechanism is the same one Google always reaches for: apps that do not comply get buried.
What Zero-Tap Sign-In means when you switch phones
The mechanism is the Android Restore Credentials API, which already exists but has been optional. Google’s description of what it does:
“This API ensures that when a user opens your app on their new Android device for the very first time, they are instantly recognized and securely signed in without additional taps.” — Google Play, in its 26 August developer announcement
In practice, that turns the post-migration cleanup — banking apps, streaming apps, the one loyalty app whose password you never wrote down — into something that resolves itself as you open each app. It also closes one of the longest-standing gaps in Android’s device-migration story, where app data has long moved across more reliably than app logins.
Two caveats sit in the announcement. Games are currently exempt, with Google saying tailored guidance for gaming authentication is coming in 2027, so expect the app you most want this for to be among the last to get it. And the requirement as described covers Android-to-Android device transfers only; Google’s announcement does not discuss moving to or from another platform.
The memory rules, and why they land in February 2027
The other half of the announcement is aimed at apps that use too much RAM. Google is setting Play Store thresholds across three measures: dynamic memory usage (anonymous RSS plus swap), bitmap memory usage, and DEX code optimisation, where apps must hit a minimum of 25% coverage across optimisation, shrinking and obfuscation using R8 or an equivalent tool. From February 2027, apps and games that exceed the thresholds may see reduced visibility and publishing capabilities on Google Play.
Google is explicit about why. Its post opens the memory section by describing an industry navigating significant hardware supply constraints that are altering how much memory devices ship with, in a way that degrades the user experience over time. That is the same RAM shortage that has already pushed up phone prices this year, now producing a second-order effect: with less memory in the device, Google is rationing what apps may take from it.
This builds directly on the OS-level enforcement we covered earlier — Android 17’s per-app memory limits, which are spreading beyond Pixel to devices from 4GB to 16GB+ and which slow an over-budget app into zRAM before terminating it. The February 2027 rules add a commercial penalty on top of the technical one, so a badly behaved app now risks both being killed on the phone and being demoted in the store.
What this actually means for you
- Nothing changes today. Both deadlines are in 2027 and both are obligations on developers, not settings you can toggle.
- Big apps will get leaner, eventually. A memory threshold with store visibility attached is the kind of pressure that actually moves large apps, in a way that developer guidance alone has not.
- Phone switching should get less painful from April 2027 — but only for apps that ship an update to comply, and only on Android-to-Android moves.
- Watch what reduced visibility comes to mean. Google says additional details will be provided later this year and that it expects the thresholds themselves to change over time. A quality bar enforced by search ranking is also, unavoidably, more discretion over which apps you are shown.
The full requirements, thresholds and the new Android vitals memory metrics are documented in Google’s announcement on the Android Developers Blog.
