User Identity and Sign In with Google
summary
Sign-In with Google now ships as a simplified three-step flow in Google Play Services (account picker → optional scope consent → app) and adds a backend-safe ID token that apps requestIdToken from the client and validate server-side with the Google ID token verifier library. Cited numbers: 86% dislike new passwords, 54% abandon sign-ups, phishing research shows ~156M phishing emails/day producing ~80k successful credential thefts/day. New API reduces UI friction and prevents middleman spoofing by exchanging verifiable tokens.
AI-written summary · about
chapters (19)
- 0:00Start
- 7:13Making It Easy To Code
- 9:13Ux
- 11:03Sign-In with Google
- 11:55Security
- 13:58Phishing Scams
- 14:54Spam Filters
- 16:33Most Phishing Scams Have a Link in Them
- 19:57Unusual Activity Alerts
- 21:09Developer Story
- 21:44Create a Gso
- 22:37The Google Api Client
- 24:23Create a Google Sign-in Result
- 31:15Step Three To Get the Sign-in Intent
- 33:02Google Id Token Verifier
- 35:13Resources
- 36:21Sample Code
- 37:35Age Restrictions
- 39:25Android Permissions
related talks
30mBest practices for using sign-un for Android apps
37mBuilding simple and secure account systems on Android
40mGoogle+ Sign-In for Android Developers
01h 26mInteractive Session: Bridging the gap between the tech and the user
41mUsing Credential Manager starting with Google Sign-in migration
36mProtecting Users from Deception
27mPasskeys on Google platforms: updates on latest features and real-world successes
24mPasskeys and digital identity best practices