Changes to how we charge for applications going forward

But has no sense at all…

If you consider 2 years rolling, that’s 0,01 Things per Unique visitor…

No Sense to dimension an app to such amout of visitors with such small DB…
They must be kidding…

I’ve already done my complaint by email…

1 Like

This feels like a bit of a cash grab. From a DB perspective, storage per thing is way overpriced. We shouldn’t be thinking the limits are low, we should be thinking the cost per thing is high.

Can we at least export the code then? Because this is literally an increase in price and no one who actually uses bubble will benefit from this.

2 Likes

I use Bubble as my front end!

For videos, Mux is my go-to, but Cloudinary is also really good!

2 Likes

Lol, good one :rofl:

1 Like

Hey everyone,

We’ve been watching the thread, and appreciate the feedback re DB things.

I know that for applications that have been running on Bubble for a long time, and built their apps without thinking about the number of database things, this leads to extreme situations, which makes these limits feel low. That’s why we’re not applying any of these changes to existing applications till 2023 at the earliest, to give us plenty of time to figure out how to make it work for you. The kinds of things we have in mind to help users who would have a very hard time adapting to this, which we would apply on a case-by-case basis:

  • Giving special discounts
  • Extending the time period on the old pricing
  • Coaching to redesign the application
  • …etc

The last thing we want to do is to make Bubble unaffordable for people who’ve trusted us as their platform.

We are aware our tooling to clean up DB things currently isn’t great, and we are working on improving it: we plan to make sure it’s good enough to efficiently clean up massive databases well in advance of the new pricing coming online for existing apps.

For new apps, it’s difficult to predict in advance what the right limits are, because all of our current apps were designed with the assumption that database things are basically free. We don’t want to discourage or disincentive people using the database, but we also feel like it’s the fairest way to charge for applications that aren’t directly exposed to external visitors. We plan to take the community feedback into account, watch how new users interact with Bubble, and make adjustments if we feel like the numbers aren’t working out.

We’re a community-driven company, which is why we discuss these things openly on the forum. We very much appreciate the feedback, and we’re committed to landing in a place that drives long-term sustainable growth for Bubble and long-term sustainable success for all of our users.

Emmanuel

2 Likes

This is extortion, I’m going to get a new tool.

5 Likes

I think trust is already gone. Doing this means they either do not understand their users, simply do not care or both.

If they pull the plug on this idea, if, every user will think…what’s next?

Not a solid way to start a business

6 Likes

I also want to add a short critique on the monthly users count.

This counts daily active users and sums these up for every month.
So actually if you have 1000 DAUs you get 30k MAUs according to Bubbles calculation.

This is a very questionable way of counting and also does not consider the seasonality involved in many web businesses (eg summer travel).

1 Like

Dear Emannuel

I love your product and wish it all the success.

Please do not only appreciate the feedback but consider it too.

8 Likes

How to kill your power users and community in one blog post. Bubble is officially unscalable for the majority of applications.

3 Likes

I would say that it’s not enough that “the majority of users would stay within their existing plan”: I guess most apps are rather confidential in terms of audience, so maybe you’re just taking into account the majority that doesn’t really use Bubble, and forgetting real working apps along the way.
As everybody said, the records limits are ridiculously low, and almost any developer would agree. Even without any user, it will soon become impossible to maintain a price history for an ecommerce app because it would inevitably lead to a crazy price.

5 Likes

So basically… “we hear you but we’re not listening”

9 Likes

Wow. Goodbye! :wave:t3:

3 Likes

This is infuriating and disappointing.

And, this is likely good bye to Bubble for me. I’ve spent four years working on my app, improving it over time and I’ve just now gotten to the point where I’m excited about where in it’s at and users like it and use it.It’s a side hustle for me, so it’s not a big money maker at this point. But I’ve been hoping to grow to something bigger. I’ve been perfectly fine with the personal plan up to this point, be these changes would force me into the $320/month plan. That’s not doable at all. Way to pull the rug out from under all that work, Bubble!

I may explore the external DB avenue but as many have said, what’s going to stop Bubble from doing the same to API calls. Why would I out all that work on into doing that? Plus, i really don’t want to spend time on that when I could be developing the app.

2 Likes

Well it’s not that it makes sense for me either. But we don’t need more guesswork - we need a huge explanation from our bubble-tech owners.

If you think about it, is a visual editor that allows you to connect your frontend to your database through API calls. The difference is that by using commonly known frameworks you can use already developed out of the box components, while with wappler you are constrained by your knowledge of code. Draftbit for isntance is a mobile app builder that uses react-native for the frontend, hence you can use React-native components created by others and plug them in your app very easily.

I’m not saying that wappler is not a good alternative, but due that a lot of people here is concerned about “the limitations” of these tools, is good to take an informed decision. I personally wouldn’t use Wappler, but there are some low-coders that would do magic with it and its low cost.

That being said, there are lot of alternatives in the market. Some are more secure and perform better than what I would be able to code myself in several years, I prefer to spend a few extra bucks to take advantage of the systems that other created and that are easier/faster to learn and use.

1 Like

This is exactly what you’ve done.

How do you come up with 10,000 visitors but 5000 rows? With this math only half of the users could even register for your site let alone use any functionality.

10 Likes

I’ve been using Wappler since 6 months. I can literally build anything with it now. Bubble can’t be compared even.

It seems more difficult in the beginning switching from Bubble because Bubble teaches very bad development practices. Once you work on a new project in Wappler, and you understand the basics, a new world opens up.

I STRONGLY recommend Wappler

2 Likes

Yes, that’s for sure and to tell the truth, what bothers me the most is that the advantage of nocode is to allow everyone to make their own app. And to set up solutions with Bubble and an external database, we are on solutions more complex to set up and more difficult to maintain. Whereas choosing Bubble is precisely to have a “simple” solution to make your app.