Totally understandable.
However, what is the impact for Bubble.io plugin developers, heavy contributors to the platform, who are required - unless I am mistaken - to provide and maintain a live-mode app to demo their plugin, for approval on the Marketplace but also to demo to end-users ?
Templates have a different license, for plugins we’ll need to improvise.
More than pushing users away, what this change does is erode the trust the Bubble won’t pull something like this again. I’m scared that I’ll build something, and Bubble will make changes yet again. You have these Bubble fan boys in this thread lauding this change, but quite frankly, this nullifies the key value prop of Bubble
how to position Bubble?
The problem starts when they want to be both. It is definitely possible to be both but MRR cannot be the sole principle then.
As seen here, many in the US may not understand the complexities of USD to local currency exchange and hence will be seen passing comments like “oh. It’s not a charity. It’s a business”.
The best way forward for @josh @emmanuel to balance this out is to come up with a Pay per use model based on the data not on feature restrictions. (existing addon features restrictions like Custom domain etc can reman)
This way all of us, regardless of our demographics gets to learn, build, test, ship and as it gets bigger we pay more.
Please consider this.
Honestly, I understand this choice and for me, it’s fair. Imagine you launch a business based on a code or No-code solution, do you expect 80% of your users subscribe to a free plan ? No, you probably don’t. The new free plan comes with the most part of the Hobby plan, excepted for the Data API. Well, we’ ré free to still use airtable or even Google sheet to host some data needing backend workflow (airtable and Google sheets are also good candidate for backend workflows!).
Months ago, I built apps with Glide, and they also change their mind and prices. Now with Glide, you pay per users, prices are much more expensive than the Bubble’s personal plan offering much more than the full Glide package.
It’s a change, but a change that will perhaps bring more performances for paying users, not so bad.
On this forum I guess we all have at least one app attached to the old hobby plan, as these apps are grandfathered, we will still continue to take beenfits from the Hobby plan, so no change, and no danger for your app in progress.
That’s my humble opinion. I do expect Bubble be still there in several years, so I do expect Bubble guys take the good decision for Bubble and its roadmap. And if one of these decisions is to preserve performances for paying users, I would say it’s understandable, to not say “normal”…
When these type of things happen you understand one thing and just one thing.
You have no control of your current and future business. Your IP is not your IP.
You own shit. If your business relies on any no-code product that doesn’t allow you to export the source code or self-host you are doing it all wrong.
No-code and low-code are great tools to bring your idea to life. They break important barriers, but not every solution out there has done it right.
In this intangible economy you need to protect your data and your IP. Bubble does it. Why don’t you?
Look for no-code and low-code tools that let you export code or self-host and if possible Open Source. Don’t vendor lock yourself. Don’t be that guy.
There are two types of bubblers: those that have already realised this and those that haven’t…yet.
I fear you have a very good point. Starting out involves a period of testing and implementing the ideas that Beta users may find to be a necessity rather than a feature you thought you could start up without. It takes time to get this feed back and paying to get it is just a burden I may not be able to afford with out help from somewhere. I would certainly be happy to see a plan that takes this phase into consideration.
Essa é a uma otima dica para o @emmanuel analisar.
Coming back to this. While developing a plugin, I realise now that the log section from a test app is available only with a paid plan.
As I mentioned before, I totally understand your position, however, I would like to understand what is the solution for developers that are required to:
Many thanks.
I’m not a fan but I’ll make do
Sounds like a good idea
Agree with Vianney (@redvivi ) here, it’d be great if Bubble could come up with a special plan for this or adjust existing plans to make this possible to manage.
Levon Terteryan
Founder @ Zeroqode
#1 Bubble Publisher and Developer
100+ Bubble Templates
25+ Bubble Courses
250+ Bubble Plugins
20+ Bubble Building Blocks
@emmanuel I can’t access the logs on a template that I’m developing which holds me back from finding the issue.
Bubble broke innovation…
i don’t really think that this is a good change but ok
unpopular opinion, but something that came to mind re: issues with creating templates on a free plan.
Wouldn’t it make sense that template makers selling templates should be paying? If I’m making an SaaS app or selling a template, what’s the difference?
I’m probably missing a million nuances and valid points here. But figured I’d ask.
If Bubble wants to make more short term profit then it is the right decision.
If Bubble wants to become mainstream like Github (free plan even with private repository) then it is not.
When pricing is not aligned with the company’s mission/ values then users will just leave when another better/cheaper product shows up 
(web flow?)
hello did you get an answer to that?
U see, people who already know the power of bubble or used it before and are now dependent on it will not turn around for an alternative BUT newcomers will/may bounce !
