Help us improve UI Bakery Builder/IDE

General 🤓
1

Hi everyone!
We’re working to make our builder more user-friendly and efficient. To do that, we’d love to hear your insights:

  • Missing features: What would make your workflow smoother?
  • Friction points: Any areas that feel slow or complicated?
  • Frustrations: Recurring issues or blockers?
  • Focus Areas: What should we prioritize improving?

Your feedback is invaluable - thanks for helping us shape a better tool!

2 Likes
3

Hi, everyone,

  1. I’m using Xano as backend so I miss this integration.
  2. I’m missing kanban component for different data visualization.
  3. Some kind of actions creator would be nice :slight_smile:
2 Likes
4

Hey @dzochowski,

I don’t know Xano, but since its backend I assume you would communicate over API? If so, you can work with HTTP API actions to have that communication. If it’s some other integration like their database, you might want to propose that on UI Bakery’s feedback site.

As for Kanban components, there is already a feature request marked as Planned on said feedback site, so it will be coming soon, keep an eye on the updates.

Lastly about the action creator, this is a bit of a vague request. What exactly should be the function of this creator and what makes it different from the way actions are currently created?

2 Likes
5

I don’t like how when you have a larger JavaScript code action you end up with two scroll bars. It makes it difficult to scroll down and up.

Debugging code within a UI component is difficult as there is no way to test run it and there are no logs of the action. So, figuring out a simple typo in a UI component’s data field can be difficult.

The AI assistant only works in the actions area. It would be nice if the AI assistant was also available in other areas where we code such as the UI components.

When executing an action we now have the ability to proceed from a step. This feature is great! But, it would be nice to be able to execute a single step only.

It would be nice to choose the resolution of the main body window. I work on a high resolution screen but I’m designing for a lower resolution screen. There is no way to see how it’s going to look. The ability to change the resolution of the body window vs having it default to the full available width would be nice.

Setting up a true multi user environment where multiple devs can work on the same application at once would be nice. Right now, the devs need to communicate with each in order to prevent merge conflicts.

Having the ability to add new cards to an accordion component programmatically would be a nice feature.

It would be nice to be able to extend the content window (the far right window on the top) to a longer length. I find I’m scrolling frequently in that window and I almost never use what’s right below the execute action button. I would want to do this without making the body area bigger.

I would be glad to share more ideas if you want. Just ping me.

4 Likes
6

Thank you for the reply and suggestions! As @Max mentioned, it would be wonderful if you could provide some details on which action creator features you feel are missing.

7

Hi @Dave_Goldfein, I appreciate the comprehensive list! I’ll definitely reach out to you to go over the pain points together.

8

Hi Dmitry, one thing that would make life easier is to build a Rule Builder design paradigm component, including one with nested rules. The conditions can be normal AND, OR, XOR, NOT, <, >, <=, >= etc but you can do some database like conditions like AVG, SUM, COUNT, STD, FREQ etc. People building powerful rules based systems on UI Bakery would find this really powerful and easy. Then they can just connect to their database to store the rule etc. Obviously the parameters have to be driven by the UI, but they can model the parameters in their database etc.

1 Like
9

It would be nice if the Tree component leveraged the dynamic structure properties like forms and tables. I would love to be able to be able to say that a boolean field is represented as a check box or be able to add buttons to a leaf node. Right now to emulate this I am working with nested lists of collapsible cards, but performance begins to tank pretty quickly.

2 Likes
10

Generally love UIB. A few helpful things would be:

  • Ability to resize width of left menu bar and right hand component settings menu - Looking at a large component tree in the app structure or having longer component names that you cannot fully see in the component settings menu can be a pain. And/or could wrap the name on to a new line so can see the full name.
  • Ability to put the actions menu to the right of the component settings menu. I work on multiple large/wide screens but they are not super tall (samsung 34" and 49" Odyssey screens). Lots of width available but not lots of height so to look at both the page I am building and the action menu I end up doing a lot of vertical scrolling in both. If I could choose to show the actions menu to the left of the components setting menu I could have both full height. That would be so nice. Need to be able to toggle where you want the actions menu because I would probably need it at the bottom when I am on my laptop.
  • Ability to “zoom out” on the view of the app page so can bring the actions menu up higher but still see a significant portion of the page you are building.
  • Debugging features in actions - break points, jump in/out, variable watching, etc. Currently the only way I know how to debug is to do LOTS of console.logs and rerun the actions again and again. Ability to run a single step of an action for testing. Quick popup window when you click on the data visualizer/preview of a data input field or in results areas that shows data formatted in large window to look through so don’t have to copy, paste into other IDE, format it, and look through it.
2 Likes