Exploring Navigation Libraries for Compose
summary
Compares Navigation Compose, Circuit, and Appex by showing working code for three scenarios: bottom/navigation bar integration, logic-dependent navigation (do work then navigate), and deep linking. Navigation Compose follows the navigation principles but makes coupling view logic to nav state awkward. Circuit exposes a Navigator to presenters (presenters are composable) so awaiting logic then navigating is straightforward. Appex models navigation as a node tree with components and gives explicit, programmable deep links and good bottom bar support. Conclusion: navigation state should be application state and building a general nav library is hard.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 2:48Defining navigation in Compose
- 7:22Navigation scenarios to evaluate
- 8:24Testing Navigation Compose
- 10:10Code demo with Navigation Compose
- 17:33Deep dive and takeaways
- 17:54Introducing Circuit library
- 20:03Code demo with Circuit
- 27:17Circuit deep linking
- 27:38Introducing Apex library
- 30:50Code demo with Apex
- 38:19Comparing libraries
- 38:41Key takeaways
related talks
46mExploring Navigation Libraries for Compose
49mNavigating with Jetpack Compose
33mBreaking the Rules: Dynamic Navigation in Modularized Apps
49mNavigation Component, feedback from the trench
42mComposing your navigation: charting your route in the Jetpack ecosystem
31mModel-driven navigation with Jetpack Compose – From zero to hero
38mNavigating the future with Jetpack Navigation 3
30mBreaking the Rules: Dynamic Navigation in Modularized Apps