Flutter-Neumorphic VS charts

3) flutter_neumorphic

If you follow web design trends, then you are certainly familiar with the term neumorphism. It relates to a new design approach that obtained quite extensive popularity in recent times. A neumorphic design implies extensive usage of shadows and gradients. Many developers find it difficult to implement UI elements with this kind of design with Flutter. If you are one of them, Flutter-Neumorphic is exactly what you need. This UI package will help you to create neumorphic UIs in Flutter apps much faster.

I probably cannot use syncfusion because of the licensing. I was looking at charts_flutter but I think they don't support curved lines. Maybe the line is smooth enough with a lot of points, I'll just try that first.

The level of features we need are only implemented in mp_chart and other library had many open issue for example charts_flutter. So as my senior preferred, we used mp_chart without null safety, we are running into many problem but we were able to solve them one by one but now this chart has IOS specific flickering issue which make chart un-scrollable which we ran into just now after a weeks of work.

Data visualization is a tricky task for any programmer. Therefore it is nice to have a good charting library in your arsenal. Charts is a charting library that certainly deserves your attention. It is designed internally at Google, though it is not the company’s official product. Written in Dart and based on Material Design, this library suits well for various data visualization purposes in Flutter apps. It supports an array of charts (bar, line, time series, pie, scatter plot, etc.) for visualizing complex data and making it more comprehensible for further analysis.

There is a simple package, developed by Google, to draw charts in your Flutter app: charts_flutter. Learn how to use it with this article by Samson Omojola.

Charting is available with this package: https://pub.dev/packages/charts_flutter

I ended up in this precidament with one of my projects because I made the mistake of depending on charts_flutter. The package itself is great but Google is pretty terrible at keeping the GitHub mirror up to date with their internal repo. That's a story for another day though...Anyway there was only one package in my project holding me back from going to null safety. Building without null safety requires passing an extra command line flag, that's why I put things off for so long but in the end I gave in. So if you want to use outdated packages in your project(that has migrated to null safety) you need to add this to basically every command: --no-sound-null-safety. So if you were running flutter run you would do it like this:

Wow ok you weren't exaggerating. Here's the refreshingly frank comment.