Note: This is a comparison between Bubble vs Weweb AND Xano, not Weweb as a standalone stack
From all the comparison threads I’ve seen, it seems like opinions are mainly from devs/users that are novice to low-code/no-code OR is only primarily experienced in a single stack.
I’ve been working with Bubble for 3+ years with over 10k client hours billed spread between ~20 projects. I’d say there are very few limitations to Bubble if your clients are individuals or SMEs, and that the platform can easily cover most of their use cases (albiet with external API services but this is the same with every LCNC stack).
I do notice clients nowadays asking more about WeWeb+ Xano, hence my curiousity on this stack & eventually shift to be able to provide services for both platforms (Bubble & Xano and WeWeb)
Is anyone here experienced in both, and can advise me as to why they prefer one stack over the other?
Thanks!
You can look around in the forum, it’s been told so many times that at this point, I can just summarize it into, no work units, no trash DX and high extensibility is what WeWeb dominates in over bubble.
Most of bubble devs are just too confortable with bubble and switching to something else requires effort, especially if you are locked in mentally in bubbles shitty patterns that don’t even closely resem the web stadnards. So they just dont switch.
2 Likes
Thanks for the answer - most seem to be from people starting to learn LCNC, I was wondering if there’s someone deeply experienced in both, and how they would advise their clients to choose either platform.
It seems for most clients, the primary difference is building on Bubble is much faster, hence cutting dev time by a good chunk. Whilst weweb + xano has much more potential to scale & less vendor lock-in issues with exportability. Another route could also be expanding from standalone Bubble to Bubble + Xano once the app scales tremendously and app performance is affected using Bubble’s DB alone
From my own experience, if you build Bubble apps optimized from the ground up, workflow units won’t really be an issue for most applications. And even if it is an issue once you scale, I’d recommend to switch to Bubble+ Xano.
Having said that, I do love WeWeb’s ability for custom code, much better DX and no vendor lock-in issues. Platforms really are better if they focus on one thing rather than everything at once as with the case of Bubble.
I’m starting to learn WeWeb + Xano & hopefully be proficient enough in the near future to be able to offer my clients both types of stack. I’d say it’s much easier to get started compared to Bubble, although Bubble learning materials from 3+ years ago was pretty poor. I’ll let you guys know how it goes
1 Like
I can’t immagine bubble being faster than WeWeb, also with WeWeb you worry less about optimizing.
to me the real difference between bubble and any other nocode tool is that bubble has the backend integrated with the platform, that can be good or bad depending on the situations and is for sure limited to what bubble’s backend can do. you get automatically securely proxied api requests, realtime database, a basic type checking (it use to be a bit better but it’s still there and yes it can kill the editor performance but it is useful to spot a lot of errors).
weweb, is just exponentially better at everything else, so you get better default components, the ability to add all the styles you want without external plugins, create complex nocode components (think about reusable elements on steroid), easily switch from nocode to js any time you need something extra, great set of native integrations, real control flow in workflows, global workflows and variables, sane and modern development for custom code components, a great active team that delivers improvements and that you can speak with.
4 Likes
Love the answer @dorilama, definitely a lot of benefits beyond Bubble’s capabilities. Really interested in this point “create complex nocode components (think about reusable elements on steroid)”. I’ve been researching for a while and it seems WeWeb doesn’t support reusable components yet (which I use extensively in Bubble) - could you please elaborate on this? Would love to learn how I can do that in WeWeb 
yes you can have reusable elements, they are called components