My app is still not viable even with current pricing.
I’m sceptical , how did investors agreed to 90% revenue reduction. So operating cost is few fractions ?
What kind of business model bubble adapted.
When this chaos is gonna repeat again?
My app is still not viable even with current pricing.
I’m sceptical , how did investors agreed to 90% revenue reduction. So operating cost is few fractions ?
What kind of business model bubble adapted.
When this chaos is gonna repeat again?
Finally, a decent reply by @josh. Nevertheless, still major question marks remain:
What do you mean with “I am not sure” @josh? Actually, if you are not sure that a certain change will result in an improvement, you should go and check that asap. Please, read @aaronsheldon reply to this comment since it really deserves clarification from you.
Even according to my calculations a B2C now becomes unfeasible. I personally have a web3 app (on which I have been working on for 6 months) that was going to be released soon, but with the new pricing, I don’t see it happening anymore. An average of 20 WUs (per my calculation) in a SPA is hardly something that can work in a B2C since only a small part of visits translate into money. What is your take on that? @josh @emmanuel
Thanks
For your third question, would it help to work with states, since that won’t consume any WU’s?
Tbh while relieved with the new revision, I’m still somewhat concerned about new method, simply because it doesn’t suit non profit websites or marketplaces where income is not guaranteed yet visitors (aka WU usage) may be high.
The only metric on my mind right now is “visitors per sale” or in other words “WU PER SALE” (WUPS) and this now trumps everything else.
And until I launch properly it’s litterally impossible to build the dataset required to make WUPS predictions.
A strange situation for sure, but at least the new changes have made it feel “less” scary taking that plundge into the big bad world, and ultimately, I guess this is the same for any marketplace type business, regardless of which platform it has been made on…
Best
@josh Thanks for the extra detail.
One detail I can’t find anywhere, for the Workload Tiers do unused WUs get rolled over to next month’s allowance? I’m sure they do as overages are charged at a very similar rate but couldn’t find confirmation anywhere.
You can add a custom field to an element on the page and store the cart client side. However, it is obviously lost when clearing browser data, switching browser, etc.
I need the carts to be saved even when the user logs out and logs in after a while (common UX I think). So, states would not work here.
after thinking a bit more.
the concrete measure i ask for is:
giving more WUs to the first 2 basic tiers of paid plans. especially dev version.
increasing the monthly cost of the highest paid plans.
[ideally based on power laws]
you will make most money in 5 years from the 100 large companies you produce and stay with you.
less stress for small users, more unicorns as more tinkerers who dont have to think about using WUs the whole time.
a problem with the large players is that as soon as your server costs are too high (still the case currently) they emigrate to external databases. I mean even I, as a small player, am considering it. [and am in the minority of people who know how to do this].
as soon as they emigrate you make less from them. you dont want that. thats also why AWS is constantly working on making things cheaper, even forced to work on own chips or why Cloudflare R2 is big. (and why above i recommended you work on lowering WU costs every quarter to outcompete other nocode platforms with your scale advantage)
yes very good point, like mobile phone contracts or Splice credits - if you do not use them, they roll onto next month. That would certainly be a very fair and friendly way to do it.
If overages cost money, then underages (that sounds wrong) should be credited?
Maybe it is. Would love clarification.
Excellent questions.
These might help us a lot building optimized apps!!
Looking forward to hear you about that @josh @emmanuel
Thanks
New WU test! I will compared with a version that I have done begin of the week.
Click and help.
This is something I’m specifically afraid of. Could you just charge your competitors thousands of dollars per month with a simple script?
Here we’re using Xano to generate page fetch and Puppeteer to click on random elements and trigger workflows on a demo app.
@vnihoul77 This will be everyday life in “new” bubble.io!
Here is the WU for my non-profit, hobby marketplace app. I pay the Personal level for this now.
Am I screwed? I have not been following the pricing discussion very much btw other than the general panic on Twitter.
Nice reduction. I can definitely work with this:
Going down from around 7.5 Mil WU to around 870K. Bill still going up, but at a rate I feel is fair and that is before any optimizations. I am sure I can probably reduce it by another 30-50% with some work.
hi major, hope you are well, youd still pay 29
and the last bar counts as before the last bar on your bar chart they still were 10x more expensive.
so monthly just 500x 30 ie 15k
your app is luckily simple as no major backend workflow stuff tho
I’d say nope! They adjusted the calculation for WUs, which was released yesterday at 9 AM ET. So that last bar, which looks to be roughly 500 WUs x 30 days, is your projected monthly cost.
It’s probably time to add new features, in fact
#mypieisdry
Everyone should be concerned about this and it does require a proper answer from @josh @emmanuel I believe.
A competitor to bubble itself even, could crawl for bubble made sites & target them, all automated.
Being able to set per user WU caps and know per user WU that we can use (within the editor) to throttle or charge additional usage is an excellent and much needed feature request given the new pricing model
There is one thing that is still bothering me. What would this “Others” be on the graph, where I click and it doesn’t go anywhere. It’s consuming and I can’t identify what it would be.
@josh
Indeed my application had a very significant reduction in WU, thanks for that.