Modo 0.6.4 indexed Simple and convenient state-based navigation library for Jetpack Compose. Supports stack, multiscreen, nested navigation, arguments, and animation, with Android lifecycle and ViewModel integration.
Bring this to kpkg
This library is indexed from the KMP ecosystem and already resolves through kpkg.dev's Maven Central proxy. Maintainers can verify the namespace and publish future versions to kpkg for free hosting, real download stats, and signed-provenance pages.
Publishing coming soonMetadata
Owner ikarenkov
Stars 343
Used by —
Health —
License —
Latest 0.6.4
Repository github.com/ikarenkov/Modo
Updated 2022-05-06 Related libraries Surfaced from shared tags and platforms — no rankings paid for.
navigation ★ 6.0k
androidx Simplifies navigation between UI destinations via a consistent API, offers type-safe arguments (Safe Args), Compose and fragment integrations, feature-module support, and testing utilities. Shared: navigation, compose-navigation navigation3 ★ 6.0k
androidx Declarative navigation for Compose UIs, offering runtime and UI modules, navigation graphs, deep-linking, lifecycle-aware back stack handling, and simplified dependency setup. Shared: navigation, compose-navigation vortex ★ 46
hristogochev Stability-focused navigation library enhances Compose Multiplatform with seamless Voyager-like API integration, supporting advanced, nested, and bottom sheet navigation, screen transitions, and state restoration. Shared: navigation, compose-navigation NavState ★ 25
androidbroadcast Simple declarative navigation library represents navigation history as global state, supporting Compose, SwiftUI, and Android Fragments. Fully asynchronous and testable without UI. Shared: navigation, compose-navigation decomposite ★ 12
nxoim Router-style navigation featuring type-safe routing, view-model store with lifecycle handling, convenient view-model creation and retrieval, overlay destinations, custom animation/gesture system, and automatic nav-controller management. Shared: navigation, compose-navigation quo-vadis ★ 9
jermeyyy Annotation-based, type-safe navigation library generating graph builders and typed destinations; deep-linking, predictive back gestures, shared-element transitions, independent tab backstacks, and MVI-friendly architecture. Shared: navigation, compose-navigation How to Integrate Modo into Your App
Screen
ContainerScreen
Leaf nodes are Screens.
Inner nodes are ContainerScreens. They can contain other Screens or ContainerScreens in their
NavigationState. The root node is a RootScreen. You can have multiple roots in your app.
See How to integrate Modo for details. NavigationState defines the UI:
The initial state is defined in the constructor of ContainerScreen by navModel: NavModel<State>.
To update the state, dispatch a lambda that calculates the new state from the old one, or use the built-in extension functions
for StackScreen
and MultiScreen .
There are Screen and ContainerScreen:
ContainerScreen can contain and render child screens.
There are some built-in implementations of ContainerScreen like StackScreen and MultiScreen.
MIT License
Copyright (c) Konstantin Tskhovrebov (@terrakok )
and Karenkov Igor (@KarenkovID )
Permission is hereby granted , free of charge , to any person obtaining a copy
of this software and associated documentation files (the "Software" ), to deal
in the Software without restriction , including without limitation the rights
to use , copy , modify , merge , publish , distribute , sublicense , and /or sell
copies of the Software , and to permit persons to whom the Software is
furnished to do so , subject to the following conditions :
The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software .
THE SOFTWARE IS PROVIDED "AS IS ", WITHOUT WARRANTY OF ANY KIND , EXPRESS OR
IMPLIED , INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY ,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT . IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM , DAMAGES OR OTHER
LIABILITY , WHETHER IN AN ACTION OF CONTRACT , TORT OR OTHERWISE , ARISING FROM ,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE .