adrielcafe/voyager

🛸 A pragmatic navigation library for Compose Multiplatform

View on GitHub ↗Jump to charts ↓

adrielcafe/voyager has 3k+ stars and 150+ forks on GitHub, is written in Kotlin, and was last pushed on Jun 6, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 26 minutes ago
Added to GitGenius on September 22nd, 2026
Created on July 19th, 2021
Open Issues & Pull Requests: 196 (+0)
GitHub issues: Enabled
Number of forks: 167
Total Stargazers: 3,088 (+0)
Total Subscribers: 22 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 3.5 days
Mean response time: 57.1 days
90th percentile: 198.0 days
Tracked items: 76

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 78
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 712 days
Stale 30+ days: 78
Stale 90+ days: 77

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • enhancement (5)
  • docs (3)
  • BottomSheetNavigator (2)
  • tabnavigator (2)
  • api suggestion (1)
  • backhandler (1)
  • bug (1)
  • di: hilt (1)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Voyager is a multiplatform navigation library for Compose Multiplatform that handles routing and screen management in Jetpack Compose applications.

The tool solves the problem of managing navigation in Compose-based apps by providing a pragmatic API designed specifically for the declarative nature of Compose. It works through a stack-based navigation model that supports linear flows, tab-based navigation similar to YouTube's interface, bottom sheet navigation, and nested navigation with multiple stacks. The library integrates state management through its ScreenModel abstraction, which connects with popular dependency injection and state management frameworks including Koin, Kodein, Hilt, Coroutines, RxJava, and LiveData. It also supports Android's native ViewModel for teams already invested in that ecosystem.

Developers should choose this tool if they are building multiplatform applications targeting Android, iOS, Desktop, and Web using Compose Multiplatform. It suits projects that need type-safe navigation across multiple modules, require deep linking support, or need sophisticated navigation patterns beyond simple linear flows. The library handles state restoration after activity recreation, provides lifecycle callbacks for screen events, and includes built-in transition animations. Teams working on single-activity architectures will find the pragmatic API particularly valuable.

The project maintains active development with regular updates to its codebase. The maintainers respond to issues and pull requests consistently, indicating ongoing engagement with the community. Documentation is comprehensive and well-organized through a dedicated project website, suggesting a commitment to developer experience. The tool receives updates that address both bug fixes and feature additions across its multiplatform support.