How to use platforms like AWS API Gateway, Hookdeck and Tinybird to offload your app's most compute and data intensive operations and reduce your Bubble WU usage.
Folks go to bubble for a low code all in one tool to get something built and out to the market.
One price change and makers are adding multiple layers of complexity just to ‘get around’ it.
You now have to manage multiple layers of potential causes of an issues. You need expertise in each app to be sure you are getting the most out of their pricing plans and services..
If a price change causes this… I think you might be ready to hire developers and think long term about the app?
I had made all these changes before Bubble announced their pricing changes so they were not motivated by that. I don't think many tech products are made with a stack consisting of one core technology.
No you’re right they aren’t… but they can start off on one core tech.. that’s part of the promise of bubble and no/low code.
Your stack and approach changes as you grow.
I guess if these changes were already in place.. then they are not really part of adapting to the pricing change. It’s more like your app has seen growth that bubble alone can’t and shouldn’t be used to support.. which is still a good lesson for those thinking they will be on one platform from start to market fit. The fact it costs more on bubble now is an aside, that makes these changes even better.
Would love insight into when bubble and other no/low code builds realized it was time to bring in other services.
Folks go to bubble for a low code all in one tool to get something built and out to the market.
One price change and makers are adding multiple layers of complexity just to ‘get around’ it.
You now have to manage multiple layers of potential causes of an issues. You need expertise in each app to be sure you are getting the most out of their pricing plans and services..
If a price change causes this… I think you might be ready to hire developers and think long term about the app?
Great article James. Its great to understand how others are using bubble at scale
To be honest, this seems crazy.
Folks go to bubble for a low code all in one tool to get something built and out to the market.
One price change and makers are adding multiple layers of complexity just to ‘get around’ it.
You now have to manage multiple layers of potential causes of an issues. You need expertise in each app to be sure you are getting the most out of their pricing plans and services..
If a price change causes this… I think you might be ready to hire developers and think long term about the app?
I had made all these changes before Bubble announced their pricing changes so they were not motivated by that. I don't think many tech products are made with a stack consisting of one core technology.
No you’re right they aren’t… but they can start off on one core tech.. that’s part of the promise of bubble and no/low code.
Your stack and approach changes as you grow.
I guess if these changes were already in place.. then they are not really part of adapting to the pricing change. It’s more like your app has seen growth that bubble alone can’t and shouldn’t be used to support.. which is still a good lesson for those thinking they will be on one platform from start to market fit. The fact it costs more on bubble now is an aside, that makes these changes even better.
Would love insight into when bubble and other no/low code builds realized it was time to bring in other services.
Enjoyed this email/post
To be honest, this seems crazy.
Folks go to bubble for a low code all in one tool to get something built and out to the market.
One price change and makers are adding multiple layers of complexity just to ‘get around’ it.
You now have to manage multiple layers of potential causes of an issues. You need expertise in each app to be sure you are getting the most out of their pricing plans and services..
If a price change causes this… I think you might be ready to hire developers and think long term about the app?