I’m just happy because I’ll finally understand the WUs better now that @MattN is going to teach them 
1 Like
@josh respectfully, how is it so hard for bubble to see this issue with pricing, you managed to drop a plethora of new information about pricing on us 2+ years after it came out on a model that even hardcore long term users of the platform can’t understand.
Documentation says WU is made up of base costs for a total of specifically 12 actions, all based on YOUR app, now you’re saying it’s more based on the total server (all apps) and actions not listed🤔
You say you don’t see it as a bug but a single create an item action can go from a couple WU to 10+ for seemingly no reason under all the same conditions yet documentation portrays it another way.
At this point it feels as if you guys have absolutely no idea what you’re doing with WU and are just spewing answers to prolonge/appease. Your words aren’t matching documentation on an over 2yr old pricing model, bugs are still being found, we aren’t talking about a couple users effected a few WU we are talking the full non dedicated user base…your answer was in essence “we know we set pricing in documentation for you but hey that’s actually just averages, if you have an action spike a few hundred % in price it’s fine and expected” yet that’s not documented anywhere…
Do you not see the the awful customer service and quite frankly massive liability bubble is putting themselves in…
5 Likes
To be fair, most everyone was complaining back when we had a “capacity” based model since defining 1 unit of capacity was impossible.
Really, Bubble is in a catch 22 here.
Going back to the days of old where people were desperately trying to figure out how much capacity they needed… vs. today where people are desperately trying to figure out what makes up a WU/how much WU’s are needed.
3 Likes
As long as the averages are consistent enough to be predictable that should be ok. I am rather WU conscious but happy to accept there’s a bit of wiggle room.
Would be a bit like filling a car up with fuel and knowing that X amount of fuel would get you Y miles distance - but sometimes a little less, sometimes a bit more, depending on external factors.
Obviously if it fluctuated wildly it would be a matter of concern.
its really simple, i do this with all my clients, as soon as they get big i move the entire backend to Xano.
Bubble loses its margins, deservedly so because customer service for backend bugs is poor and this pricing model is poor. still no european servers for 500 a month, still no cronjobs on 10,000 database things per night for under 500 a month, meanwhile all for 80 a month on xano or under 40 on cloudflare.
4 Likes
And free on Supabase 
. Why have you chosen for Xano? We had to make a decision as well but went for Supabase because of the price point and open source. Xano is closed I believe? And not free so what features made you select Xano?
i met the management team and believe in them.
check their twitter on how many new features they ship every month based on actual user painpoints
That’s a sound reason!
I competely agree that this change is needed, but I have found that using “Arbitrary Text is ____” can be a decent workaround here.
If you’re handling boolean logic, just build the logic inside the Arbitrary text to return a yes or no – I also sometimes will substitute the “yes” output for a description of the logical step being handled to make the final composed expression a little more readable
if you’re handling multi-step math, you can have the final result “converted to number”
In general, this makes it possible to more easily encapsulate logic and copy-paste pieces as needed. And then if you need to remove a condition in the middle, you can just make it a redundant Arbitrary Text is yes (where the arbitrary text is just “yes”)
1 Like
Yeah but this gets really annoying when you have multiple conditions and they all have to be nested inside multiple arbitrary texts.
Still nothing on this piece?
It seems all attention is going into the AI feature! Which is fine, but at what expense.
At the end of the day we are still working in the editor.
Forced parenthesis in expressions.
Finalizing the Tables (BETA) element.
Things like this have just been abandoned.
Just curious why?