At first compact mode looked good but when left side is hovered it blocks the view
Is there a way to influence them to change it back? I can’t normally work.
May be create 1000 complaints to tech support asking how to change this back? I’ve made one=)
2 Likes
@emmanuel how many more statements like this does the product team need to read in order for them to reverse course?
Disappointed if literally nothing is being said here.
4 Likes
I think it’s the opposite. If the VCs had a more granular into what’s happening, and with this kind of outcry, it wouldn’t be happening.
@josh @emmanuel - why are we not hearing from you after all these complaints regarding the new editor?
3 Likes
Interesting comment.
Out of the 10s of thousands that use Bubble, it seems about 20 or so are posting on here not liking the new change.
The OP said 34,000 tried it and only 8% opted out.
I have about 400 or so workflows on a SPA with all reusables and really have had no problems.
I saw a post where someone said they had almost 400 WFs on one page. That did seem like a lot.
I don’t doubt there are those having problems. Hopefully Bubble is looking into those problems.
I don’t see a lot of the ‘coaches’ I’ve followed since I started Bubble complaining about the new setup. I did get an email from one a couple of days ago that explained how to optimize apps to alleviate most of the problems.
Also, I had thought the new design was to pave the way for even more updates to the WF editor?
3 Likes
Would be interesting to give the option to revert now, and see how many do. I suspect that 8% will be MUCH MUCH higher.
5 Likes
You may be right…
but it also seems to me (and I could be wrong), that a lot of users could optimize their apps?
I’m not an expert on the subject but I have seen some with very large apps that said they optimized and found the new editor not as bad as they thought.
1 Like
Or they can revert, fix the issues and roll it out again.
In fact when they had introduced it, lot of people had shared feedback with the points that work and the ones that don’t. They acted on some of it and ignored some. Now that it has been forcibly roled out, voices are even stronger and more.
Actually here it is just about fixing some UX issues, unlike in the page menu and editor in general where the editor is crashing or is very slow. In those cases, they need to fix the code a lot to make editor usable for people without super high end machines.
1 Like
I use a Chromebook and don’t have crashes.
Then again, I use all reusable elements.
Thankfully, I discovered the use of REs early on because using them was definitely well worth it. I believe I have maybe 50 or 60? I realize I don’t have the biggest app…but I hope as either one of my apps grow I can continue to use best practices.
I do hope you get your problems taken care of because I know it has to be discouraging to have your browser crash constantly.
First only bc you read it, it isn’t true.
Second steelmanning your argument with a SPA that takes an “all” reusables approach. It is generally easier to have less logic in one place, obviously. But that insight is independent of the new update. To make it more clear, in a reusable:
Before you could see all your max. 10 wfs in the center of your screen and easily switch between them.
Now you see nothing in the center, select one wf, edit in the center, move mouse to left, select another wf, move mouse to right. It is objectively worse bc it forces everyone to make more movements with your mouse.
I did not even talk about the backend… which is a mess (yes even if like I and many others do use folders).
2 Likes
I appreciate your feedback.
Having a SPA with all reusables is not independent of the new update.
By having all reusables I don’t have a million WFs on one page. I only have the WFs associated with the RE. Maybe I’m reading your comment wrong?
Sometimes I wonder if I’m doing something wrong because almost every time I go to a workflow it is because I clicked on an element.
I never just go to the WF area and search for workflows. But, as I said, I may not understand how others operate.
2 Likes
Wrong, bc generally having reusables for distinct and independent logic is good. However, I showed you above how even in a reusable this is causing a clear and objective reduction in productivity.
Got you, I mean if you are not doing that then I understand a bit better where you’re coming from. Makes sense.
Maybe let’s take a simpler example of say a button with 2 conditonal wfs. One fires when X is empty, another when X is not empty.
Before you were able to edit them side by side without much mouse movement
Now you have to move across almost your whole screen to switch and edit
Do you see it now?
2 Likes
Speaking for myself I have seen no reduction in productivity with either of my SPAs.
I realize I’ve only been using Bubble for about 2 years and have a lot to learn but I’m just giving my experiences.
With the button with 2 conditonal WFs if I’m understanding you right…
I have conditionals like that on several things but put them all in the same workflow.
Maybe that’s not the best practice?
Ditto for me 90% of the time that I end up in the WF editor. For the other 10%, I use the search bar to find the desired WF.
With that said, this new change has not been catastrophic at all for me. But I do understand that is just my personal experience and can understand others’ concerns…
I don’t think Bubble will roll this one back for several reasons. My recommendation to those who are upset is to take a deep breath and approach the new system from a fresh perspective. Take some time to familiarize yourself with the layout and get comfortable with it. You’ll forget about the old system in no time!
3 Likes
Part of the reason some of you are struggling with the change is that the new workflow editor is opinionated about how you build.
It is opinionated in the sense that you are now nudged to name workflows and use folders more. That does work well when you do both of those things, but is obviously not great if you haven’t done these previously.
That’s compounded by the fact that interacting with folders is still fairly janky and long conditions are truncated pretty short.
So, I’d encourage you to organise your workflows, name them, etc. Those are good practices in any codebase - you were just able to get away with it previously.
Of course, I’d like to see improvements to folder interactions etc to make this organisation easier and more natural.
5 Likes
No, VCs are incentivized to grow new users for vanity metrics than for building the best capabilities for power users. That’s why they optimized the workflow design for less complex workflows at the expense of more in-depth ones.
1 Like
Please stop trying to blame the users for this change. It’s laughable to pretend the only struggle is for people who weren’t organizing / naming their workflows.
- There are still no subfolders.
- Still only very few colors.
- Names are truncated much more now, so every naming convention used for alphabetical grouping now looks indistinguishable.
- The UX has changed. You can no longer click on the name in the property editor.
- If you create a workflow now, it doesn’t actually exist until you put actions in them, but it shows up in the tree anyway. (like wtf)
- …
1 Like
I told myself same. I m gratefull to my past me to have always renamed all wf and actions.
Plus : in the debuguer please let us have the renamed wf name instead of group xy is clicked !
2 Likes
I remember the time when you can get most 30 performance score in dev tools ( currently 60-70 max) and people were advocating how to improve it db design, image compress and so on, I thought I was the problem and solved everything still got 30.
Using reusables are irrelevant
Naming folders are irrelevant
These are productivity tools to speed you up, not the otherway around. It is Bubble problem not user problem.
This editor needs fixing
3 Likes