Apps Built with Svelte

Svelte's central idea has an unusually direct benefit in these markets: it compiles components at build time rather than shipping a runtime, so the browser downloads and executes less code. On a mid-range Android phone over an unreliable connection, a smaller bundle is not a benchmark, it is whether the page becomes usable. The authoring experience is also notably lean: reactivity without hooks or boilerplate, and less code per feature, which suits solo builders and very small teams. The constraints are the usual ones for a newer framework: a smaller component ecosystem, so more building from scratch, and a much smaller local hiring pool. Teams that pick it are typically optimising for performance and their own velocity rather than for recruitment. Browse the products built with Svelte below and see how they weighed it.

Browse by tech stack

Frequently asked questions

Why does Svelte's compile step matter?
It ships no framework runtime, so bundles are smaller and less JavaScript executes on the device, directly relevant on low-end phones and slow networks.
What is the trade-off?
A smaller ecosystem and a much smaller local hiring pool than React or Vue, so more components get built in-house.