There's a particular kind of exhaustion that comes from using software designed for someone else.
It's the task app whose confetti animation sets your teeth on edge. The calendar that buries the one view you need under six you don't. The journal that gamifies your emotional life with streaks, then punishes you for a bad week. The notification that lands in your nervous system like a dropped pan.
If you're neurodivergent, or chronically ill, or dealing with sensory stuff, or just a person with preferences, you already know this feeling. You've been managing around it for years: turning off sounds, hiding tabs, paying for the pro tier to unlock the setting that should have been on by default. Accessibility, for most apps, is an afterthought bolted onto a product designed for someone else's brain.
What if it wasn't?
That's the quiet premise of a spec. A spec doesn't hand you a finished product with your name typed into a welcome screen. It gives you the blueprint, and then lets Claude build the app around you. Not around the statistical average user. You.
Want a task app with no streaks, no gamification, and a single unambiguous "next thing"? Build that. Want a journaling app that never sends you a reminder, never shows a word count, and opens to a blank page with no decoration? Build that. Want a focus timer that starts in silence, ends in silence, and never flashes, pulses, chimes, or celebrates? Build that.
A short list of things a spec can accommodate that mainstream apps fight you on:
- High-contrast color palettes you actually picked
- Font sizes that don't reset when the app updates
- Flows with zero animation
- Interfaces with one button on screen, not twelve
- Sounds you chose, or sounds that don't exist
- Language that doesn't infantilize you
- Data structures that match how you think, not how a product manager thinks you should
- Features you will never use, permanently removed instead of hidden in a submenu
None of this is radical. It's just expensive. A product team serving a million people can't ship a million versions, so they ship one and call the settings menu "accessibility." That compromise is the air we breathe. It's so familiar we stop noticing we're breathing it.
A spec is a different deal. You're the only user. The default is you.
There's a second thing that happens, which is harder to name. When you stop adapting to software, a little of the energy you spent adapting comes back. Not a lot. You still have to live in the rest of the world, which was also not designed for you. But the corner of your day that used to be friction becomes the corner of your day that isn't. That adds up.
Accessibility as a toggle will always be a second thought. Accessibility as the starting point is something else. It's what happens when the tool is built for one person and that person is you.
The cheapest, fastest way we've seen to get there is a spec. Pick one. Build it. Change the parts that don't fit. The app you end up with will be weirder, smaller, and more yours than anything the App Store can sell you, which, it turns out, is the whole point.
