Why we build with Svelte and not React
We tested React, Vue, Solid and Svelte on real projects. Svelte won for reasons less about the framework and more about how we work.
We’ve spent five years building websites for clients in Medellín and across LATAM. Along the way we tested React (Next.js), Vue (Nuxt), Solid (SolidStart) and Svelte (SvelteKit). Today every new project starts in SvelteKit except for edge cases. Not because it’s "better" — because it fits how we work.
The benchmark isn’t the criterion
Almost every modern framework produces fast builds. The real difference is how long it takes a new dev on the team to understand a complex component.
With Svelte 5 + runes, a stateful component reads like JavaScript that updates the DOM. No hooks, no circular dependencies, no defensive useMemo.
Three things that tipped the decision
- Less code per feature. A checkout form in SvelteKit takes half the lines of its Next + React Hook Form + Zustand version.
- Smaller bundles by default. For clients in Colombia, where 4G isn’t always reliable, this translates into better conversion.
- SSR + islands + adapter-node. We can do everything: pure static, server-rendered, edge, or own server. Without rewriting.
When do we NOT use Svelte?
When the client already has a large React team that will maintain the code afterward. Consistency with their stack beats our preference.
The best technology is the one the team that inherits your code can maintain without you.
Conclusion
Svelte isn’t a silver bullet. But for a small studio delivering turnkey projects, it reduces friction where it hurts most: maintenance cost.
If you’re evaluating a stack for your next project, write us — we’ll honestly tell you which fits your case, even if it means we don’t end up working together.