After working with both, here’s a simple breakdown:
Bubble Backend:
Integrated with the Frontend
Great for rapid prototyping.
Limited in scalability and complex data handling.
Xano Backend:
More powerful and scalable.
Offers advanced filtering, background tasks and custom functions.
Better suited for backend heavy apps.
Steeper learning curve but great for long term growth.
My approach: I use Bubble for frontend and Xano for backend. It is a perfect combo for flexibility and performance.
I’m curious to know that how do you structure your no-code stack?
2 Likes
I’ve just started using FlutterFlow + Xano for a client’s project and have fell in love with Xano (not FlutterFlow though).
I haven’t used Bubble + Xano yet, but I feel that if you lose the seamless integration of Bubble backend it might not make sense to use Bubble anymore.
In such a case I’d definitely explore WeWeb + Xano or FlutterFlow + Xano.
1 Like
Great insights @ademiguel why did not use Supabase with Flutterflow as it is integrated natively ?
1 Like
Indeed it seems like a more logical decision to use Firebase (not Supabase) with FlutterFlow sice it is integrated natively.
I’m currently using Xano with FF just because my client had this setup from the beginning. Otherwise I’d probably had gone with Firebase.
Supabase would be a interesting option since it’s open source and reduces vendor lock-in. It will probably require the same amount of work than integrating with Xano, but probably more work to integrate than Firebase.
1 Like
