My suggestion: look at bubble in it’s current stage as a great prototyping tool and if you start receiving traction, build it with code right away
This has been my takeaway over the last 12 months of getting to learn bubble. And it’s not a knock on Bubble itself - providing a truly low-barrier-to-entry “codeless” app platform by default must come with some technical sacrifices. I compare it to a high-end custom Linux configuration vs Microsoft/Apple. The former will always be more efficient, but only the high end of powerusers will be able to make use of those efficiency gains. Most people just need something to help them handle the basic CRUD activities that make up 95% of their usage habits. Microsoft (and then Apple) provided that monolithic but stable user experience that was easy even for a rank beginner to do complex things. There is a reason why Microsoft and Apple completely own the PC space while Linux has only a niche user base. And yes, I do see Bubble as a potential Microsoft/Apple of the codeless development platform space
If you get to the point where you need to control server architecture for edge performance gains, you’ve outgrown what Bubble is good at providing for you. But that’s a good thing, because it means you’ve created something awesome that tons of people need to use every day!
I do believe - just from what I’ve seen in terms of responsiveness of @emmanuel and @josh - that once Bubble cracks the monetization nut, they will be able to focus on providing great support for powerusers.