Since the release of Custom Components 2.0 and Custom App, new releases mainly included updates, fixes, and improvements for these AI tools, with some (mostly fixes) for the default App.
I understand that it’s important to make new features work well, and the current focus is doing exactly that. But the question is, for how long is this going to be the main focus of new releases?
Some issues, for example, the items in ListViews not being atomic, have already been in the backlog when asked about in the community. Similarly, some of the most upvoted feature requests, like forcing page refresh on app release, have been around for approximately half a year. Some even longer.
Now, my question to the UIBakery team is basically, what does the roadmap look like? Will we be seeing new release with features and fixes for the default App in the near future, or will the main focus continue to be on the AI tools?
For fellow UI Bakery users, how do you feel about this? Are you now mainly using the Custom App and Custom Components, or is the “default” app builder still the main tool for your apps?
You’re absolutely right - at the moment, we’re allocating around 70% of our resources to developing our new AI product. This focus makes sense for us, as the AI offering is still evolving and requires significant investment in functionality and support.
The remaining 30% of our resources are dedicated to the low-code product. Our current efforts there are primarily focused on bug fixes and targeted improvements that enhance the overall stability and logic of the application.
Regarding the roadmap. Honestly, with the AI release, it’s really been a while since we went through it. I’ve planned for us to review it during the next week. We will pinpoint the main and most asked requests that align with the product, and will try to plan the development. The rest of the requests might go.
That being said, despite our current focus on AI, we are still supporting the low-code version and are not planning to deprecate it.
Hope it makes sense! Please feel free to share your concerns and questions.
I agree that it makes sense to allocate the resources this way. As you say, I can imagine that AI requires a lot of investment and effort.
Glad to hear that the roadmap will be reviewed. I hope the roadmap, or at least part of it, will be shared with the community. I think people are definitely interested in what’s to come.
It’s also reassuring to hear that it’s not planned to deprecate the low-code version. But will the resource allocation shift to a more 50/50 approach in the future? I assume you probably can only tell us more after the coming meetings/reviews.
We’re definitely using the default App. In our case UIBakery is on premise running in our labs with a tightly controlled Internet connection and eventually IT will pull the plug entirely.
So AI doesn’t happen with our UIBakery.
We’re very much interested in hooking up UiBakery with other systems in labs and engineering like JIRA or being able to react to external events, run background tasks, connect to local storage etc.
The current UI Bakery roadmap doesn’t really suit us and the new projects we would like to implement.
I had noticed that work was done in UI Bakery Roadmap and that your internal meetings presumably took place, so I wanted to see if the team could share some plans or a roadmap with the community. I think everyone would be genuinely interested!
At the moment, I’m not able to share details about specific upcoming features beyond those already listed in the roadmap under the “In Progress” section.
Our overall focus is on continuing to enhance the AI functionality and improving the platform’s overall stability. We also plan to introduce selected improvements to the low-code part of the product, particularly those that strengthen core logic and align well with the product’s direction.
As for new feature requests, we’ve agreed to review them individually and evaluate their potential impact together with the product team before making any commitments.