LiquidNavBar
compose-destinations
| LiquidNavBar | compose-destinations | |
|---|---|---|
| 1 | 25 | |
| 22 | 3,061 | |
| - | - | |
| 0.0 | 9.0 | |
| over 2 years ago | 5 days ago | |
| Kotlin | Kotlin | |
| MIT License | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
LiquidNavBar
compose-destinations
- What do you use for compose navigation?
-
jetpack navigation(https://github.com/raamcosta/compose-destinations) with activity
This time is about navigation, when raamcosta ( https://github.com/raamcosta/compose-destinations) in jetpack compose
-
Compose only apps question
The biggest help of all by far was Compose Destinations. It takes away all the boilerplate of maintaining your routes. A simple way to not have to create all those routes yourself with placeholders etc, including deeplink patterns and all. It generates all of that for you in a typesafe way. Just check the basic example on GitHub or the dedicated documentation website.
-
How do you deal with complex nested navigation in Jetpack Compose?
Here is a great solution for navigation in compose. Actually this is what Google should have done in the first place https://github.com/raamcosta/compose-destinations
- New app: xml or compose?
-
Pure Compose Navigation
Compose destinations is another alternative: https://github.com/raamcosta/compose-destinations
-
A Type-safe extension library for the Compose Navigation library
Hey, thanks for sharing here. Do you mind sharing how exactly this library is different from this one https://github.com/raamcosta/compose-destinations and why one would use one over the other?
-
Single Activity Apps: Fragments vs Views in 2022
I don't have much experience with conductor, so I'm curious what your concerns about lifecycle is lacking compared to fragments? But if your team already knows that framework I might just stick with views over fragments. I see there is a compose integration if you do ever plan on picking that up with conductor. Otherwise compose makes fragments obsolete and your team already knows conductor. I do agree the navigation story in compose is not mature especially after jetpack compose navigation. But there are other 3rd party libraries like compose destinations or decompose, but would be nice to see something better 1st party.
-
Which navigation library for compose do you suggest?
I can't recommend the vanilla compose navigation from Google, but the community has built others like compose destinations which is pretty good.
-
ViewModel: for UI business, not UI operations 😮
Compose Destinations
What are some alternatives?
SSCustomBottomNavigation - Animated TabBar with native control and Jetpack Navigation support..✨🔖🚀
voyager - 🛸 A pragmatic navigation library for Jetpack Compose
mapbox-navigation-android - Mapbox Navigation SDK for Android
Duo Navigation Drawer - A flexible, easy to use, unique drawer library for your Android project.
Chip Navigation Bar - An android navigation bar widget
SlidingTutorial - Android Library for making animated tutorials inside your app
Keyboard Dismisser - Dismiss your keyboard by tapping anywhere outside it.
FragNav - An Android library for managing multiple stacks of fragments
AnimatedBottomBar - A customizable and easy to use BottomBar navigation view with sleek animations, with support for ViewPager, ViewPager2, NavController, and badges.
PagerSlidingTabStrip - An interactive indicator to navigate between the different pages of a ViewPager
RecyclerTabLayout - An efficient TabLayout library implemented with RecyclerView.
TypedNavigation - A lightweight library to help you navigate in compose with well typed functions.