wtf is voyager?

Voyager is a navigation library for Jetpack Compose, the modern toolkit for building Android (and increasingly multiplatform) app interfaces. In plain terms, it handles the "screen switching" in your app, moving from a login page to a home page, opening a bottom sheet, managing tabs like the YouTube app, or keeping track of nested navigation when you have complex flows. Instead of wrestling with navigation boilerplate, you define each screen as a simple object and let a Navigator component handle the routing. The way it works is straightforward for developers: each screen in your app is a class that implements a Screen interface, where you place your UI code. You kick things off by passing your starting screen to a Navigator. From there, the library manages a stack of screens, so you can push new ones on top, pop back, or jump between tabs, all while preserving state when things like screen rotations or activity recreations would normally wipe your data. This project is aimed at Android and Kotlin multiplatform developers building apps with Compose. If you are a solo founder or small team shipping an app and want a cleaner alternative to Google's default navigation library, this is a strong pick. It supports Android, iOS, Desktop, and Web, making it practical for teams targeting more than one platform from a shared codebase. What makes Voyager notable is its breadth of integrations and pragmatic design philosophy. It includes its own lightweight ScreenModel (similar to Android's ViewModel) for managing state, and it plays nicely with popular dependency injection frameworks like Koin and Hilt. It also covers concerns that go beyond basic routing: built-in screen transitions, lifecycle callbacks, back-press handling, deep linking, and state restoration. The README points to a dedicated documentation site for full API details, and includes sample apps with animated GIFs demonstrating each navigation pattern in practice.