← All posts

The Slow Death of Desktop Apps (and Why I Picked Svelte)

Think about the last time you actually installed a piece of software. Not an app store download on your phone, but a real installer you ran on your computer. For a lot of people, it's been a while. Email, documents, spreadsheets, design tools, accounting, project management, even photo editing: it all lives in a browser tab now, and you pay for it monthly.

Desktop apps aren't dying overnight. But they're dying slowly, and I've had a front-row seat.

Where I Started

I started my career almost exclusively building desktop applications. Installers, local databases, forms with a hundred controls on them, the whole deal. You shipped a version, people installed it, and if there was a bug, well, they lived with it until the next release went out.

There was something nice about that world. The app ran on the user's machine, it was fast, it worked offline, and you had full control over the environment. No browser quirks, no worrying about whether someone's on Chrome or Safari.

But the downsides were real too. Every update meant getting people to actually install it. Supporting different OS versions was a headache. And if a customer wanted to use the software on a second computer? That was a whole conversation about licenses.

Why Everything Went to the Web

Once you look at it from a business point of view, the shift makes total sense. With a web app:

  • Updates are instant. You deploy, and everyone's on the new version the next time they refresh.
  • There's nothing to install. A link is all anyone needs, on any device.
  • The money is predictable. Subscriptions beat one-time license sales for pretty much every company that's tried them.
  • Collaboration comes free. When the data lives on a server, sharing and real-time editing are just features, not massive projects.

Even a lot of the "desktop apps" you still use are secretly web apps. Plenty of the popular chat, music and code editor apps are basically a browser wrapped in a window. Tools like Electron and Tauri exist precisely so web developers can ship something that looks like a desktop app without writing one.

Desktop still wins in a few places: heavy video and 3D work, games, anything that needs deep hardware access, and environments that have to run fully offline or locked down. But that list keeps getting shorter. My honest opinion? Outside of those niches, traditional desktop apps are going to be close to extinct in a few years. New projects just don't start there anymore.

Learning Web Development the Hard Way

So I had to adapt. And I'll be honest, it's been a tough adjustment.

Web development is a different mindset. On the desktop, you have one process and one state, and everything is right there. On the web, you suddenly have a client and a server, HTTP requests, caching, CSS that does something different in every browser, build tools, bundlers, and a new JavaScript framework every week. Things I never had to think about, like SEO, page load times, and what happens when the network drops halfway through a request, became daily concerns.

The good news is that I'm getting better at it every day. And a big reason the learning curve has felt less steep is AI. Being able to ask "why is this component re-rendering?" or "what's the idiomatic way to do this in SvelteKit?" and get a clear answer right away has been huge. It's like having a patient senior dev sitting next to you who never gets tired of your questions. I still have to understand what I'm shipping, but I get unstuck way faster than I would've just digging through docs and forum threads.

So Many Frameworks

If you're coming to the web from the desktop, the sheer number of options is overwhelming. React, Next.js, Vue, Nuxt, Angular, Svelte, Solid, Astro... and that's just the popular ones.

React is the giant. It's what most job listings ask for, it has the biggest ecosystem, and if you hit a problem, a thousand people have hit it before you. Next.js builds on React and adds routing, server rendering, and a lot of opinions. Vue is friendly and approachable, with a really loyal community. Angular is the big, structured, batteries-included option that enterprises love.

They're all perfectly good choices. People build great things with every one of them.

Why I Keep Coming Back to Svelte

Personally, I really like Svelte. It's the framework I keep pivoting back to, and this very site is built with SvelteKit.

A few things won me over:

  • It's simple. A Svelte component is mostly just HTML, CSS and a bit of JavaScript. Coming from desktop development, that felt way more natural than wrapping my head around hooks and render cycles.
  • It's fast. Svelte is a compiler, so it does most of its work at build time and ships very little runtime code to the browser. Pages load quickly without me having to fight for it.
  • It's flexible. SvelteKit handles server rendering, static pages, API routes and forms, so I can build a whole app with one tool instead of stitching five together.

With Svelte 5, reactivity got more explicit with runes. You write $state for values that change and $derived for values computed from them:

<script lang="ts">
	let count = $state(0);
	let doubled = $derived(count * 2);
</script>

<button onclick={() => count++}>
	Clicked {count} times (doubled: {doubled})
</button>

That's the whole component. No boilerplate, no imports, and it does exactly what it looks like it does.

The trade-off is that Svelte's user base is a lot smaller. In developer surveys, only a small slice of people use it compared to React, even though it consistently lands at or near the top of the "most admired" lists. That means fewer job postings, fewer third-party component libraries, and sometimes fewer answers when you search for an obscure problem. For my own projects, that's a trade I'm happy to make. Honestly, AI has softened that gap a lot too, since I don't need a Stack Overflow thread for every question anymore.

Pick What Works for You

Here's the thing though: I don't think you should pick Svelte just because I like it. The best framework is the one you and your team actually enjoy working with and can maintain. If your whole team knows React inside out, switching to Svelte for a few kilobytes of bundle size probably isn't worth the disruption. If you're hiring, the bigger ecosystem might matter more than developer happiness. And if you're solo and just want to have fun building something, try a few and see what clicks.

As for desktop apps, I'll always have a soft spot for them. They're where I learned to build software. But the world has moved to the browser, and rather than fight it, I'm enjoying the ride. If you're a desktop developer feeling a bit left behind, my advice is to just start. Build something small for the web, lean on AI when you get stuck, and pick a framework that makes you want to keep going. It gets easier every day.