Feature Ideas

In Cube Cloud you have different branches of code models, and each branch has a unique URL. We currently support pointing your embeddable:dev workspace at different URLs, but we don't support it in your primary (team) workspace yet. This idea is to support dynamically testing your Embeddable dashboards against different URLs, in your primary workspace.

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.

When connecting Embeddable to Cube Cloud (or your own Cube) we show a "refresh data models" button next to the datasets in the builder. However, in the data playground there is no such button. This idea is to add the button there too.

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.

This will allow you to dynamically control which dimension or measure to segment or aggregate by. E.g. you could have a dropdown containing a list of dimensions or measures, and then when users switch to another dimension or measure, all the charts update to show that dimension or measure.

End users can download their dashboard as a PDF

Enable builders to publish to environments such as QA, Test before publishing to Prod.

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

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

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

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

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}

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

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