3 ms·
Based off the demos, it seems like you can integrate HTML directly, so it might be possible to move from Bubble to "external API + Bubble frontend" in a straigh
by rtpg 9y ago
Based off the demos, it seems like you can integrate HTML directly, so it might be possible to move from Bubble to "external API + Bubble frontend" in a straightforward fashion.
You could also likely put a layer in front of Bubble to only serve some pages with Bubble, other with your replacement.
Also from the FAQ:
> The good news is that Bubble is fully extensible via Javascript plugins. The Bubble model is to write the core website functionality using our super-simple language, and plug in Javascript to handle algorithms that are hard to build in Bubble.
So you could probably add shims and move around.
I think the most interesting way of doing this would be something like embracing Bubble for a lot of work and having the "serious" code relegated to places that are easier to manage, like complex API or some custom widgets
- bluedino 9y ago>> The Bubble model is to write the core website functionality using our super-simple language, and plug in Javascript to handle algorithms that are hard to build in Bubble Programming without code...until you need to actually do something
- aeorgnoieang 9y ago> I think the most interesting way of doing this would be something like embracing Bubble for a lot of work and having the "serious" code relegated to places that are easier to manage, like complex API or some custom widgets This is basically what I do now at work. I was hired to, in part, work with several RAD-tool projects. I pretty quickly ended-up tho working on mostly backend code that the RAD tool projects interact with via, e.g. web requests. That's been a pretty good division of labor given that most of the RAD tool project's features are fairly simply in terms of UX. They're definitely not good enough to be widely used by lots of users tho, e.g. there's no real error handling.