Feature Ideas

This would enable end users to search/filter the table easily

Wouldn't it be amazing if there was a copy/clone button close to the Edit and Delete ones 🥺

Sometimes a part of a dashboard only makes sense to show once the user has selected an input.

To make building dashboards in the no-code builder easier, we'll introduce the concept of 'containers' to layout components on the canvas

Currently dataset filters all use simple AND across each filter. It is, however, common that you might want to use OR instead, or a nesting thereof.

It would be nice to have a variable, e.g. granularity, populate a text input, such as a chart title, so that for example a chart title can be 'Sales by {granularity variable}' and update based on the end users filters

Some teams might have their own local databases that they want to use when building locally, instead of using the connections that are set up via the connections API.

Currently the tooltip behaviour in Remarkable is to show all the values (for example in a multi-line chart this would mean all values for a particular point on the x-axis) but in some cases it would be useful to be able to toggle to just show either one or many data points. You can override the tooltip behaviour via theming but this would be nice to have as OOTB behaviour

Allow component inputs to accept custom (non-primitive) types as sub-inputs, so that developers can define reusable complex types and use non-primitive inputs - such as measure selectors - within them. Currently, sub-inputs are limited to primitive values (strings, numbers, booleans). This forces developers to flatten what should be structured, grouped inputs into explicit top-level fields as a workaround, rather than modelling them as arrays of a custom type with rich sub-inputs.

Allows for things like filter updates while viewing graphs near the bottom of a dashboard without having to scroll back to the top, change the filter, and then scroll back to your graph of interest.

A change in how we wanted the dashboard to function necessitated some variable cleanup and it was used in 12 places, I easily found 11 of them and the 12th was filtering the dataset itself and it took an embarrassingly long amount of time to find. Would be great to have an easier way of identifying where the variable you are trying to delete is used. Would also be good to be able to quickly double check which charts a variable is applied to for things like full dashboard date filters or something to ensure no components were missed.

E.g. ability to switch dimensions into rows/columns for the end user

This is a really nice feature to enable end-users to zoom in on a specific period (for example)

Drilldowns are super helpful for end users, so being able to add them within the no-code builder is really important - e.g. by opening a sub-embeddable via a modal.

End users can download their dashboard as a PDF