Feature Ideas

Right now there's no way to pre-load the JS bundles for Embeddable before going to a page in the client's app that has the Embeddable in it. This is because the Embeddable loads everything within the web component. It'd be useful to be able to pre-load the bundle files so that when the user actually arrives at a page that contains the Embeddable, it hydrates more quickly, reducing overall load time. This is difficult to do manually since the bundle names are randomly generated, but perhaps something could be done on the backend to allow a consistent bundle naming scheme that would in turn allow at least some bundles to be pre-loaded?

Some end-users are quite technical and would like to be able to write their own SQL to get custom answers (Stripe Sigma is an example of where Stripe have offered a SQL interface for their customers). Embeddable could support this too, in a secure way, by using Cube's semantic SQL, built on top of Embeddable's native row-level security.

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 🥺

End users can download their dashboard as a PDF

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

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.

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

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

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

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

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.

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}

Like this (https://restpack.io/html2pdf) but specifically for your embeddable dashboards

We will support the option for customers to self-host Embeddable.