The reviewer walks the real flow

Mend is a calm, private place for two people to notice how they're doing, slow down in difficult moments, and find their way back to each other. That's intimate territory. So the last stretch before submitting it to the App Store wasn't about features. It was about making sure the app behaves exactly the way it says it does.

Here's what that looked like in practice.

Consent before any words leave Mend

A few of Mend's features send words to a model to help you say something well. Before that ever happens, Mend asks once, on the way in, right after you give your name. The same switch lives in Settings.

Three details made it real rather than decorative:

• The copy names what is sent. It was written against what the request actually contains (your partner's first name and the words you approved), not against how the feature feels.
• The check lives on the server. Consent is verified in the same transaction as the work, at every call site that reaches the model. The app's screen decides only what's drawn; it can't be the thing that lets words through.
• Consent has a version. If the explanation changes in a way that matters, Mend asks again instead of quietly inheriting an old yes.

The interesting part was the no. The first version treated a refusal like an error. But "Not now" is an answer: nothing else in Mend is withheld, and the app doesn't nag again at every launch.

A refusal with a remedy is not a failure.

Permissions should explain themselves

An early build asked for camera access, and Mend never opens the camera. That's the kind of thing that erodes trust in a second, so it went.

Every remaining permission string now says why, in one sentence, from the user's side: what you get by allowing it, not what the API needs.

The listing says what the build does

App Store copy drifts. You write it early, the product changes, and one day the listing promises something the build doesn't do. Before submitting, I rewrote the listing line by line against the actual build: every claim either maps to a screen you can open, or it's gone.

The reviewer walks the real flow

Review notes often come with a demo account and a note that says "use this code". Mend's don't. The reviewer is walked through the real onboarding, the real consent step and the real pairing flow, described the way it can actually behave, including what happens when you say no.

If the reviewer can't reach a feature the normal way, a user can't either. That's a bug, not a review problem.

A real mailbox

Last, a small one: the support URL has to lead somewhere a person can actually write to and get an answer. So the landing page got a real support page and a real mailbox, the day before submission, which is about when these things always get done.

---

Mend is on the bench now. If you're building something that handles people's private moments and you want it shipped with this kind of care, let's talk.