Building a Delightful (Enterprise Grade) Login Experience
summary
A 1.5 year rebuild targets fewer drop-offs by making email confirmation the first step, adding a native two‑factor flow and an open email app button to cut login loops. Engineering shifts replace brittle RxJava presenter chains with Kotlin sealed classes and clearer result events, and a new workspace picker surfaces pending enterprise workspaces. Implementation uses RxJava, Kotlin, MVP migrating toward MVVM ideas, Espresso + robot-pattern tests and end-to-end suites; analytics show 80% of users have one account, validating the simplifications.
AI-written summary · about
chapters (23)
- 0:00Introduction and welcome
- 1:10Legacy login experience problems
- 2:18Product challenges and goals
- 3:00Inverting the authentication flow
- 4:02Authentication request flow explained
- 5:25Designing the new login experience
- 6:31Feedback and customer insights
- 6:53Optimizing for the majority
- 7:35Workspace selection screen
- 8:18Two-factor authentication improvements
- 8:39Technical challenges with RxJava
- 10:03Adopting Kotlin and sealed classes
- 11:08Error handling in login flow
- 12:34Why login experience matters
- 13:19Q&A session begins
- 13:39Advice on refactoring legacy apps
- 14:43Handling new login methods
- 16:09Testing strategies for login
- 17:12Customer involvement in testing
- 18:16Architecture improvements
- 20:26MVP in legacy app
- 21:08End-to-end testing tools
- 22:12Closing remarks
related talks
14mBuild a signup flow that doesn't suck
19mBuilding Managers Over 3rd Party SDKs for Easy Access
17mBest Practises for Android Development as a Daily Business
35mBuilding Effective Developer Experience
29mImplementing Multi-Login
35mThe real face of functional testing
15mEnhancing Developer Productivity with UX
33mMake your Android Studio Plugin