Is it possible to integrate Framer as the frontend while using Bubble.io for the backend and database? If so, what’s the best way to connect the two?
For the backend workflows and data base you can trigger and use them out side the Bubble app but not the client side workflows
Yeah, you just make API calls in Framer to backend API workflows in Bubble. But, if this is a new app, you might want to explore (being that you’re comfortable with exploring code) using Supabase and an AI tool like Claude Code or Codex to create your backend/db. It’ll be a lot cheaper than using Bubble only for db and backend.
Yeah, that makes sense. But then what would you say is the main advantage of learning/building with no-code in the first place if I’m still going to rely on something like Supabase + AI for the backend?
My main priority is actually having a really polished, premium UI with smooth scroll animations and interactions like you get with Framer. Do you have any suggestions of how i may achieve that in bubble for that?
The value of no-code isn’t necessarily “never touch code” It’s getting a lot of product infrastructure and iteration speed without having to build everything yourself. I mean, No-code saves you time by handling a lot of the foundation for you but you can still use code when you need to.
The advantage of Bubble for me isn’t that you never need code, it’s how quickly you can have the UI, database, auth, workflows and backend logic all working together without managing all of those separately. If the main priority is a really animation-heavy Framer style frontend though, Bubble can do a lot with custom CSS/JS and something like GSAP, but at some point you may end up fighting Bubble to get the exact interactions you want.
For a SaaS/app dashboard I’d probably still keep everything in Bubble if possible. For a very design heavy public frontend, Framer and a separate backend starts making more sense.
As @iamsaadalee mentioned, the advantage of no-code is to ship fast, have a central place where you can work on your front, backend, files, auth, everything and also own your code. Own as in, you know what you’re building. With vibe coding, you often don’t know what’s being added in or at least that’s the trend I see. But, with vibe coding you get benefits like that super premium polished UI with smooth animations and interactions, which you can get with Bubble to a degree but for much worse performance and cost because of the way Bubble’s infrastructure and runtime works. If you want Framer, use framer. Use Bubble for the rest of your app apart from the frontend. Check my posts, I showed how to use a single domain for multiple services. You can do something like myapp.com/ to Framer and then myapp.com/ app / * to Bubble.