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