Visual Editor

I think having a color field as the setting of environments and displaying it consistently as a small top bar or something else could really help avoiding human mistakes. It eliminates a mental load of being constantly aware of which env I am in a...

Currently there is no good way to allow defining a visible but non-editable input type. Possible usecases for this would be Custom Code function to enable/disable editing of the input field (possible role-based editing for select fields of a custo...

When building dynamic Symbols with many Content Inputs, I find that I often have a need to copy a previous Content Input and just change the name. It'd be really nice if I didn't have to go into the JSON Editor to do that and could just click a bu...

We're tracking a bunch of stuff with builder but we can't build useful metrics out of our custom tracking events. E.g. we'd like to be able to divide custom metric A by custom metric B and display the result in the insights tab.

Some CSS properties do not need to be seen by non technical members of a design team. There could be an option when registering a design token in the visual editor that lets you hide the display of the actual CSS value of a design token. For examp...

Custom components using type rich text quite a powerful tool. However it seems to be lacking 2 noticeable features. 1. the ability to control font size on rich text2. the ability to have more control over how bold text should be. Currently you can...

While using a Builder text component, it would be great if the hidden HTML tags are deleted once the text in the editor is removed.

Instead of offering choices to do different AI actions everytime I would like to have the ability to use the last one again. Ex: translating a field in a specific language

It would be great to have the color swatches be the same as your design token colors instead of having to maintain both separately. Currently, even if you have design token colors set (and strict mode), the swatches are of different (default - but...

Renaming inputs is currently a painfully awkward process since it takes quite some time for caches to update before those new names become available for use in the UI which is needed to have confidence that you're doing the right thing when updati...