Feature Ideas

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.

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.

Make it easier for Embeddable builders to organise their Embeddables using folders.

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.

We're building a set of dashboards for customers to get insights into their Embeddables, including information on unique viewers, query performance, dashboard performance, error messages, and more.

We're developing a brand-new charting library based on all of our learnings and feedback we've received from our Vanilla components. Remarkable will be made up of two parts: Remarkable Pro: a comprehensive library of beautiful, ready-to-go charting components built for Embeddable with features like theming, internationalisation (full translation & timezone support), colour-value assignment, and more 🚀Remarkable UI: the underlying set of components and Embeddable-specific functionality we've created while building Remarkable Pro, available to you to quickly build and extend your own components 🚀

Something to ease a component prop migration, or to create a template in case we go into the hundreds of dashboards. E.g. a basic import/export JSON endpoint to configure an Embeddable

It would be useful at an administrator level to avoid directly calling the caching API or republishing when we have to run some jobs to fix some data, this would allow us to open our frontend and refresh the security context.

Embeddable already allows you to override variables in your Embeddable, dynamically, when Embedding in your app. Testing this in the builder, however, is a little manual right now. This feature will allow you to define set variables for each client-context, and switch between them as you switch client context in the builder.

End users can download their dashboard as a PDF

Currently Embeddable uses UTC by default (e.g. when aggregating results by day / week / etc.). We plan to support supplying a timezone, per dashboard session, so each user can see the results in the timezone that makes sense for them. This will also involve making the caching layer timezone-aware.

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

It would be useful to be able to clone a dashboard from the live workspace to local dev preview so that it could be worked on locally

An API for retrieving the metadata for a published Embeddable dashboard: The canvas layout (position and size of each widget)The component values (input values and types for each of the component inputs)etc. E.g. GET https://api.embeddable.com/api/v1/embeddables/{embeddableId}