# Collapsing Distribution Cost Is What Unlocks Personal Software ## Claim Software for an audience too small to justify itself becomes buildable only when both the cost of making it and the cost of getting it onto someone's device fall to near zero, and distribution is usually the later of the two to fall. <!-- atomicity: 1 idea ✓ --> ## Evidence **Source**: [[3. Resources/Readwise/Articles/PWAs Personal Web Apps|PWAs: Personal Web Apps]] — Mattias Geniar The artifacts make the case better than an argument would: currency converters for one holiday, three games in Dutch for his own children, a frame grabber because iOS lacks one, a video speed tool because iMovie caps at 2×. None would ever justify an app store submission. All of them exist. Two costs had to fall together. Build cost fell to a prompt and a wait. Distribution fell to a monorepo with automatic deploy on the one side and a two-click home-screen install on the other — no store, no review queue, no signing ceremony. The rules he extracted are what makes the resulting software usable rather than merely possible, and the framing is the reason to trust them: > [!quote] > Every rule in there is something I got wrong first. His labelling practice deserves copying independently of the argument: *"The skill itself is AI-generated, distilled from the CLAUDE.md file that repo runs on. This post I wrote myself."* ## Scope & conditions - Holds where the audience is small enough that no reduction in build cost alone justifies the distribution overhead. Where distribution is already free, the binding constraint is elsewhere. - Collapsing build cost does not make hard software easy — it makes *small* software worth starting. - The corollary is that platform gatekeeping is a tax levied almost entirely on small-audience software, and barely at all on large-audience software. - Personal-scale quality is a real limit and he says so plainly: not commercial-grade, but sufficient for the problems it was built for. ## Links - [[Personal Knowledge Management MOC]] — the economics that make single-user tooling worth building at all - [[3. Resources/Permanent Notes/Personal Fit and Shareability Trade Off in Vibe-Coded Software]] — the quality boundary this claim runs into once the audience grows - [[3. Resources/Permanent Notes/Ownership Beats Disposability in EdTech Tool Design]] — extends: what changes when the person using the tool also owns it - [[3. Resources/Permanent Notes/Agents That Install Skills Create an Unreviewed Supply Chain]] — contrasts: the risk introduced when the extracted rules get shared as a skill - [[3. Resources/Permanent Notes/Judge a Tool by Who Controls It Not What It Does]] — applies-in: why no-store distribution matters beyond convenience - [[3. Resources/Permanent Notes/A Nightly Agent Rebase Makes a Personal Fork Cheap Enough to Keep]] — extended by: maintenance, not writing, kills personal software; a nightly rebase removes that cost for small patch sets (Crawshaw).