MPAndroidChart VS compose-samples

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

Source: JetNews sample app

Your concept of Android development looks to be stuck in the 4.4 days. Jetpack Compose and its declarative UI is how modern Android apps are developed.

https://github.com/android/compose-samples

>Hopefully Flutter will fix that because the difference in usability is night and day. It's just a shame the Dart ecosystem is so dead.

I don't see how the difference is night and day when they both use declarative UI's. Whether you use Jetpack Compose/Kotlin or Flutter/Dart is really up to your objectives. As for your claim that the Dart ecosystem is dead - I really don't get that, since Flutter/Dart is the #1 cross-platform development environment.

Voyager is a multiplatform navigation library built for, and seamlessly integrated with, Jetpack Compose.

This repository contains Jetpack Compose components for the Maps SDK for Android.

The official documentation provides a comprehensive guide on the basics of Jetpack Compose, components, layouts, theming, and more advanced topics.

Apparently Jetpack Compose is an Android copy of SwiftUI?

https://developer.android.com/jetpack/compose

Only two HN threads with comments: https://hn.algolia.com/?q=jetpack+compose

If you want to take a look at code, we have the Jetnews sample app that support different screen sizes. And Jetcaster also implements features such as table top mode.

check this out : https://github.com/android/compose-samples/tree/main/Crane

So I would say that instead if learning everything from Android SDK, you should just set a goal to create some app. Learn about Activities, their lifecycle, layouts (or Compose if you want to be more up to date). Try to implement your app based on this. Then improve your app using Fragments and their lifecycle. If you truly want to understand Views, which are essentially the building blocks of Android UI then I would recommend implementing your own custom View, which will have completely custom look - it is cool thing to try and you will learn how it all works inside.