voyager
event-emitter
Our great sponsors
| voyager | event-emitter | |
|---|---|---|
| 12 | 9 | |
| 2,210 | 77 | |
| - | - | |
| 8.1 | 0.0 | |
| 8 days ago | about 1 year ago | |
| Kotlin | Java | |
| 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.
voyager
-
Kotlin Routing - routing everything
KMP use cases increasing, developers migrating or creating your projects to KMP, no routing system or navigation available to KMP (Except Voyager), that was the opportunity to create one.
- Are Fragments in Android going to be deprecated in favor of Jetpack Compose?
-
Why compose multiplatform don't get more popular?
If I were to start a project right now, I'd use https://github.com/adrielcafe/voyager although, it doesn't support Web Canvas or iOS yet I don't think.
-
Which navigation library for compose do you suggest?
Voyager has some bugs (apparently SavedStateHandle doesn't work and the PR is open since Nov 24), Appyx is nice but I hear it's laggy (but honestly, everything in Compose is laggy all the time, so if you use Compose, that's pretty standard tbh), I don't know enough about Navigation-Reimagined to tell you, Compose-Destinations is a codegenerator over Navigation-Compose so you drag in Accompanist-Navigation to have basic screen transitions which is pre-alpha tech.
-
ViewModel: for UI business, not UI operations 😮
Voyager
-
voyager VS Appyx - a user suggested alternative
2 projects | 19 Sep 2022
-
What's the Current State of Android Developmentâ„¢?
https://github.com/adrielcafe/voyager/issues/42 open since January
-
The State of Navigation in Jetpack Compose
Yes, I've checked (it doesn't). I've also read AndroidScreenLifecycleOwner's source code, and I don't see a way for it to ever go to the ON_PAUSE state.
-
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
-
voyager VS compose-navigation-reimagined - a user suggested alternative
2 projects | 4 Feb 2022
event-emitter
-
ViewModel: for UI business, not UI operations 😮
If you mean UI events like the events from the Model to the UI, then you can use a sealed class and a Channel or EventEmitter
-
Kotlin Flow implementation of SingleLiveEvent
I can also comment https://github.com/Zhuinden/event-emitter 😛
-
Sending View Model Events to the UI (is this how people are handling Navigation and Snackbars now?)
For events, I use https://github.com/Zhuinden/event-emitter with https://github.com/Zhuinden/live-event
-
What's the proper way of accessing a Composable function from a non-composable one?
I use https://github.com/Zhuinden/event-emitter for this sort of thing via DisposableEffect(Unit) {
-
MVVM and one shot operations
If there isn't multiple screen switches involved, I use https://github.com/Zhuinden/event-emitter
-
LiveData is superior to StateFlow for UI and ViewModel layer.
That's why I wrote EventEmitter and never had a problem.
-
What is your currently configured SharedFlow implementation ?
I use BehaviorRelay in place of MutableStateFlow/MutableLiveData, and I use EventEmitter in place of uh, SingleLiveEvent I guess.
-
LiveData vs SharedFlow and StateFlow in MVVM and MVI Architecture
Well I've been using this which is merely a lifecycle-aware wrapper over this, if you're in Kotlin and you are using coroutine stuff then you can also use Channel(UNLIMITED) with receiveAsFlow()
What are some alternatives?
Decompose - Kotlin Multiplatform lifecycle-aware business logic components (aka BLoCs) with routing (navigation) and pluggable UI (Jetpack Compose, SwiftUI, JS React, etc.)
Kotlin_Flow_To_The_View - PoC using Flow completely on an Android Projet with MVVM architecture. No LiveData. The advantage over simply using the viewModelScope is the fact that 5 seconds after leaving the application (not killing it !), the coroutine is cancelled, avoid possibly unnecessary work.
compose-navigation-reimagined - 🌈 Type-safe navigation library for Jetpack Compose
androidx - Development environment for Android Jetpack extension libraries under the androidx namespace. Synchronized with Android Jetpack's primary development branch on AOSP.
compose-destinations - Annotation processing library for type-safe Jetpack Compose navigation with no boilerplate.
navigator - A small navigation library for Android to ease the use of fragment transactions & handling backstack (also available for Jetpack Compose).
PreCompose - Compose Multiplatform Navigation && State Management
live-event - [ACTIVE] Lifecycle-aware wrapper over EventEmitter, for modelling one-off events.
compose-shared-element - Experiment with SharedElement transition in Jetpack Compose, inspired by Flutter Hero widget.
navigation-compose-typed - Type-safe arguments for Jetpack Navigation Compose using Kotlinx.Serialization
Dispatch - Automatic CoroutineDispatcher injection and extensions for kotlinx.coroutines