Naming a thing after what it already meant.

The brief I gave myself

Wristed started as a founder-led product, which means the brief was mine to write. I'd been collecting for years, and like most collectors I'd ended up running my collection across five places that were never meant to talk to each other: a spreadsheet for values, Instagram DMs for buying and selling, a Reddit thread for opinions, a shoebox of service receipts, and whatever insurer's form happened to be open when a new piece arrived. None of it was connected, and none of it was built for the actual shape of the hobby.

That's not a business insight so much as a personal irritation, but personal irritations make the best briefs. The job wasn't "build a watch app." It was: build the thing I wished existed, for people exactly as particular about their watches as I am about mine.

Why "Wristed" and not something invented

Collector slang already had a word for this. "Wristed" is genuine horological vernacular, used the way "well-wristed" gets said about someone whose watch clearly matters, and "under-wristed" gets said, only half joking, about someone whose doesn't. I didn't coin it. I borrowed it, on purpose.

That's a copywriting decision as much as a naming one. An invented name has to earn recognition from nothing. A borrowed piece of real slang arrives already understood by exactly the audience it needs to land with, and it signals something a made-up word can't: that whoever built this actually spends time inside the community, not just researching it. The whole voice of the site leans on that same borrowed vocabulary rather than generic startup copy, because once you've picked a name that's already true, writing around it in your own invented language would undercut the whole point.

Five pillars, one dataset

The product is organised around five areas: Community, Commerce, Knowledge, Care and Discovery. It would have been easy to ship that as five separate features bolted together, but the architecture decision that actually matters is underneath: every pillar reads from and writes to the same vault record for a given watch, rather than keeping its own copy of the truth.

The clearest example is Care. Log a service in the vault and that same entry is what a collector would eventually hand to an insurer as evidence, rather than being a separate form filled in from memory months later. That's a solution-architecture choice before it's a feature: decide once what the canonical record of a watch looks like, and let every surface of the product, community feed, marketplace listing, insurance application, read from that one place instead of asking the collector to repeat themselves. The alternative, five disconnected tools that each ask for the same information in a slightly different shape, is exactly the problem the brief was written against.

Web app, native app, one architecture

Wristed isn't one build wearing two skins. It's a public web app and a native iOS and Android app, built with Expo, doing genuinely different jobs off the same underlying platform.

The web app is the front door: the marketing site, the blog, the editorial and wiki content, RSS feeds, and a browse-only version of the marketplace. That's a deliberate choice, not a limitation, because that's the surface Google and AI crawlers can actually read, and the surface a new collector lands on before they've decided to trust anyone with their collection. Nothing that matters for discovery sits behind a login.

The native app is where the collection actually lives. Logging a watch into the vault, capturing a wrist check with the camera, unlocking the app with Face ID, getting notified when a listing you're watching moves: none of that works as a web page, because it depends on hardware and permissions a browser can't offer the same way a phone can. iOS supports tablet layouts too, since a collector reviewing their vault on an iPad wants the same depth as on a phone, not a stretched version of the mobile screen. And because the app ships through Expo's over-the-air update path rather than a store review cycle for every change, most of the product can move at the same pace as the web app does, which matters when the two are meant to feel like one product rather than a website with an app bolted on.

Designing for a dial, not a dashboard

Most social products default to a warm, rounded, slightly cheerful visual language, because that reads as approachable. I deliberately didn't want that here. Watches reward precision: a well-cut dial, tight tolerances, restraint. So the interface runs on the same instincts, small monospace labels doing the work a caption font usually does, generous whitespace instead of card-shadow clutter, a light cream theme and a proper noir dark theme rather than a token dark-mode afterthought. The aim wasn't to look like a fintech app or a social feed. It was to look like it understood what a dial looks like when it's done properly, because the audience will notice immediately if it doesn't.

Writing to three readers in one voice

The "who we're for" copy on Wristed splits deliberately into three: the new enthusiast who just bought their first Seiko, the active collector managing a real portfolio, and the specialist who wants complication atlases and movement architecture. That's not audience segmentation for its own sake. It's an admission that "watch collector" isn't one reader, and pretending otherwise produces copy so general it convinces nobody. Each paragraph is written to a real, specific person I could picture, not a persona document, which is the actual difference between copy that sounds like marketing and copy that sounds like someone who gets it.

Where it stands

Wristed is pre-launch, building toward the waitlist converting into a working beta. The reasoning above is the part that doesn't change between now and launch: the name, the shared data model, the visual restraint and the three-reader copy are the decisions everything else gets built on top of.

Visit Wristed ↗︎ · Back to selected work