An IP lawyer built a Sonos iOS app in a weekend with Claude — and the indie-software economy quietly cracked open

On r/ClaudeAI this month, an intellectual property attorney described building both an iOS and a Mac replacement for the Sonos apps after Sonos quit supporting them. His framing was unusual: I am not selling anything. I’m not distributing this. In fact, I’m not in software at all and work full time as an intellectual property attorney. I work with tech companies but maintaining software like this for years isn’t really feasible for me beyond my personal use.

The iOS app took one weekend. The post got 213 upvotes and 43 comments, mostly variations on wholesome, this is what AI tools should be for.

What this story actually is (vs. what it isn’t)

It is not AI replaces developers. The lawyer explicitly notes he can’t maintain this software for years, which is the actual job of a software engineer. It is also not anyone can ship a SaaS now. He’s not shipping a SaaS; he’s solving a personal annoyance with code that meets a personal threshold for working.

What it is, structurally: the cost of writing software whose user base is exactly one person just dropped to a weekend. That cost used to be the reason that software didn’t exist. Sonos’s Mac app being abandoned was a normal commercial decision — there weren’t enough Mac users on Sonos to justify ongoing development. Pre-AI, that decision was final. Post-AI, the affected users can route around it.

The supply curve of personal software

For most of software history, the supply curve has been: a problem gets solved when enough people share it AND a team is willing to commercialize that overlap. Both conditions had to hold. AI tools knock out the enough people share it condition for a specific class of problem — small, well-bounded annoyances where the affected person has enough domain knowledge to specify the problem clearly.

The lawyer in this story didn’t have to convince anyone to fund a Sonos-replacement app. He didn’t have to find a co-founder. He didn’t have to validate the market. He had to know what a working Sonos client looks like (he’s a user) and have access to a tool that translates specifications into working code. Those two conditions held for him, and so the app exists.

Multiply this across the long tail of abandoned-by-vendor software, IP-attorney-style personal needs, and this could have been an app annoyances, and the supply of personal software increases by some large multiple over the next five years. None of it is in the SaaS-MRR economy. Most of it never gets shipped to anyone. But it changes what users will tolerate from vendors — the threshold for this is so bad I’ll just build my own fell.

What an indie SaaS founder should take from this

You are now competing with users’ weekends, not just other SaaS companies. If your product solves a problem narrow enough that one motivated user could vibe-code a replacement, your moat is your distribution and your maintenance contract, not your code. The defensible products in 2026 are the ones where users couldn’t or wouldn’t replicate the solution themselves — multi-tenant data, network effects, regulatory burden, infrastructure cost. The product whose moat was we wrote a competent client app just got commoditized at the personal-use scale.

The IP attorney’s weekend is the leading indicator.