apexcharts.js VS nivo

As a frontend dev who also works in UX and graphics from time to time, I find it helpful to be able to do both, looking at SVGs as both a vector graphics format and a human-readable XML. IME the workflow depends more on whether any SVG is meant to be illustrative (like art) or quantitative (like charts) or interactive and animated/mutable (like a game).

For something like this bell example (https://svg-tutorial.com/svg/bell), you can certainly hand-code it if you're really math-inclined and can estimate the formulas of curves just by looking at them, but for us mere mortals, it's easier to just draw out the curves in a graphics app then export as an SVG. And for things like the ringer (is that what you call it? the orange ball thing at the bottom of the bell that strikes the bell to make the sound), being able to visually draw it on a canvas, change its size, drag it around and play with its colors and dimensions, etc. is really helpful. Figma is fine for simpler graphics, but it's really more of a UX tool than a graphic design tool, and Illustrator is a lot more powerful. Inkscape is a FOSS option.

In other circumstances, though, manipulating the SVG XML directly is also very helpful. Let's say you want to programatically generate a bar chart. If you have a big dataset, it's going to take a designer forever to manually plot them and change them every time the data changes. But it's easy for a dev to use Javascript (or any language) to draw each rectangle, programmatically adjust their heights and colors based on the data, add tooltips, etc. And that way you can dynamically update them in real-time whenever the data changes (like if the user selects a different date range, or new events come in). A lot of this is made easier by libs like https://frappe.io/charts or https://apexcharts.com. But before you take that approach, you should know that for complex charts, sometimes Canvas rendering (or just generating graphics in the backend) can be more performant than SVG.

SVGs can also be animated and interactive, not just with CSS transitions but by directly manipulating the XML geometries, like http://snapsvg.io/demos/ or https://www.svgator.com/ or https://codepen.io/collection/XpwMLO/. This is fine for product pages and such, but for really graphics-intensive apps (full games) it's probably slower than other rendering pipelines. (Not my specialty, won't speculate too much.)

TLDR Drawing them in a graphics app is usually easier for the designers, but the XML can be programmatically manipulated afterward to great effect.

ApexCharts is a modern charting library that helps developers to create beautiful and interactive visualizations for web pages. It is an open-source project licensed under MIT and is free to use in commercial applications.

tradingview.com for the chart... but also apexcharts.com is a decent open source library whereas TV is not open source

ApexCharts: https://apexcharts.com/ Easy integration with Vue.

1. Apex Charts

we're using https://apexcharts.com/ in production and are reasonably satisfied with it

Check out https://apexcharts.com/

Nivo is a data visualization library built on top of D3.js and React. It offers a range of well-designed, customizable charts with great animations, making it suitable for creating visually impressive data visualizations.

When it comes to charting, Nivo makes you immediately superhero.

Since no one mentioned it, checkout nivo

Today this works thanks to nivo and Cloudinary, but that journey included a lot of trials and testing for the perfect solution.

Nivo is built on D3 and provides a variety of templates for data visualization and presentation. It is one of the few libraries that provide server-side rendering ability and fully declarative charts.

Then, we can think about the implementation. We use Nivo for most data visualizations, but we do have a few that either use straight HTML/CSS, or use D3 directly.

I always use https://nivo.rocks/ you can customize it a ton. Works great.

I use nivo.rocks to visualize the genres and make the list more interactive. Please read my comment on how I implemented it.

CRUD is just one part of the layer. It allows adding/removing/updating data. This is simply a data-foundation for an application.

Of course it feels the same across apps and industries-- it's a concrete slab upon which you build things.

Add layers on top of that, such as:

- Data visualizations. You have data from your CRUD, so do something creative with it. If you're familiar with ReactJS, check out open source, free libraries such as: https://nivo.rocks/ and https://charts.ant.design/

- Data integrations. Depending on the business you're in, experiment with integrating your CRUD app with external data sources via REST API or GraphQL. For example, a CRM like Salesforce or Marketo. Or a REST API in a particular business domain. Or a Google product which a customer might use, such as google drive.