Building simple and secure account systems on Android
summary
Research shows over half fail to authenticate on sign‑in screens; the talk demonstrates concrete fixes: ask for the identifier first (email lookup to decide sign‑in vs sign‑up), merge sign in and sign up UIs, use Smart Lock hint requests and Google/Facebook SDKs to autofill verified names/emails, adopt one‑tap password‑less email links or OAuth with access/refresh tokens to keep sessions, and measure dropoff per field. Example: replacing bespoke stacks with Firebase Auth reduces thousands of lines to a few SDK calls, simplifying cross‑platform work.
AI-written summary · about
chapters (12)
- 0:00Start
- 4:45Sign Up
- 6:13Get a Recovery Email
- 9:09Asking at the Right Time
- 10:27The Value Proposition
- 17:30Runkeeper
- 18:38Password Field
- 23:27What Does Account Linking Mean
- 28:11Firebase
- 28:22Build a Sign-In Screen
- 34:04Can You Recommend a Solution for Two-Factor Authentication
- 34:20Two-Factor Authentication
related talks
30mBest practices for using sign-un for Android apps
52mAuthentication, Authorization, and You...
40mThree New Ways to Secure Your App with Firebase Authentication
53mA More Secure World for Android Apps
15mAndroid solutions for seamless sign-in across devices
46mA More Secure World for Android Apps
42mUser Identity and Sign In with Google
36mOAuth Done Right: Secure Authentication for Androi…