Questions
New Google Play Memory & Zero-Tap Sign-In Requirements — Compliance Plan for Our App
Hello,
Our app, TERRE GUINÉE, is built with Median on top of our Softr PWA and published on Google Play. We were recently notified by Google Play of new quality requirements that affect our app, and we'd like to understand how Median plans to address them.
Two points concern us specifically:
-
Memory thresholds (enforced from February 2027): these cover dynamic memory usage, bitmap memory usage, and compiled code (DEX) optimization. Could you let us know whether Median builds already incorporate optimizations for these areas, or whether additional steps will be needed on our end (e.g. updating to a newer builder version, specific configuration settings, etc.)?
-
Zero-Tap Sign-In (enforced from April 2027): this requirement relies on the Android Restore Credentials API to automatically sign in a user when they switch devices. Does Median plan to support this API for apps wrapping a PWA? If not, do you have a recommended fallback for handling user re-authentication smoothly?
We'd like to get ahead of these deadlines and adjust our setup accordingly. Please let us know if a new build version or configuration change will be required on our side.
Best regards,
Lavile Dopavogui
Founder and General Manager, TERRE GUINÉE