Dynamic Navigation in Modularized Apps
summary
Comcast implements navigation across modules by using compile-time deep links plus nesting external nav graphs and navigating with DeepLinkRequest, and by sharing state via savedStateHandle across backstack or graph-scoped view models. The team also creates shell nav destinations at runtime with a fragment navigator when the target is unknown. The solutions run in production with no obvious UI lag but carry brittle assumptions about keys and backstack shape and feel somewhat hacky under edge cases.
AI-written summary · about
chapters (12)
- 0:00Dynamic navigation intro
- 1:06Modularization complicates navigation
- 3:58Core navigation challenges
- 6:49Modular app structure
- 9:40Navigation with unknown destinations
- 11:04Deep linking across modules
- 15:18Navigation components internals
- 20:37Cohesive UX across modules
- 23:29Sharing data in navigation
- 28:27Runtime navigation unknowns
- 32:00Designing dynamic navigation
- 33:22Summary & Q&A
related talks
16mNavigation in Modular Applications with Deep Linking
30mBreaking the Rules: Dynamic Navigation in Modularized Apps
33mNavigation in Modular Applications with Deep Linking
33mBreaking the Rules: Dynamic Navigation in Modularized Apps
50mAndroid Navigation at scale
46mExploring Navigation Libraries for Compose
41mBottom Navigation Headache
38mAdventures in Navigation