AdapterDelegates VS timber

Here, this article was very formative in my growth as a developer http://hannesdorfmann.com/android/adapter-delegates/ copying things is often a symptom of not developing the correct solution. NowInAndroid is an example of recent android development

For adapters specifically it was very achievable with some cleverness https://github.com/sockeqwe/AdapterDelegates

This is an anti-pattern that was dealt with years ago: http://hannesdorfmann.com/android/adapter-delegates/

RecyclerView utilities: Epoxy, Groupie, AdapterDelegates

Most of my professional and personal projects have used adapter delegates: https://github.com/sockeqwe/AdapterDelegates

Adding flavor dependent features on a shared screen can be troublesome. The problem gets even worse when you don't want to couple app flavors to features they don't use. In this article I'll show you how we do in FootballCo using Dagger 2 Multibinding, AdapterDelegates and some abstractions.

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