Cicerone — MVP Navigation Without Pain or Tears
summary
Presentation covers implementing flexible, simple, lifecycle-safe screen navigation when using MVP on Android. It shows how to keep navigation code clean and testable (unit tests for navigation logic), discusses Android navigation requirements and compares/mentions Flow and Conductor, and presents the Cicerone library as the proposed solution.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 1:03Navigation problems in Android
- 4:15Ideal navigation requirements
- 6:20Complex navigation analysis
- 7:02Navigation commands in Cicerone
- 9:05Navigator implementation
- 11:14Router command combinations
- 13:03Lifecycle problem solutions
- 14:26Cicerone library overview
- 15:28Cicerone practical benefits
- 16:53Mixed Activity and Fragment navigation
- 19:04Deep link navigation
- 20:50Activity vs Fragments approach
- 23:40Activity and Fragment creation
- 24:24Dialogs and navigation
- 26:10Q&A
related talks
49mNavigation Component, feedback from the trench
28mNavigation in a Multiplatform World
35mBuilding better Android apps with MVP
45mThe Final Word in Android Navigation
36mNavigation and the Single Activity: Learnings from a Skeptic
33mFinding Your Way Through the Navigation Framework
33mAdventures in Navigation
43mNavigation Component, feedback from the trench