tivi VS glide

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.

Do you mean what I use to show the images? I am using the Glide library, you can find more information here: https://github.com/bumptech/glide

as mentioned in the other post i don't have too much insight in the art loading because its using https://github.com/bumptech/glide for all image loading. Resolution is the only thing i know for sure can prevent an imagine from successfully loading, whether or not that resolution is fixed or if its dependent on the device I have not been able to determine

Ah, yes, downloading images as a files works completely differently from displaying images and it doesn't use any cache. Though in theory you could rewrite downloading logic to use the same mechanism as display (which is Glide)

Glide

You can also take a look at Coil, Picasso or Glide which usually have some kind of crossfade animation when the image loads.

GitHub: https://github.com/bumptech/glide

Image loading: Glide, Picasso, Coil, Fresco

Shortly said, they use React generally with fast-image and Glide for better loading of images Hermes JS Engine for app optimization. The app itself seems to generally use Kotlin and a few Java libraries and they also implemented Sqlite but I'm not sure about the use case for it probably they use it for progress though (The Developer/Marketer needs to confirm this), lastly they seem to use IntellJ Idea for programming and probably compiling

If you see a file like this: https://github.com/bumptech/glide/blob/master/library/src/main/java/com/bumptech/glide/RequestBuilder.java tell me that your eyes don't immediately go to the comments first instead of the code.