Hello,
regarding the plans for the future, I will leave the Jmix team to answer but would like to share a few thoughts.
Atm, for a dashboard, I use the charts add-on on a dashboard view I made, with some buttons and filter drop-downs, because for this product I do not yet need a heavyweight solution such as Apache superset. After all, on the surface it looks the same - it’s a view with some charts.
Some developers need more because their customers need more - either because of the features, the amount of data processed, or a BI solution.
If a customer wants such a solution, e.g. BI where they can query the data, then they have a BI analyst that can do that for them, or they pay, for example, you.
Superset is good because it’s Apache, known, and it’s free. From that standpoint your customer doesn’t need to pay for example Crystal Reports BI or SAP, and you can offer that competitively to low and mid-tier customers, but there are costs of producing and maintaining the queries and reports.
That’s also good for you because you can have a revenue stream, probably included in the maintenance contract, perhaps with some maximum limits per month set without additional fees.
If they can’t operate it/spend additional resources, but there is a need for it, then well you can do your best to make several “static” queries and displays for them, but that’s it.
Kind regards,
Mladen