I’m sorry this is way to confusing and unpredictable. I feel like I have wasted years developing on Bubble. Like many others I feel let down. If I am correct and my pricing is going up 10x I will spend the next 18 months rebuilding. I just can’t work like this. Such a sad day.
8 Likes
I moved an app from Bubble to Azure app service using Node/Svelte last time they raised their prices and it worked out pretty well (and more predictable in terms of performance/pricing).
2 Likes
Me too
how did you do that?
Did you fully rebuild everything?
It’s super disappointing to hear that. Do you think had it been built on a wappler or flutter flow (+ xano etc) they would have thought differently?
1 Like
Yes. And it surprisingly easy when you have already tested out your ideas and verified which logic and ui/ux that works best for you in Bubble.io.
1 Like
Yes, not sure about Wrappler (haven’t researched them much. Maybe it’s just their name, I hate their name lol), but FlutterFlow would have been fine as we’d have just been built in flutter and FlutterFlow was just the tool we used to write the code. Their dev team could have chosen to just work directly with the code if they didn’t want to use FlutterFlow to continue development.
I’m still up in the air about Xano.
Xano is technically still a vendor locked platform (though they claim to be working to fix that by allowing exportable ”markup” for everything on their platform), but it’s a little different than Bubble since it’s only the backend and they allow for code in lambda functions. You can export your database records whenever you want, they can’t hold onto that, so there’s freedom there, but their equivalent to “backend workflows” is different.
If you were to mostly use ChatGPT to write python for their lambda functions instead of using their internal function building tools then that would also be something you could take if you ever left. So with that approach, Xano might be a good option.
That being said, if all you’re doing is housing the database, and hosting lambda functions, how much value is Xano delivering that you can’t get just from going straight to AWS or Google cloud? Is it just auto-generated API documentation?
Talking out my ass here because I haven’t actually used or tested Xano yet, but this is my understanding from the research I’ve done so far, which includes talking to their sales team for about an hour yesterday. Maybe someone with more Xano experience can step in and comment?
1 Like
so you had to learn javascript/html/css?
It’s pretty simple: This pricing model is not sellable. You cannot tell the customer in advance what it will cost. After all, you do not know in advance what the WU is of what you are going to build. And uncertain costs is exactly what you don’t want as a company. In many cases, bubble will no longer be an option for agencies (and direct customers).
Bubble brings agencies into big trouble with this model. But also herself. I’ve experienced this exact situation before with another platform. In theory, workload pricing is a fair and logical model, but in practice not at all. The numbers plummeted as soon as they implemented the model and never recovered. Customers, apparently, just won’t understand it and won’t accept it. So my advice to bubble; reconsider your proposition. Take it from an “experience expert”. Thank me later. 
4 Likes
This is possible of course but needs backing by user wanting it and investors willing to invest and there is until now a lot more talking than action and commitment. But the group on telegram is growing that does want something else 
it is also hard to digest the fact they released this before a long weekend.
such major anouncement can be done on Monday and must be backed with competent bubble staff suppporting the community because as we see there is sooo many questions.
if they event thought that this would all pass, by the time they start working, then it unforgivable.
but i dont want belive or speculate here.
but how ever, then i ask my self - why release this on a just before the weekend.
im working on updating my app and planing for new business - also during the Weekend - and since im lost and paralyzed, i havnt been able to do anything.
even people around me are asking whats up with me.
9 Likes
Usually, when something bad happens, organizations tend to share the news on Fridays. One reason is that it allows organizations to get the news out before the weekend, giving people some time to digest the information before the start of the new week.
It seems like Bubble knew that most users would react negatively, but went ahead with their decision anyway. To try and turn things around, they had influencers make videos and write approved by bubble articles as part of their strategy to create a more positive response.
I also believe the WU pricing should be reconsidered. But it is clear to me that Bubble made a clear decision to focus on high-paying customers from now on.
4 Likes
I really like Xano as a no-code backend and had already migrated back-end from Bubble. For my case it has great value-add is in its no-code API and backend workflow builders and user friendly database Ux. And I believe from what you write that you could do what you describe just fine. That said, based on your situation - which is far more advanced than mine - e.g. if you plan to write lambda functions/Python anyway and have an eye on acquisition by no-code-suspicious enterprises, then AWS or Google Cloud might be a better solution for you.
1 Like
true some companies use that practice. but that doesn’t make it acceptable.
I also have to say that i learned a lot of things during crises. not that it is dangerous to be locked, i knew that from the start but i didn’t think would end up like this.
reading how so many people( alot alot) are scared and worried about their daily bread or how to continue to pursue their dreams. but also how people are worried because of the uncertainty.
i know this was the case but not just to this extent. this is an experience i can use in the future as well.
I think that to regain customer confidence Bubble would now have to do 2 things:
-
Change this new pricing structure assessing the massive feedback given in the past days.
-
Remove their vendor lockdown once and for all.
2 Likes
Almost 1600 negative comments since the announcement VS 700 on the last year backlash.
Just saying…
Not talking about the hundreds of negative comments on the no-code & bubble french communities
3 Likes
essa atitude do bubble é decepcionante, aumentar o preço é compreensível, agora as limitações não fazem sentido, se continuarem com essa política, teremos que utilizar os 18 meses para migrar para outra plataforma. bubble parabéns pelo tiro ne pe
4 Likes
But there are also Bubble employees who built a side business on Bubble
I wonder what they all think
2 Likes
@aj11 I guess I can stop obsessively checking to forum to see what other Bubble entrepreneurs are going to do. You have validated every fear/concern I have had over the past 3 years. You’re right. Of course you’re right. Low code/no code is a nice tool to try out MVP’s or whatever, but ultimately it is an impediment that will cause legitimate startups to fail. All this talk of which no-code platform to move to instead of bubble is meaningless.
I hate having to move to “traditional” development. I’m not a developer and I’m probably too old to learn. But it needs to be done.
At least now I can now look forward not having to say the word “Bubble” with a straight face when trying to explain to people what the hell it is I do. What a stupid name.
11 Likes