https://github.com/linx64/stackoverflow
StackOverflow - MVVM architecture | Hilt-dagger, LiveData, Flow, Retrofit, RecyclerView
https://github.com/linx64/stackoverflow
flow hilt kotlin retrofit
Last synced: over 1 year ago
JSON representation
StackOverflow - MVVM architecture | Hilt-dagger, LiveData, Flow, Retrofit, RecyclerView
- Host: GitHub
- URL: https://github.com/linx64/stackoverflow
- Owner: LinX64
- Created: 2022-09-18T16:23:19.000Z (almost 4 years ago)
- Default Branch: master
- Last Pushed: 2022-09-24T12:10:04.000Z (over 3 years ago)
- Last Synced: 2025-01-21T15:23:18.657Z (over 1 year ago)
- Topics: flow, hilt, kotlin, retrofit
- Language: Kotlin
- Homepage:
- Size: 133 KB
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# StackOverflow - Android Questions
### Introduction
This is a sample Android app to demonstrate the use-case of Flow, and LiveData together. Previously, I was using Coroutines along with LiveData, but it was time to upgrade myself.
Regarding [Flow](https://developer.android.com/kotlin/flow), a `Flow` is a type that can emit multiple values sequentially, as opposed to suspending functions that return only a single value. `Flow` is basically a **COLD** stream which means that it is on-demand and will emit the data when being observed or collected (`collect()`). On the other hand, Hot `Flow`s as `SharedFlow` and `StateFlow` act differently. They are always **ACTIVE** regardless of being observed or not! More info: [StateFlow and SharedFlow](https://developer.android.com/kotlin/flow/stateflow-and-sharedflow)
### Preview
### Tech stacks & technologies
MVVM architecture | Hilt-dagger, LiveData, Flow, Retrofit, RecyclerView, DataBinding, Glide