← All tags

Launching an app

What it takes to put a new app in front of people: the launch website, being found in search and AI assistants, and the questions to answer before day one.

Why does every app we launch get its own website?

Because the website is where most people meet an app for the first time. People search for their problem, not for an app whose name they have never heard, so a launch site with clear pages about the problem is how a new app gets found. That holds whether the app is for the public or for one business and its own customers.

AI assistants such as ChatGPT, Gemini and Perplexity now answer many of those searches. They answer from pages they can read, so every site we launch states plainly what the app does, answers common questions, and carries structured data plus an llms.txt file that maps the site for AI tools.

What belongs on the website instead of in the app?

Questions like "Is it free?", "Does it work on my phone?" and "Who is behind this?" Answering them on the website keeps every screen inside the app about doing the job.

Each launch site also carries the app's own look and voice, from the dark theme and neon green of OwnSites to the graph-paper pages of Homeroom. The posts below explain how we put one together.

Got an idea of your own?

Tell us your idea