Draft / Experiment · 2026

Features for One.

Software was built around the economics of scarcity. When changing it becomes cheap enough, a different question becomes possible: why should everyone have to use the same product?

This page can adapt too

01

Software should adapt to people.

Make the feature for one person. Change the interface for their ability. Change the affordance for their device. Change the presentation for their language. Change the experience for the moment they’re in.

PersonAbilityAffordanceDeviceMoment
02

Start with the pure experience.

Before acquisition. Before engagement. Before monetization. First make the thing worth using. Then earn the right to ask something of the person using it.

Pure is the experience before someone begins extracting value from the person using it.

Design that experience first. Identity, measurement, promotion and monetization can enter later—but each should justify what it takes away from the original experience.

No login screen unless identity is actually necessary.
No password creation when there is a better way.
No email modal before I’ve seen what you made.
No popup demanding attention I didn’t offer.
No advertising that consumes the experience it supports.

Two rules

Adapt to the person.
Earn every interruption.