android-kotlin-fundamentals-apps
jetpack-navigation-ftue-sample
android-kotlin-fundamentals-apps | jetpack-navigation-ftue-sample | |
---|---|---|
3 | 6 | |
1,602 | 237 | |
- | - | |
0.0 | 2.5 | |
11 months ago | 10 months ago | |
Kotlin | Kotlin | |
GNU General Public License v3.0 or later | 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.
android-kotlin-fundamentals-apps
- Looking for a sample project: Compose, Room, ViewModel, manual DI (no Hilt)
- Can't figure out how to save a list of objects in Room
-
Things seem to be shockingly complex in Android dev now
Anyway, there is minimal Codelabs example with a tutorial. Also from my experience you might want to find and watch video with explanation - somehow it can be perceived easier than a wall of text. So maybe this or this can be helpful.
jetpack-navigation-ftue-sample
-
Any Modern examples of using only 1 activity, but multiple(lots of) fragments in a non trivial app
Not a complex example per say, but I did write this sample and it'd scale as it looks right now, just more packages in core and in features.
-
How to properly handle conditional navigation with dynamic starting destination whhen using navigation component?
The whole circus around login/logout is a mess in jetpack navigation. It assumes a world where your app always has a fixed starting point which imo doesn't make sense with apps where the entire content is behind auth. I recommend checking out https://github.com/Zhuinden/jetpack-navigation-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...
-
I'm looking for a good sample codebase to review/learn from that uses MVVM, live data, compose and either dagger or hilt. Any suggestions?
I have a non-Compose "MVVM + Hilt" sample here
-
Things seem to be shockingly complex in Android dev now
See https://github.com/Zhuinden/jetpack-navigation-ftue-sample/blob/master/app/src/main/java/com/zhuinden/jetpacknavigationdaggersavedstatehandleftueexperiment/features/login/LoginViewModel.kt#L30-L41
-
Hilt alpha 0.0.3
Yes it works wonders
What are some alternatives?
android-clean-architecture-mvi-boilerplate - A fork of our clean architecture boilerplate using the Model-View-Intent pattern
tivi - Tivi is a TV show tracking Android app, which connects to trakt.tv
guide-to-kotlin - [GUIDE] This tutorial assumes all you know is Java, but you want to learn Kotlin.
architecture-components-samples - Samples for Android Architecture Components.
flow-ziptuple-kt - [ACTIVE] Helper functions to zip Flows into 3 to 11 arity tuples, and to array.
jetflix - Movie listing app using Jetpack Compose and Tmdb api
myColors - A simple but useful app, allowing one to generate colors
android-mvvm-dagger-rxjava-retrofit - A sample project which demostrate use of MVVM and Dagger 2 with RxJava2 along with Retrofit
CocktailApp - Cocktails Android App with Clean Architecture, MVVM , Retrofit, Coroutines, Navigation Components , Room, Dagger Hilt, Cache Strategy and Coroutines Flow
compose-samples - Official Jetpack Compose samples.
live-event - [ACTIVE] Lifecycle-aware wrapper over EventEmitter, for modelling one-off events.