Back to article

Revision history

An App Too Small to Exist

Every saved editorial version remains available. Text, structure, images, diagrams, and embeds are tracked as part of the article rather than flattened into one edit summary.

1 revision

Current version: v1

  1. Version 1Current

    Initial publication

    Initial publication arguing that Apple’s generated Safari extensions reveal a category of personal, temporary software that was previously too specific and too small to become a product.

    1,677 words2 sections3 images

    July 27, 2026

    Kris Haamer

    Visuals in the initial version

    A diagram showing the old browser extension journey from annoyance through search, comparison, installation and use.

    A diagram showing the old browser extension journey from annoyance through search, comparison, installation and use.

    Previously, even a tiny irritation had to become a market.

    /blog/an-app-too-small-to-exist/01-old-extension-economy.svg

    A browser diagram showing a natural-language request becoming a local Safari extension.

    A browser diagram showing a natural-language request becoming a local Safari extension.

    The extension can arrive before it has a name.

    /blog/an-app-too-small-to-exist/02-prompt-becomes-extension.svg

    Three stacked interface layers showing the shipped website, a generated personal layer and the interface the user actually uses.

    Three stacked interface layers showing the shipped website, a generated personal layer and the interface the user actually uses.

    The product team designs the lower layer. The user increasingly controls the last one.

    /blog/an-app-too-small-to-exist/03-website-is-not-final.svg

Help improve this website?

Optional Google Analytics and Microsoft Clarity measure content performance and usability. They load only if you allow them. Form values, email addresses, and chat messages are never included in analytics events.