The idea of introducing number counts to monitor is stressful and not a user centric decision, If I change to an annual plan now will I be able to stay on the old plans for the rest of the year? This news is scary and bad.
Appreciate your time writing this down but not sure what to think of it.
I notice some sort of playground mentality in which we need to be aware of drastic changes now and then. This does not help to get trust from users and companies trying to make a living with Bubble.
Although Bubble delivers many good things, one major drawback is the lack of control and ownership of the code. No Bubble, no business. I think people will start thinking about this before starting with Bubble and posts and changes like this will not help. This is exactly what people and business are worrying about.
As for the arguments given, I bet when you take averages with maybe 80% of apps doing nothing you can hold on to a statement that it does not affect users. You and everyone else knows that doing any kind of meaningful project means thousands of records from the start. Multiplying easily with the number of users using it.
For me, just started paying this year to launch our MVP, it means serious considerations to move away from Bubble. For sure this move will be very very costly already in the beginning because of the database thing limits. But more so because you got me thinkingâŠwhat will Bubble change and do next year?
I built a loyalty Saas for small shops. Each time one of their clients checks-in or redeems a reward, I write a line. A shop has in average 50 of those transactions per day, 1,300 per month. I started little time ago and now I have just a few shops but 20 shops (i.e. my users) produce 26,000 Things per month. Each month. They cumulate with time and increase with the number of users.
The new pricing is simply not sustainable for me.
Can anybody direct me to a way of storing Bubbleâs data to an external DB?
I have told a 100 people about Bubble, it has truly been a fab experience building apps. However, with this change â Bubble doesnât make sense to our boutique travel company. We were here for the longer run, however, this looks like a dealbreaker in all aspects.
As your team correctly mentioned, all of us, paying users, weâve structured our databases to store lot more data than 25000 rows. How are we supposed to change our entire design? Uh! Please figure out a different way to charge us.
As an app owner very near to launch with a database with over a million âthingsâ, I quite simply have no way to know how this will affect me.
My original plan was to get ready to launch then upgrade to a more expensive production plan this summer, so I welcome the reduction of price in that, but now Iâm on the hook for who knows what.
Perhaps someone can provide some illustrations of how this is going to come in.
Thanks for the notice. Iâm really worried about the db limitations, my app uses very little capacity but has +10,000 things per user (very simple, plain text things), I would love to see the older pricing versions stick. If not, I believe that a lot of developers, including myselft, will need to find other platforms
Another question:
Are you going to give the Personal plans the ability to add additional storage now? 5000 records is significantly small to start out with, and making the almost $100 jump to the Professional plan purely for more rows (especially if website visitors number is very low) doesnât make sense.
I agree with what everyone has been saying above about the data limits. This is going to be detrimental to most apps that have been alive for a while because just overtime a lot of data is collected.
I had wished that based off the screenshot this was going to be a monthly limit on database limits, but based off what @grace.hong has stated, it doesnât sound like it.
This change will prevent a lot of scalability and for SaaS model businesses to offer their services for cheaper prices, or in my case running a nonprofit with higher operating costs when we are already on a tight budget.
I hope this decision is reconsidered or at least modified to something more reasonable.
We may just need to rely on external services and hope that external API calls wonât be limited in the future.
This will be an issue for me I am building a system for a taxi company to store all information and create a like HRM system and we would need to go for the full whack specs to run an internal system over 2 years it would work out cheaper to hire a full stack developer to create it
Exactly. And 200,000 rows is low for the production plan. Whatâs after that, dedicated?
Hmmm, I donât really believe in what I just read. Database limits ?!
Iâm currently finalizing a 6 months project to redesign my existing system with the new responsive engine and some optimisations (yes itâs a huge app). One of the additional, important element of this redesing was to speed up search via introduction of dedicated Tables of Things Search Indexes - so small, light THINGS that can be easily searched for - that means creating TWO Tables per each THING; one with the Data and one for Index (this model is based off on @petterâs book about bubble performance). So now I done it for nothing ? All the server APIs and All the DB changes I will have to revert back ???
Iâve been working on bubble for over 5 years now; there were good and bad times but itâs the first time I kinda feel unsure and cheated.
I donât need a hudge performance because my system is used by 50 people but the DATA is the main reason why people use it and why people want to digitalize more processes via bubble build system.
This update means I just wasted 5 years of my bubble learning ?
This update means I just unnecessary evangelized bubble among other people ?
That change is unacceptable - I donât want (and I will not) rebuild my system which I spent years of development on, just to move now to external database !!!
This means there is no point in further developing apps and this also mean for me that all processes that has been changed in my company will have to go back to paper !!!
Why ? Because now people can easily say that NO-CODE is a huge BS because NO-CODE owner dictates whatever they want w/o even carrying for their developer businesses and responsibility that is laying over the developer.
My honest applogies for such bad stuff out here in my post but itâs the first time Iâm really angry on whatâs going on here.
Sad to see that Bubble is measuring against competitors for their pricing here when they have been in my mind a leader in the no-code category and their product is much different/better than competitors.
Now they are coming in line with Webflowâs CMS pricing, which is a builder designed for completely different functionality and not near the data intensive features that Bubble offers, yet on a per Row price is now not that much different. Maybe they donât want to serve App Builers anymore and would rather get into more static sites and that is why they are making the change?
Bubble:
Webflow:
Seriously not cool!
It might have been better if you said you were using all the extra money youâll be charging us in overages to get actual support that actually responds to emails, or making it so we donât have to use BDK or other third party services to make mobile apps, or in any way making Bubble better.
However, based on this post it sounds like Bubble is simply giving us the screw job. Will be going elsewhere for my next app and will be looking into rebuilding my current ones elsewhere too.
Bad decision for users from developing countries. I have been a very loyal customer for 3 years but this will be unaffordable
Ante eras chĂ©vere BubbleâŠ
One of the biggest benefits of bubble was pricing based on cpu usage, not count of rows. My app has a lot of rows for history, but costs very little to host because we only have a few sporadic users. My costs are about to more than quadruple⊠The things limit is way too low.
When you ran DB averages⊠did you look at actual active bubble apps or did you also factor in all the dummy accounts with only 1 database thing? Hard to believe that was an actual average of the real Bubble Community⊠especially after seeing the overwhelming response in the forum.
Can someone better explain the pricing on overages when you invetibly go over your database records allotment? The picture above shows $20⊠is that just a general overage fee or per 1000 DB records orâŠ
*Side note: Who are the external DB pros? Would love to chat about optionsâŠ
**Suggestions for better pricing model: Keep it to traffic-based or user based. Iâm totally cool paying you more as I grow. But paying you more as my current user base just keeps doing the same things they always do like chatting back and forth or adding things to their task list⊠hard pill to swallow for sure.
Thanks for this breakdown @gf_wolfer!
I am extremely worried here. It will be cheaper to get an app developed using code in the long run. I now have to really reconsider what i do moving forward as half the features i may have to drop. I understand storage, but database records is something that is really going to hurt and can put a spanner in the works.
Given the fact that the initial post included a screenshot showing âMonthly database recordsâ (which now has changed to âTotal database recordsâ) I have hope they might change this based on user feedback.
This totally forces bad database design, not to mention we donât have a decent tool to delete a lot of rows in the database yet.
Man, I feel physically sick from this announcement. This just killed so many of my app plans.
what a terrible and unethical approach to price gouging. 4K and 25K of things is not a lot of things!
Bubble is meant to be an all in one platform providing an opportunity for non-coders to easily build apps, now that opportunity is certainly gone unless you want to build simple toy apps.