navigation-architecture

Trace deep links by following URI entry points through shared router contracts to feature-owned UI destinations. This involves navigating the three-layer model of deep link entry, shared routers, and feature providers to identify the correct Activity, Fragment, or Compose screen target.

Navigation routing works by resolving deep link routes through NavigationTargets router contracts, which are then backed by Koin FeatureProvider implementations. This bridges deep link parsing to the correct feature module hosting the final UI destination.

Yes, you can use Compose NavHost alongside legacy navigation, but you must respect Activity-to-Fragment bridge boundaries. The architecture supports verifying whether a feature is fragment-backed, Activity-only, or Compose-local NavHost based during your staged migration.

A deep link routes to the wrong target when module boundaries are broken or router contracts are mismatched. Debugging requires tracing the URI through the deep link entry, shared router contracts, and feature providers to find where the routing logic diverges from the intended destination.

The main limitation is respecting architecture boundaries across deeplink, app/navigation, and feature modules. When modifying navigation, you cannot update just one layer; deeplink Route parsing and feature hosting must be updated consistently to avoid breaking the Activity-to-Fragment bridge.