Navigation in Modular Applications with Deep Linking
summary
Argues that URI-based deep links replace a brittle global navigator by letting each feature register entry points via intent filters and a catch‑all handler that routes to feature-specific processors, citing Jetpack Navigation and Deep Link Dispatch as tooling and showing OneFootball moved the heavy video player into dynamic feature modules to shrink installs. Notes limits: URIs carry only identifiers (no objects), back‑stack ambiguity unless links include context, and reflection becomes ugly when modules load at runtime.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 0:44Why modularize apps
- 3:55Module approaches compared
- 10:37Navigation patterns overview
- 12:49Requirements for navigation
- 13:10Navigation and dependencies
- 18:09Deep linking basics
- 22:47Processing deep links
- 27:03Dynamic features impact
- 32:00Resources and summary
related talks
16mNavigation in Modular Applications with Deep Linking
39mDynamic Navigation in Modularized Apps
50mAndroid Navigation at scale
30mBreaking the Rules: Dynamic Navigation in Modularized Apps
30mNavigation: deeping safely
33mBreaking the Rules: Dynamic Navigation in Modularized Apps
38mMyths about the Deep Links
33mAdventures in Navigation