“Everything you watch. All in one place.” Eight words to make an unfamiliar product legible. No provider names, no explaining what aggregation means. Apple adopted it for advertising.

Where the line shipped first. Each phrase of body copy names a real behavior, and the two buttons split the audience. A tour for the cautious, a start for the ready.

The earlier pass positions by category and mechanics. The shipped version positions around the person. Same promise, different subject.

An empty state has nothing to show, so the words do all the selling. I led with the benefit and wrote the button to start setup. A dead end turned into a beginning.

I named the sections to read instantly across iPhone, iPad, and TV. Up Next held everything you'd started, regardless of service. What to Watch recommended across the whole ecosystem.

Upgraders didn't choose a new app. An update turned Videos into TV. One modal to orient them and answer the only question that mattered. Where did my stuff go?

Setup asked for access before people had felt the payoff, so the copy did trust work. It framed the ask around the benefit and kept the privacy disclosure plain.

An aggregator is only useful if every action tells you where you'll land. “Play in FXNOW,” “Open in iTunes,” “Remove From Up Next.” Precise labels let people move with confidence.

The Store sat inside a utility, so the copy sold without turning the app into an ad. “Season 1 Now Available” for streaming, “Now Available to Buy” for purchase.

An example screen from the Google Hub photo setup flow. It let people choose the kinds of photos they wanted to see, so their display filled with the moments that mattered to them rather than everything at once.

A recurring purchase living inside a free app people trust with their memories. The copy led with the value. Your best photos, printed and delivered every month. Pricing, materials, and terms stayed up front.

Prompts that explained why Google was asking and how answers would improve the product. Light, optional, and quick, so contributing never felt like a chore.

Trash explained the 60-day window before anything is permanent. Archive clarified that hidden items still live in albums and search. Both told people where their content went.

Freeing up space makes people nervous, so the copy did the reassurance in the same breath as the ask. Removed from this device only, safely backed up, still viewable any time.

Most testers' first look at TestFlight. I led with the tester's contribution. What the product is, what your role is, why it helps developers, all in one sentence that set the tone for every screen after it.

I skipped “beta testing,” “builds,” and “pre-release software” and introduced one concept at a time through what the tester can do. Give feedback, test different versions, stay up to date.

Invitations, notifications, the loading screen. Identical language across every entry point. One name per thing, because a tester who sees two names assumes two things.

The small copy that does TestFlight's real work. What am I testing, what changed, how do I send feedback, how do I stop. Each screen answers its user's immediate question first.

The same welcome idea from iOS, trimmed to survive the 10-foot reading distance, so the product sounded the same no matter the screen size.

One instruction and one promise. Enter your code, and we'll install the app. With a remote as the only input, nobody should wonder what to type or what happens next.

“What to Test” notes, expiration dates, and actions like Install kept scannable from the couch. A tester who can't tell what's new can't test what matters.

TestFlight on Apple TV only shows Apple TV apps. The settings note says it plainly, once. Repeating a caveat teaches people to skip it.

Featuring can give an app visibility most developers can't reach on their own, but the path to consideration wasn't always clear. Nominations gave developers a way to raise their hand.

The sidebar tab initially said Featuring. Developers know what it means to be featured on the App Store, but Featuring as a label could confuse them. Is it a status, a request, a report? I worked with the team to change it to Nominations. It names the action a developer takes here, and it ties into the language on the intro screen.

Since the feature was new, the strategy was to give a brief overview of what featuring is, tie nominations to featuring, explain how the process works, and set expectations. One sentence for each job, then a single call to action.

The first step had to move quickly. What this is, what you can submit, why it's worth your time. Too much excitement would overpromise. Too much process would shrink the moment. The copy stayed direct, practical, and encouraging.

Explaining why your app deserves featuring is hard to answer cold. The copy made the blank fields feel less blank while leaving developers room to tell the story in their own words.

The trust lived in the details. Field labels, helper text, date guidance, confirmation language. It mattered most in the places people were most likely to hesitate.

Submitting had to feel complete and worthwhile without feeling like a promise. Apple would review and decide. Encouraging, but precise.

Developers got a clearer way to share meaningful work. Apple got a structured way to see what was coming. For smaller teams without built-in visibility, that mattered.

The same positioning carried through developer-facing content explaining how featuring works and what makes a strong nomination. Helpful, clear, and careful about the promise.