Its been more than a month after last few updates came on Bubble. I do not see anything new came recently. When is the next release and what new items are coming on Bubble ?. Looks like Bubble went silent after fund raised.
Please update about next release date and what.
Bubble has a roadmap. You can find it here Roadmap
The roadmap is empty 
my mistake - failed to click on the left sub menu âŚ
Itâs not empty. Also, they will publish a complete new UI/UX re-design.
I hope not! Its great as is now!
I donât agree with you here. I think that bubble miles behind in terms of design and user experience if you compare it with webflow for example. I canât wait for a redesign and I hope they do it rigorously and not just a different color scheme.
I just donât want them to âsimplifyâ it and try and make it like the Wix or Weebly for apps by removing stuff to allow for better UI.
Agree we donât want to dumb it down! But I donât think that is what they will do. The admin database management side needs a complete overhaul!
Why are you being so toxic? Goodness gracious.
A lot of additional functionality has been implemented ad hoc in the current UI and itâs not a great UX.
Some things that come to mind are the zoom , docking (anyone uses this??) and other canvas utility tools but also the complete responsive editor could use a think-through.
Some aspects are part of the builder, some only of the responsive editor which is unhandy.
Some functionally is missing and makes for a poor experience in the responsive editor. Like jumping to a group and there are more bugs in there.
Going from a group in the builder directly into the responsive settings would be great for example.
So yeah, for me itâs not so much about a slick webflowy UI redesign but a more thorough overall UX think through.
I totally agree. Everything that is under the Data tab in the editor is poor at best and needs a full redesign. To say that this is the area of Bubble with which I enjoy the least working (and had to spend a lot of time with) does not start to describe how much I dislike it.
I truly look forward to those changes!
I am not really impressed about bubble progress after they fund raised. No major updates on bubble though there are many areas needs lot of improvements example, Data module and etc. I am confused should I stick with Bubble for my clients decent investments applications.
+1 on looking forward to UX updates.
I canât really say I share the impression that Bubble has been standing still since the fundraising.
First, thereâs no reason a fundraising should mean that major updates are just around the corner. The opposite, realistically. Getting funds is great news, but I can tell you from experience that the process can steal shitloads of time and energy from a company. Lots of back and forth, legal stuff, negotiations, financial roadmaps, new board members in with new opinions, redistributing of stocks and options, not to mention that the thoughts of the entrepreneurs are all over the place, trying to juggle the product development, community and demands of the new owners.
Secondly, itâs been what⌠less than two months? We get to see the result of the new cash in the next five years, not the first 60 days. From what I know, there hasnât been a single new hire since the announcement (though I may have missed something). Cash in the bank is nice to have, but it wonât write the code for you.
Actually that is probably the one area I think they should look to open source. Give us a way to access the DB and we can build our own data management tools (SQL Server, MongoDB etc all work in this way).
Hi Nigel,
I do appreciate the value of having our own DB engine in the back, because it opens a whole new world of possibilities --and I can already hear Aladdin and princess Jasmine singing in the background!
Frankly, the issue for me is less about DB capabilities and more about Bubbleâs UI to manipulate the data. For selfish me, being able to use modern functionality to:
using a well-thought UI would be fantastic. Every time I have to use Bubbleâs Data tab (when creating a new app and loading all the reference data required to make it work or when debugging API workflows) I hit a UX designed for minimal or casual interaction. And I know that the solution for some of my problems is to write workflows that work well from the get go and require no debugging, but I havenât reached that point yet.
Ignoring the âhowâ the Bubble guys will make other DB engines work seamlessly with the Bubble language used in the Bubble Editor, these two issues come to mind:
PERFORMANCE
Iâd like to assume that running the DB engine in an environment different from Bubbleâs will only create negligible latency/performance issues. This may be a big assumption.
SIMPLICITY
One of the reasons people like me choose Bubble is so we donât have to worry about integrating with and running a DB back end. I donât need to know about PaaS or IaaS in order to instantiate a database and cross-domain authentication, or all the little things that are needed to make this puppy play. So, I hope that if Bubble goes in that direction, it makes that feature optional.
Hope this makes sense,
Alex
That was exactly my point 
I donât want to manage my own databaseâŚbut I want to be able manage my own data ⌠quickly and simply.
So like ⌠MySql Workbench or RoboMongo. But for Bubble.
I, for one, am very glad that theyâre looking at redesigning aspects of the UX. Iâm a long-time UX designer with a lot of experience with just about every design tool there is. Bubble is amazing in terms of building functional applications without the back-end know-how. The idea of Workflows and how statements are constructed is a beautifully simple thing to understand after a few minutes.
The team did a great job building a UX to accommodate them early on. It was admirable. I can even understand their decision to use absolute positioning for elements early in their life-cycle. It made sense as a move to get more users involved at an early stage, but itâs been holding them back for years now. The reason: Itâs incredibly hard to understand proprietary layout rules built by a single company with almost no documentation. Bubble basically ignored the box-model and amazing modern layout tools like flexbox and CSS grid. This, again, made sense because they built all of their layout tools when those ideas were in their infancy. Now, every major application on the planet uses flexbox.
Yes, there are other UX improvements they can make to the editor. But all of those follow from building a V2 of the editor that optionally allows users to use the box-model in a more predictable fashion (padding, margins, flexbox, etc.) instead of their current layout engine. I realize all of the existing Bubble apps wouldnât be compatible and there is no way to automatically switch apps over. But Bubble should build a box-model version and open it up to users who want to make the switch.
Webflow (and others) are already working on more complex functionality for their users. Itâs only a matter of time until Bubble has true 1-to-1 competitors in the market. Once they do, they need to be in a position to champion their UX and underlying layout approach as best-in-class. To be best-in-class, theyâll have to take this approach eventually. Webflow has proven you can gain large adoption by embracing the box-model and exposing true CSS values to end users.
As always, @emmanuel, Iâm here to help!
Another huge growth factor for Bubble moving forward will be exportability. This is tied to my previous comment. Again, Webflowâs approach is different than Bubbleâs and has helped it have tremendous growth. Because Webflow is built on web standards and doesnât obfuscate them behind a proprietary layout engine, their code exports are easily imported into other applications or extended as necessary.
From a business perspective, the impulse is to be afraid of allowing users to leave. Recurring subscriptions are obviously the name of the game. But the reality is that by enabling portability you remove a tremendous barrier to entry for new users. I use Webflow to design entire responsive web apps for a number of companies. Knowing that I can export the code and they can use it however they like is a requirement. That experience has been amazing and I continue to use Webflow because itâs simply easier and faster to create in Webflow than in a text-editor. Point being: Portability is extremely important to new users because they feel itâs a win-win scenario.
If Bubble can continue to build out scalability and infrastructure features, staying in Bubble will be easier than leaving Bubble. People will continue to pay their subscriptions, they just wonât have the initial fear (that Bubble could fold and their work would be lost or that their work canât easily be exported if they need to change direction) that inhibits them from starting in the first place.
Here is the current Bubble Team now. Seems to me they have hired a few new ones. People | Bubble
