Google has updated its account settings to allow U.S. users to change their @gmail.com usernames while keeping all existing account data and inboxes intact. For developers, this means that while old email addresses will remain active as aliases, apps that rely solely on email addresses for identification may face issues with account duplication or lost access. To ensure a seamless user experience, Google recommends migrating to the “subject ID” as the primary user identifier and allowing users to manually update their contact information within app settings.
Related Posts
Async Streams in WebAssembly with WasmRS
TL;DR: WasmRS is an implementation of RSocket for WebAssembly giving you reactive, async streams in and out of…
Front-end Signing and Back-end Verification in JavaScript Applications
We live in a time of offline apps, AI-generated content, and decentralized storage. In this world, guaranteeing data…
Subscribe to a new newsletter for security-aware developers!
Hi, I’m Felix from Cossack Labs. You might know me as a mascot of these cool data security…