MPAndroidChart VS timber

I have used https://github.com/PhilJay/MPAndroidChart for a few big projects and has always had enough support for our customization needs.

I am planning to use a charting/graphing library in my App, however I have noticed that the options are pretty limited. In particular it seem like that there are many mediocre libraries and the rather promising ones (i.e. https://github.com/PhilJay/MPAndroidChart) are no longer maintained. In other words I couldn't find a framework that is both good and actively maintained.

MPAndroidChart

I'm currently making a personal project which involves using a chart. I was just wondering if there are any recent up to date libraries to use. I know of MPAndroidChart, but the Github hasn't been updated in a long time. I also recently saw Vico and was considering using that as well. Are there any other alternatives that would be a better option?

GitHub: https://github.com/PhilJay/MPAndroidChart

I want to create a simple line chart using the MPAndroidChart library with the following values:

I think MPAndroidChart is a good option. It has a large documentation which can probably help you out. I personally have never used it before but I heard from my colleague that it's a good option.

It is not limited to the tutorial. When I want to look up things on github without cloning the repo, it is basically the same: https://github.com/PhilJay/MPAndroidChart/blob/master/MPChartExample/src/main/java/com/xxmassdeveloper/mpchartexample/LineChartActivity1.java (yes, that is not the best example with only few long lines)

MPAndroidChart for charts and graphs

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