guide-to-kotlin VS tivi

Read through https://github.com/Zhuinden/guide-to-kotlin/wiki and you'll know Kotlin. That, and you can also check the collection APIs which are pretty much the best thing in Kotlin compared to Java.

I would recommend learning Kotlin for Android though, it does help. I wrote this guide https://github.com/Zhuinden/guide-to-kotlin/wiki but you can also look at this video https://www.youtube.com/watch?v=wuiT4T_LJQo

I wrote this guide for Java => Kotlin a few years ago, other than me not adding coroutines it still holds: https://github.com/Zhuinden/guide-to-kotlin/wiki

Check this guide by me to learn Kotlin: https://github.com/Zhuinden/guide-to-kotlin/wiki

but you can read through https://github.com/Zhuinden/guide-to-kotlin/wiki and you will know what you need to know for Kotlin basics (except coroutines, then you watch https://www.youtube.com/watch?v=6P20npkvcb8 )

I wrote https://github.com/Zhuinden/guide-to-kotlin/wiki a few years ago for people who know Java and don't know Kotlin, I've heard many positive feedback for how simple it is to transition from Java to Kotlin once reading through it.

you should probably look into Kotlin (see https://github.com/Zhuinden/guide-to-kotlin/wiki and/or https://www.youtube.com/watch?v=wuiT4T_LJQo ),

You actually can just read through https://github.com/Zhuinden/guide-to-kotlin/wiki and you'll know how to use kotlin lo

I wrote this guide a while ago specifically to cover this kind of migration https://github.com/Zhuinden/guide-to-kotlin/wiki it should be fairly no-nonsense and I've heard people like it (they said it helped them).

I didn't need to because by the time it came out I already knew Kotlin, personally I wrote this https://github.com/Zhuinden/guide-to-kotlin/wiki

Look no more: https://github.com/chrisbanes/tivi

It's definitely the most verbose part of our app and one of the weakest parts of the Jetpack library. We used https://github.com/chrisbanes/tivi for some inspiration on how to organize your navigation structures.

I have considered a few variants around this route. One easy way out would be just to launch a ComponentActivity with a PreferenceFragment like what Chris Banes does in TiVi ... but if you go with PreferenceFragment(Compat) it seems you are kinda stuck with SharedPreferences. If one attempts to supply DataStore wrapped in PreferenceDataStore, it seems types get messed up (TextPreference will store as a String, even if the InputType is number, etc).

Thanks I think what's confusing is that UI events are recommended to be modeled as Flows, which I guess is why Tivi uses Flows for even the simplest actions, but it does a lot of very fancy things. Most repository interactions seem to have an entire class extending an Interactor (e.g.) which catches and emits errors, progress and handles timeouts and does all that crazy queuing stuff with UI "messages" Flow

I would read and study nowinandroid and tivi apps.

Check out the approach from tivi https://github.com/chrisbanes/tivi/blob/main/app/src/main/java/app/tivi/AppNavigation.kt as an idea.

They probably want you to do a module split like in https://github.com/chrisbanes/tivi or https://github.com/igorwojda/android-showcase, but what they probably don't realize is that modularization is a trade-off, namely greatly increased build configuration complexity for... well, having modules.