Navigation is a core feature of every app, it has deep implications in architecture, component lifecycle, state management and restoration and presentation strategies to better adapt to the available space. In Compose Multiplatform, until 2024, there were no official libraries. In today's article we'll see how Raccoon switched from a third-pary solution (Voyager) to Navigation Compose in 2025, to end with Navigation 3 (introduced in CMP 1.10.0) in 2026. We'll briefly analyze how nested navigation, deep links and adaptive layouts were dealt with in each approach, when custom adapters were useful or not during migrations, and conclude with some consideration about how to choose libraries and use them in a future-proof way.