live-event
simple-stack-ftue-sample
live-event | simple-stack-ftue-sample | |
---|---|---|
7 | 2 | |
63 | 27 | |
- | - | |
3.3 | 4.3 | |
5 months ago | 10 months ago | |
Kotlin | Kotlin | |
Apache License 2.0 | 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.
live-event
-
How to make kotlin library
For Android-specific code, you need slightly different configuration of the maven-publish plugin, but I use it in this repo https://github.com/Zhuinden/live-event
-
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?
ok technically I think last time I even used https://github.com/Zhuinden/live-event because I have lifecycle support via fragments in Composables
-
What do you use except SingleLiveEvent for one time actions in MVI/MVVM?
I've been using this: https://github.com/Zhuinden/live-event
-
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()
-
SharedFlow asLiveData replays emissions - expected?
I originally wrote https://github.com/Zhuinden/live-event but you can use Channel(UNLIMITED).asFlow()
-
Migrating from LiveData to Kotlin’s Flow
I wrote https://github.com/Zhuinden/live-event/ to make it easy but for some reason nobody uses it, they instead copy-paste LiveData> / SingleLiveData from Google even though it's effectively a hack
simple-stack-ftue-sample
-
LiveData vs SharedFlow and StateFlow in MVVM and MVI Architecture
A simplified variation can be seen in this repo, a LiveData variant with Jetpack stuff can be seen in this repo, my issue with this sample is that as there is no input + debounce + filter + async data load example in it, there is no switchMap (and even for combineTuple, I can use my other helper validateBy here), and those would be key to understanding the difference in terms of expressibility and power...
-
A fragment -> auth flow-> bottom navigation w/ Navigation component/jetpack
See this sample for auth / conditional navigation then pretend that "ProfileFragment" is the fragment in this sample
What are some alternatives?
SingleLiveEvent-EventWrapper-LiveData
Jetpack-Navigation-Multistack-Example - [DEMO] An example using Jetpack Navigation and bottom nav multi-stack using child fragments.
event-emitter - [ACTIVE] The event emitter allows you to register multiple observers, but enqueue events while there are no observers.
android-template - Project with various common components, to reduce "project setup" operations
jetpack-navigation-ftue-sample - [DEMO] Sample code to display "First-Time User Experience" in a Single-Activity app using Jetpack-Navigation, NavGraphs, Dagger, SavedStateHandle, Hilt, and EventEmitter - based on the FTUE example code in simple-stack-tutorials, but originally described by Google.
android-template - Android app starter template