You Didn’t Build That App. You Just Picked the Wallpaper.

I remember the first time I built a torrent client. It was 2004, I was nineteen, and I felt like a god. I wrestled with libtorrent’s C++ bindings, debugged memory leaks at 3 AM, and finally, after weeks of sweat, I could download a Linux ISO. That feeling—the rush of creation—is what every developer chases.

Fast forward to today. A developer posts “Show HN: I built a torrent client for the Mac. It’s called Swarm.” The top comment? “Spoiler: it’s yet another wrapper for libtorrent.” Ouch. But here’s the thing: that commenter isn’t being mean. They’re being honest.

The brutal truth: building a torrent client in 2025 is no longer an engineering feat. It’s an interior design exercise.

Let me explain. The underlying technology—libtorrent, WebTorrent, BitTorrent protocol—is a solved problem. Open-source libraries have commoditized the entire stack. You can pull in a mature, battle-tested library in five minutes with a package manager. AI coding assistants like Copilot or Claude can write the boilerplate integration in seconds. The actual building—the novel logic, the hard algorithms—is gone. What’s left? The UI. The UX. The icon set. The onboarding flow. The color palette.

Think about it. The developer of Swarm spent most of their time deciding whether the download button should be blue or green, whether the progress bar should be rounded or flat. That’s not engineering. That’s decoration.

And the community smells it. They know that behind every shiny new Mac app is the same libtorrent backbone. They’ve seen it a hundred times. The novelty isn’t in the code—it’s in the curation. “The last competitive moat in software isn’t code. It’s curation.” Say that out loud. Let it sink in.

This isn’t a knock on Swarm’s creator. They did real work. But the nature of that work has shifted. The value proposition has moved from technical execution to UI/UX curation. In a world where AI and open-source can generate the functional backbone, the only thing left to differentiate is how you arrange the furniture.

And that’s terrifying for engineers. We built our identities on being the ones who built things. Now we’re being told that the building part is table stakes. The real value is in how you present it. “Building a torrent client in 2025 is like bragging you built a house because you chose the curtains.” That’s the twist: the act of creation has been replaced by an act of selection.

This isn’t unique to torrent clients. Every app that relies on a commoditized backend—chat apps, CRUD dashboards, media players, note-taking tools—is facing the same reckoning. The barrier to entry has dropped so low that the only defensible moat is distribution, brand, and design. The code is the least interesting part.

So what does this mean for you? If you’re a developer shipping a new app, ask yourself: Am I building something new, or am I curating something existing? If the answer is the latter, own it. Don’t pretend you’re reinventing the wheel. Admit that you’re choosing the rim color. Because the audience already knows. They see the libtorrent wrapper. They see the AI-generated boilerplate. They see the thin veneer.

And you know what? That’s okay. The world doesn’t need another innovative torrent engine. It needs a torrent client that doesn’t look like a 1990s Winamp skin. The curation is the product. The UI is the value. “Stop calling it a ‘built’ app. Start calling it a ‘curated’ experience. That’s the honest future of software.”

So next time you see a “Show HN” post, don’t reflexively applaud the engineering. Look at the screenshots. Look at the flow. That’s where the real work lives. And if you’re the one posting, remember: your pride in ‘building’ is valid, but the community’s cynicism is warranted. The tension between those two isn’t a bug—it’s the signal of a market maturing.

Embrace the decorator role. The engineers who thrive in the next decade won’t be the ones who write the most complex code. They’ll be the ones who pick the best wallpaper.