glide VS timber

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.

To try and fix this problem fast I knew I needed some sort of logging and that is when I discovered Timber and Firebase Crashlynics. I then used THIS video to set both of them up and to create a decent crash reporting system.

Timber

Do you still use the Android Timber lib? The only real pro I see is that you don't need to declare the Tag, other than that that "pro" where each call checks if debug or not I wonder why you would like to have that, I mean what I want is all debug-only logs to get stripped out from the code, and instead of calling if(BuildConfig.Debug) on each Timer.xy() call why not create an extra Application class under the debug folder where logs are activated? Just trying to figure out of this lib that actually started like 9 years ago is still needed or not really anymore. https://github.com/JakeWharton/timber

One of the options could be to setup logging to the file within the app and sync it with backend once necessary or required. This could be achieved by using library, such as Timber and setting up local file. Depending on your constraints, such as file size, you might want to include a file rotation strategy, e.g. start a new file and remove the old one.

Timber for logging

Same as in Timber