I got an email last week that wasn't a bug report or a feature request. It was a thank you note. For a sentence in a privacy policy. That told me more about distribution than any analytics dashboard ever has.
The Seduction of the Perfect Demo
We all know the dream. The perfectly choreographed two-minute demo video. The one with the slick animations, the seamless flow, the feature reveal that makes everyone go “aha.” I’ve spent weeks of my life chasing that dream, nudging keyframes and tweaking easing curves to get a button to feel just right for its three seconds of screen time.
The demo is the hook. It sells the vision. It gets you the retweet, the upvote, the spot on a curated list. It shows what is possible inside the world you’ve built, and there is immense value in that. We build things to solve problems, and the demo is our best attempt to show someone we’ve solved theirs.
But the demo is a promise, not a relationship. It's the highlight reel. Distribution, the thing that actually gets your app from the store to someone’s home screen and keeps it there, is built on everything that happens after the video ends. It's built in the quiet moments of trust.
The App Store's First Question
I once had an update rejected by App Review for a single line of text. Not a crash, not a bug, but the justification string for a permission request was deemed unclear. My first reaction was annoyance. I wanted to ship. The feature was done, the code was clean.
Then it hit me. App Review was acting as the first line of defense for a user who hasn't even downloaded the app yet. They were stress-testing my trustworthiness before anyone else had the chance. That rejection was a gift. It forced me to think about the very first question my app asks a new user, which is never “What do you want to accomplish?” It’s always some variation of “Can you trust me with your data?”
When that system dialog pops up—the one asking for access to Contacts, or Photos, or Location—your beautiful demo is nowhere to be found. The user is alone with a choice. All they have to go on is your app’s name, its icon, and a short sentence you wrote in a plist file. In that moment, your entire brand is distilled into a single, stark question of trust. Get a “Don’t Allow” and your best feature may as well not exist.
Support Pages as Sales Tools
Most founders treat support and privacy pages like legal chores. They are the last thing you write, usually by modifying a template that reads like it was designed to be incomprehensible. The goal is compliance, to check a box for the App Store. This is a massive missed opportunity.
I’ve come to see these pages as some of my most effective marketing materials. The people who read them are the people you want most as customers. They are the careful ones, the thoughtful ones, the ones who do their research before committing. They’re looking for signs that a real human is behind the app, that their data will be respected, and that if something goes wrong, they won’t be shouting into a void.
We had a support document that was just a dry list of features. I rewrote it to explain *why* the features exist and how they fit together. A week later, a new five-star review mentioned it by name: “I was on the fence, but their support page was so clear and helpful I knew the app would be well-thought-out.” That’s a conversion that happened a thousand miles away from a demo video.
Writing for Humans, Not Lawyers
The central lesson here is that trust is a feature. Your privacy policy, your permission strings, your support docs—these aren’t ancillary documents. They are part of the core product experience. They deserve the same design- and user-centric thinking that you apply to your main interface.
My process for this is simple. I write the first draft in the plainest language I can. I explain what the app does, what data it needs and why, and how to get help. Then I send it to a lawyer to make sure I haven't left out any required disclosures. Their first draft back always looks like a car rental agreement. My job is to translate it back to something a person might actually read without their eyes glazing over.
This isn't about hiding things in fine print. It’s the opposite. It’s about making your commitments so clear that they build confidence. You aren't just aiming for a user's compliance; you're earning their conviction that you are on their side.
A great demo shows what your app can do. A great privacy policy shows who you are. In the long run, people bet on who you are.