Lesson 11 · about 55 minutes
Tell people about it
Your app works. Now people need to find it, understand it in a few seconds, and trust it. This lesson covers the page that explains it, how a shared link looks, a waitlist, a short video, hearing back from the people who use it, writing to people one careful email at a time, and helping AI tools describe your app properly, all without tricks.
A public page with the value up front, Open Graph share previews, a waitlist (built in or Tally), a short UGC-style video made honestly, a newsletter for updates, feedback plus uptime so you know it's working, outreach emails you approve one by one, and an llms.txt so AI tools understand your app.
A public page for people who aren't signed in, and share previews (og:image, plus og:video if you like). Add a waitlist in your own database or with Tally, and a short video: an AI-made hook, a real recording of your app, cut in Remotion and clearly labelled. Buttondown handles opt-in updates; feedback, Cloudflare Web Analytics and UptimeRobot tell you how it's going. Outreach goes out from your own domain with Cloudflare Email Sending, each email tested on you first, and an llms.txt plus Markdown pages help AI tools read your app.
What you'll make
- A page that says who it's for and what it does, in seconds
- Links that look good when shared
- A waitlist, a short video and a way to send updates
- Feedback and an alert if the app goes down
- A few honest emails, each one checked by you first
- A monthly check of what AI tools say about your app
You'll need: an app people can use (lessons 2–10).
One sentence for who it's for
Before any page or video, write one sentence: who it's for, and the moment it helps. Everything else follows from it.
- "A feeding log two tired parents can share at 3am."
- "Every match you play, your runs and wickets, season by season."
A page that explains it
People who aren't signed in should see what it does, not a login box. Lead with the benefit, show the app working, then how to start.
Lesson learned: a small interactive piece, like a try-it box, explains an app better than any paragraph.
A preview when the link is shared
Most people will first see your app as a link in a message. With a share preview it shows a picture and a title; without one it's a bare address.
A picture, your app's name and a short line, not a bare link.
These are the Open Graph tags (og:image, og:title, og:description) in the page's head. A 1200×630 image works almost everywhere.
Lesson learned: a simple, labelled picture of what the app does reads better than a busy screenshot. You can even make it move: a 6–8 second looping preview (og:video), served by your Worker so Safari can play it.
My old preview still shows
?v=2 to the end) to see the new one.A waitlist or an invite
Not ready for everyone? Let people join a waitlist, or give out invite codes. It's also how you find your first testers.
Prefer a form you don't build? Tally makes one in minutes and has a generous free plan.
A short, honest video
A 9–11 second video works well on TikTok and Reels: a person says the problem in their own words, then a quick glimpse of your real app answering it. We made these for a real app with an AI-generated person and a screen recording of the real app.
over the guide
What we learned making them: polished animations and logo cards feel like an ad, a silent person falls flat, and a long app tour loses people. The winner was one short glimpse of the exact benefit the hook promised. And ask for ordinary, slightly imperfect lighting; "warm" and "cinematic" look AI-made.
- Label it. Anything AI-made says "AI-generated · dramatisation" on screen, and you switch on the platform's AI label when posting.
- Only show what the app really does. Numbers on screen must be real; no invented results.
- No fake testimonials, ever. An AI person can say the problem, not "this changed my life".
- Paid posts are ads. If you pay creators to post about your app, their post must say so (#ad or the platform's "paid partnership" label).
- Agree a budget first. AI video is charged per clip; your agent should ask before spending.
Our pipeline: Gemini video for the 8 s hook, Playwright to record the real app at 390×844, Remotion to cut, caption and label, then a transcript check of the spoken words.
Updates people asked for
When people want to hear from you, a short newsletter keeps them close: what's new, what's coming. Only to people who chose it, with a one-tap unsubscribe.
We suggest Buttondown: simple, indie, and a free tier to start.
Hear back, and know it's working
Two quiet things that make a big difference: a Send feedback button in Settings, and an alert if your app goes down.
Uptime: UptimeRobot's free plan. Visitor counts without tracking people: Cloudflare's free Web Analytics.
Reach out, one email at a time
Some of your best early help comes from a short, honest email: to a tool you recommend, a club that might use your app, or someone who could feature it. Your agent drafts each one, you read it as the other person will, and nothing goes until you say yes.
Your agent turns on Cloudflare Email Routing so anything@yourapp.com reaches your inbox, then sends from hello@ with Email Sending. Testing to yourself is free; emailing other people needs Workers Paid ($5 a month).
A handful of emails needs no Worker code. "Queued for" also means it was accepted.
What we learned from our first emails:
- Open the test like they will. Our first tests said "sent", but the whole email had ended up in the subject line. Only reading them on a phone caught it.
- Find the real address. Take it from the company's own contact page. Never guess one.
- No numbers you haven't agreed. If a budget or price appears in a draft, it should be one you chose.
- Say why them. One true sentence about why you're writing to this person beats any template.
My test email went to spam
@yourapp.com with "Never send it to Spam".I want to reply from hello@, not my own address
Be found by AI tools, honestly
More and more people ask ChatGPT, Claude or Perplexity instead of searching. They tend to repeat pages they already trust: well-known lists, forums, directories and guides. You can't buy your way in, but you can make your app easy to understand, and check what they say.
This month's question"What's an easy app for tracking my cricket stats?"
- Same for everyone. Never show AI bots something people can't see. Search engines treat that as cheating, and it breaks trust.
- Get listed where they already look. Directories, "awesome" lists on GitHub, and honest answers where people ask questions. Not more blog posts.
- Check, don't guess. Ask the same questions each month and keep the answers, so you can see what changed.
My app isn't mentioned at all
Cloudflare's dashboard shows which AI crawlers visit (AI Crawl Control), so you can see who's reading without adding anything to your app.
Grow without tricks
The fastest way to lose trust is a trick: fake reviews, a countdown that resets, an email list people didn't join. Your agent follows the same rules as this course.
The rules: honest claims, labelled AI, opt-in email, real reviews only, and a delete button that works. Then point people to Growing your project for tools we'd use ourselves.
Ready for strangers? List it where people look for web apps, like PWA Directory. On Android it can also go on Google Play, wrapped with PWABuilder; Apple's App Store doesn't take web apps.
Did it work?
Tick these off. They're saved in this browser, so you can come back later.
- My app has a page that says who it's for and what it does
- Shared links show a proper preview
- People can join a waitlist or get an invite
- Anything AI-made is labelled, and nothing claims what the app can't do
- I know if it's up, and people can tell me what's wrong
- I sent my first email only after reading a test of it
- I know what AI tools say about my app, and nothing is shown only to bots