What precision actually costs
Before Apple, I thought I cared about craft. I had standards, I sweated details, I pushed back on work that felt unfinished. But eighteen months embedded with Apple's interactive design team — working on product launch experiences for iPhone 13, iPad Pro, and iPad channel initiatives — recalibrated what 'caring about craft' actually means.
At Apple, precision isn't a value. It's the baseline. Nobody congratulates you for getting the padding right. Nobody notices when your type scales perfectly at every breakpoint. These things are simply expected, at every review, on every deliverable, without exception. The question is never whether the work is precise — it's whether the precision is serving something worth serving.
"Precision without purpose is just expensive. At Apple, every detail had to earn its place by doing something meaningful for the person using it."
What the process taught me
The process at Apple was the most rigorous I've experienced, and also the most instructive. Every design decision went through layers of review — brand, engineering, legal, marketing — before anything was approved for production. This wasn't bureaucracy for its own sake. It was a mechanism for catching things that individual designers and teams miss when they're too close to the work.
I learned to welcome that scrutiny. The reviews that felt the hardest in the moment — the ones where a detail I'd spent two days on was sent back with a single comment — produced the cleanest outcomes. The feedback wasn't about my judgment being wrong. It was about the work not being done yet.
There's a version of that lesson that's easy to misapply: you don't need Apple's review infrastructure to benefit from the underlying discipline. You need the habit of asking, at every stage, 'is this actually finished?' Most of the time, the honest answer is no.
"The reviews that hurt were the ones that were right. Learning to distinguish between feedback that improves the work and feedback that deflects it is one of the most valuable skills in a senior design career."
The thing about scale
When you design for apple.com, you design for hundreds of millions of people. The numbers aren't abstract — they change how you think about every decision.
A one-pixel positioning error that looks fine on your monitor looks wrong on a specific combination of display, OS, and browser that sixty million people are using. An interaction that feels smooth at 60fps on your M2 feels broken on hardware three generations older. A headline that reads clearly in English can break spectacularly in German or Arabic.
This isn't unique to Apple — it's what designing for real scale feels like. But experiencing it firsthand changes the way you approach the work. You stop thinking about your design as a finished object and start thinking of it as a set of decisions that will be applied to contexts you can't fully anticipate.
That shift — from artifact to decision — is the most lasting thing I took away from the eighteen months.
"At scale, your design isn't what you made. It's how your decisions behave in the hands of people you'll never meet, on devices you've never tested, in contexts you didn't imagine."
What I carry forward
I left Apple a different designer than I arrived. Not because I learned new tools or new techniques, but because the standard of what 'done' means was permanently reset.
I carry that standard into every project I take on — at Cash App, at vCluster, in everything I build independently. The specific context changes. The expectation that every decision can be justified, every detail can be defended, and every pixel is an opportunity to demonstrate care: that doesn't change.
If you get the chance to work somewhere that holds genuinely high standards, take it. Even if it's hard. Especially if it's hard.