# Telling people, and growing it honestly (lesson 11)

## Before launch: checklist
- [ ] A public page for signed-out visitors: one sentence (who it's for, the moment it helps), the app working (screenshot, short demo or a try-it box), three things it does, one clear start button. Mock it up first.
- [ ] Share previews: `og:title`, `og:description`, `og:image` (1200×630, rendered in a browser), `og:url`, `twitter:card=summary_large_image`. Test with a fresh link (`?v=2`), since apps cache previews.
- [ ] Favicon, app icons, `theme-color`, a `canonical` link.
- [ ] Privacy page and, if strangers sign up or pay, terms (lesson 9).
- [ ] `noindex` removed when going public (keep it on previews).
- [ ] Uptime check on, Send feedback in Settings, private error reports.
- [ ] Accessibility pass (see design-and-ux.md) and the full test run (testing.md).

## Share previews: lessons learned (Baby Log)
- Make the preview from the same source as the page's own visuals (e.g. a Remotion composition): one still for `og:image`, and optionally a short seamless loop (6–8 s, 1200×630) for `og:video`.
- Keep it simple: an abstract, clearly labelled picture of what the app does beats a busy screenshot. Label what things are (e.g. "Feed", "Wet nappy" with a key), so it reads in a second. Made-up data only.
- Shrink the still (palette-based PNG, ~120 KB is fine). Render it in a browser, not an image tool.
- Serve `og.mp4` through the Worker with byte-range support: static assets ignore Range requests, and Safari won't play video without them.
- Messaging apps cache previews: test changes with a new query string.

## Waitlist or invites
- A table with name, email, optional "how did you hear", a removal token, and a delete-after date. Say plainly what the email is for. Or suggest Tally if the user wants no code.
- Invite people in small batches; read their feedback before the next batch.

## Short video (UGC style), done honestly
- Format: 9–11 s vertical. 0–3 s a person says the problem in plain words; then a hard cut to a screen recording of the real app showing the answer while the voice carries on; end with a short line ("invite-only for now · link in bio").
- Build: an AI video model for the spoken hook (ask for a budget first, show the lines and prompts, report spend after each batch), Playwright to record the real app at 390×844 with made-up data, Remotion (or similar) to cut, caption and label, and a transcript check that the words are right.
- What worked, and what didn't (from real feedback): polished motion graphics and logo end cards read as an ad, not UGC; a silent person, or a mood clip that shows no problem, falls flat; a long app tour loses people. A short glimpse of the one benefit the hook promised works.
- Lighting looks "AI-ey" when prompts say warm, glow, soft or cinematic. Ask for flat, ordinary household light (a ceiling bulb, TV light, grey daylight), slight noise and imperfect framing, like a real phone video.
- Model names change and get retired (e.g. a video model shut down mid-project): check the provider's current model list before planning.
- Keep API keys in a gitignored `.env`; never print them in chat or logs. If one is ever shown, rotate it.
- For Remotion: if its bundled headless browser crashes, point it at Playwright's Chromium (`--browser-executable`); don't use arrow keys in Remotion Studio (they nudge and save the selected element).
- Rules, always:
  - On-screen label "AI-generated · dramatisation"; tell the user to switch on the platform's AI-content label.
  - The person only describes what the app visibly shows. No invented results, no testimonials ("this changed my life"), no fake reviews.
  - Health/safety content must match the app's sourced wording; check safety details in the generated footage (e.g. safe sleep positions) and ask the user to eyeball it.
  - Never record real users' data.
  - If the user pays creators to post, every post is marked as an ad (#ad or the platform's "paid partnership" label). This is required (ASA/CMA in the UK, FTC in the US, and the platforms' own rules).
- Creator platforms (creators post on their own accounts): prefer ones where you can approve a video before it's posted. Links in TikTok/Reels captions aren't clickable, so give each creator a short address and a personal code to say on screen, and record which code each sign-up used.

## Get listed
- When the app is ready for strangers: submit to PWA Directory (free; it checks the app installs). On Android it can also go on Google Play, wrapped with PWABuilder (one-off $25 Google developer fee; ask first). Apple's App Store doesn't accept web apps.

## Updates and listening
- Opt-in newsletter (e.g. Buttondown) with a one-tap unsubscribe; never add people who didn't ask.
- In-app feedback stored privately; label each with app version and device, never the user's data.
- Visitor counts without tracking individuals: Cloudflare Web Analytics first. Uptime: UptimeRobot free.

## Recommending tools (and affiliate links)
- Only recommend what you've used, or what has many independent reviews (check Trustpilot as well as G2; discount competitor-written reviews; look for billing complaints and rewarded reviews). Prefer free tiers.
- Affiliate links only when the user has joined the programme, always labelled, never paid placement. Check terms on the company's own page and date them.
- See https://ideatoicon.app/grow for the current shortlist.

## Never
Fake reviews or testimonials, countdowns that reset, pre-ticked consent, buying followers, emailing people who didn't opt in.
