A nice addition would be to be able to branch out in the development system and then decide what branch to deploy to production.
What happens if your are the middle of developing a new feature that changes the behavior of existing components when an urgent fix is needed in production?
You have to undo changes, perform the hotfix, deploy and start redoing.
It’s probably easier said than done I know, but one can dream
This happen to me all the time. Fortunately I’ve segregated many of the feature sets and UI views into their own workflow folders and constantly make sure the development flow of new features doesn’t screw up existing components. Would be nice though! +1
I think this feature is incredibly important for apps with any real amount of traffic or monetization. Things break and hotfixes are needed. It’s really painful to have to review the app then code the fix and push to production, then recode the same thing in the current version. Especially painful for us since we have 2 people coding, so then 1 has to stop working while the hotfix is being created / pushed.
Seems like something Bubble would want to offer on their more premium plans. It’s so valuable that I’m sure some users would upgrade to a higher version of the product just to get this feature.
That would work for me too, of course. My point is that it’s an incredibly important feature that’s noticeably missing from Bubble at this point. Not having it costs us several days of productivity each month so I’d happily pay more to have it.
Furthermore, it becomes an even larger constraint with larger development teams. As such, it creates some uncertainty around how far we’ll be able to grow/scale our team while still using Bubble. We’re not at a point where we have to make these decisions yet, but would be nice to know the feature set is in place so that we can continue to use Bubble in the future, which makes it easier for us to make larger investments in Bubble today.