No it can not. According to Bubble’s own findings, most impacted apps can see a 30-40% reduction. And that’s with the people who knows the ins and outs of the system… not you. So let’s be nice here and assume you can achieve the 30%… you’ll still be looking at 2,100,000 WU… nowhere near the included amount in the plans. It’s ridiculous, please don’t pretend this is in any way defendable.
14 Likes
The Workload usage is pretty straightforward. You get charged for most interactions in both the development and live version. Such as: workflows, page loads, api calls, uploads, and fetching data.
In theory it would be possible to map out the workload usage for workflows, api calls, fetching, etc. However, it is near impossible to predict user behavior such as:
-
how many times will they load a page.
-
how many times will they add or change data.
-
how many times will a workflow be triggered.
-
how many times will a filter be applied or a search be conducted
With these unknown variables in mind, even when optimizing your app workload in a very calculated manner, it would be extremely hard as a business to predict end-user behavior and produce a budget for these unknown variables.
It is extremely scary being charged on variables that you have no control over.
To charge workflow usage for development is extremely disheartening. I have an app where I literally built a side menu with 5 buttons (which is unfinished by the way) and that work alone has used 2,889 workload units.
I look forward to hearing more from Bubble and how they coach us to navigate this change. We have 18 months to figure it out or find alternative options.
9 Likes
We need to leave bubble en masse and turn to alternative solutions ! 
6 Likes
For me, a few things still worry me:
- We are now punished for testing too much. Not sure if you can do anything about that.
- We have no tools to put an end to a bad actor that could literally drain our bank accounts or halt our app for an entire month.
- API workflows are just way too expensive compared to the rest of the market.
- New Bubble users must pay for being new and getting things wrong. For example:
I have an app where 250,000 WU in two weeks came from a single dropdown that I created that returned all of the companies in our db. It wasn’t a big deal on the development database where there were 10 companies, but on live there were several thousand. I know I should have made this a search box, but it slipped my mind because I was trying to build things fast. On this new plan, I would have had no idea until my capacity was 75%, and if that happened at the beginning of the month, that is a huge problem. We need a tool to be notified on WU per day or WU per hour, and ways to stop the bleeding if need be.
24 Likes
Not necessarily. Because no one knows what they mean by optimizing an app. Maybe yours is already the most optimal way to do it.
It’s like launching a car and saying it could use less fuel.
Ok, less compared to what? A sedan? A sports car? An airplane? What makes your car more fuel efficient? The big or small wheels? The color?
It’s empty information, nobody says what they mean by optimize? How do you optimize for example the loading of a blank page? If just opening a blank page is 13WU?
Without taking into account that the “optimization” is tied to the possibilities of Bubble as it is the case of Bulk operations, where there is no optimization possible by the user, it is what it is and you will pay what Bubble wants you to pay.
If tomorrow they decide that a click on an empty element costs 100WU, you will pay it because you have no idea what the WU refers to, you don’t know if it is too much or too little, if it is efficient or not.
10 Likes
Why do we have to wait 2 weeks for the webinar ? You should have scheduled it right away. You will get tons of negative posts. You said the WU is more transparent than “capacity” : maybe in your head but not in your day to day user’s heads…
9 Likes
That little 8% there represents your most dedicated power users who are building actual businesses on Bubble. That is the most important segment of your user base that you’re so casually writing off as statistically insignificant.
41 Likes
We used 180 million WUs last month… don’t get me wrong, we need to optimize, but we put our full faith upon the presumption that we got to use our capacity, that we paid for, however inefficiently we liked. We paid for it, we got to use it how we wanted to. To totally switch to a new pricing model, which requires optimal efficiency from the start–for a user base that has not needed to be 100% mindful of optimization for over a decade–is an atrocity. Bubble should be ashamed. We’re fine with a 10%, or even a 20% price increase to existing plans, but this new model is absurd.
22 Likes
Is VP of marketing is a right position to explain how WU calculates and works? Is there maybe someone who is more related to how it was build to make such claims?
21 Likes
Making mistakes is natural for human beings, but insisting on the error and not being able to listen to customers, has another name!! unfortunately whoever came up with the brilliant idea for this new pricing model, insisting on not properly adjusting some points, will inevitably end up with the Bubble. Regrettably, I’ll wait a few more days, otherwise, bye Bubble.
8 Likes
Bubble used to be an amazing platform that enabled us to unlock new possibilities with no code and paved a way for technology to become more accessible and easier to use. As Bubble was growing, so did its prices, leaving the current users and partners feeling taken advantage of. We understand the importance to make sure Bubble can sustain itself and provide a smooth running experience for its users, but it seems like it’s coming at the expense of the developers and agencies that helped build Bubble. We hope Bubble will continue to listen and take into account feedback from its existing users and partners, especially when it comes to any changes to their pricing.
1 Like
big difference between my calculations (and other people’s calculations) and what @tatiana.a is saying…
She says that a action should be between 0.1 and 3 WU. Other are seeing 15 WU for just login or 13 for a create action with no fields, conditions or search…
Just here is one simple sample:
32 Likes
This is a heartbreaking news. Bubble has been a great part of my journey to build apps and thankfully supported me along the way. It’s sickening to see them take such drastic steps towards making the platform costlier for many. Bubble has always been about making app building easier for everyone, and these new changes seem to be contradicting that notion. It’s really sad to see Bubble taking a step in the opposite direction.
4 Likes
So to summarize, you are going to charge NOW for tooling and optimizations that should probably come in Q3… maybe.
This is all just more “we’ll make this better in the future, we promise. TRUST US”.
But the trust has simply not been earned.
Like, has anyone forgotten how many years the ‘responsive editor was coming’?
Also, SOC2 was like a Q3 thing last year, right?
This is not what we are seeing in real apps.
So let’s talk here. Bubble loads somewhere around 300 - 400 items in the network tab for a basic repeating group search. Including all the field values for every item.
What are we going to be charged for? The 400 items loaded into the network tab or the 20 items being shown in the repeating group?
Do we get charged for the weight of loading every field on a data type or is Bubble going to take it’s own medicine and optimize itself here as well?
You guys understand we know how cheap S3 storage is right? After paying exorbitant storage prices for years suddenly we should be grateful that the Bubble overlords have seen fit to grant us more storage?
This is so par for the course. I’ve been Bubbling for 7 years and have been a fanboy and evangelist for years. I’ve stuck up for Bubble through previous fiascos.
Unfortunately I think the fanboy just died.
59 Likes
Respectfully your “stats” seem like bullshit compared to the most basic testing the community has done. I have an app that is purely for plug-in demos with function of simply creating & changing a thing and am touching 50k U. Avg create a thing button click seems to be 6 WU.
This no longer feels like it’s about helping startups and creating the best no code tool rather squeezing every dollar you can.
I’ve been looking into alternatives and with these changes bubble isnt even an option anymore in the no code space anymore. For a fraction of the price on bubbles new plans you can have the ability to self host, access to source, and more native functionality, without worrying about being locked into a host who once again went out of their majority community best interests.
6 Likes
I guess the 8% are all on the forum right now haha…
Jokes aside, this average number may sound nice but the impact is disproportionate across plans.
Given the chance of running overages and being billed for them, this recommendation may not be the most convincing. Especially for free apps who have been shown by other users to easily bust their limit.
1 Like
I’m actually dumbfounded the pricing model was so bad that people actually considered their was a bug in the calculations and y’all are sticking with it 
20 Likes
@tatiana.a How should I advise businesses to project end-user behavior and how that translates to workload usage?
Ultimately, I am looking to provide them with some type of projection that says, you have an app that does “x” with “x” amount of daily users, “x” amount of workflows, etc… you should expect your workload usage to be “x” each month.
Any feedback would be greatly appreciated.
This.
6 Likes
The ‘Free’ plan for an app or even testing ground now essentially becomes disposable. With the limitation already of 200 DB entries and now 25k WU, that will burn through super quick by the sounds of things, probably within a day or two of testing or developing - especially any new comers that want to try and pick things up.
Just a random thought.
4 Likes