compose-navigation-reimagined
Decompose
compose-navigation-reimagined | Decompose | |
---|---|---|
17 | 20 | |
525 | 1,958 | |
- | - | |
7.4 | 9.1 | |
3 months 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.
compose-navigation-reimagined
-
Are Fragments in Android going to be deprecated in favor of Jetpack Compose?
Navigation Reimagined https://github.com/olshevski/compose-navigation-reimagined
- What do you use for compose navigation?
-
Compose Navigation Reimagined 1.4.0 released
Look at how deeplinks are converted into destinations/backstack here: https://github.com/olshevski/compose-navigation-reimagined/blob/main/sample/src/main/kotlin/dev/olshevski/navigation/reimagined/sample/ui/MainScreen.kt. It is all manual in comparison to the official Navigation Component, but I feel it gives developers much more control on the deeplink handling.
-
ViewModel: for UI business, not UI operations ๐ฎ
Compose navigation reimagined
-
4 reasons Jetpack Compose is better than XML
Using any of the 5 prominent community alternatives is a better approach (even though most people hoping to use the docs as if it was like, written for stable code, will muck around with their apps crashing if the user inputs a & symbol). I have this thing but I'd consider taking a look at https://github.com/adrielcafe/voyager or maybe https://github.com/olshevski/compose-navigation-reimagined
- Will Jetpack Compose Take Over XML?
-
Why using Navigation-Compose in your Jetpack Compose app is a bad idea
Also, I'll just leave it here: https://github.com/olshevski/compose-navigation-reimagined
- Show HN: Compose Navigation Reimagined โ open-source library for Android
- Compose Navigation Reimagined
Decompose
-
What do you use for compose navigation?
I use Decompose, although I also have a kmp project which that supports. I find the compose extensions providing a very easy API when integrating with compose.
-
Anyone here who uses compose-multiplatform for desktop apps, whatโs your feedback?
For one of our apps we used https://arkivanov.github.io/Decompose/ for navigation. It is mentioned in the Compose Multiplatform repo, but we found it pretty obscure to use and it has some confusing concepts built in.
-
Does View Model works with Compose?
View model is Googles recommended approach, but there are other approaches out their you can use like decompose
-
KMM: writing Kotlin API for Swift - 7 things you need to know.
When you are building your app in KMM, sometimes you need to pack some libraries along with project files in the shared module. For example if you are using Decompose you need to access it's Value class in Swift.
-
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 personally like decompose for its testability, clear separation of concerns, and apis for compose animations. Plus it's multiplatform so you can use it for other kmp targets.
-
Is MVI way to go for new applications with compose
Full discretion, all my new apps are built using mvi with MVIKotlin and decompose for the compose extensions for navigation animations. A sample project I have built with that architecture can be found here.
-
Decompose VS appyx - a user suggested alternative
2 projects | 30 Aug 2022
-
Appyx - Application mechanics for your Android apps, built on top of Jetpack Compose (Navigation)
Check out Decompose, it's multiplatform - https://github.com/arkivanov/Decompose
-
Received a job offer letter with "All inventions developed by you during your period of employment with the Company will be deemed as the property of the Company." Its a Web dev job. How would this affect my mobile app dev hobby. I occasionally publish apps/games to PlayStore.
Decompose
What are some alternatives?
voyager - ๐ธ A pragmatic navigation library for Jetpack Compose
Appyx - Model-driven navigation + UI components with gesture control for Compose Multiplatform
PreCompose - Compose Multiplatform Navigation && State Management
Cicerone - ๐ฆ Cicerone is a lightweight library that makes the navigation in an Android app easy.
Alligator - Alligator is Android navigation library that will help to organize your navigation code in clean and testable way.
koin - Koin - a pragmatic lightweight dependency injection framework for Kotlin & Kotlin Multiplatform
Bubble Navigation - ๐ [Android Library] A light-weight library to easily make beautiful Navigation Bar with ton of ๐จ customization option.
Kotlin-Multiplatform-Libraries - Kotlin Multiplatform Libraries. Welcome PR if you find or create new Kotlin Multiplatform Library.
Fragula - ๐ง Fragula is a swipe-to-dismiss extension for navigation component library for Android
compose-samples - Official Jetpack Compose samples.