SaaS et tech
Mobile App Launch Playbook
An app store listing has room for a few screenshots and a short description, and people often decide whether to install long before they reach it. This playbook builds the web pages that answer their questions first: what the app does, who it is for and how it compares with what they use today.
À qui il s’adresse
Founders and small product teams releasing a new iOS or Android app who have, or can add, a website for it.
Avant de commencer
- A one-sentence description of the job the app does, written the way a user would describe it.
- The store listing text and screenshots, so the website and the listing say the same thing.
- A landing page with links to both app stores.
- A list of the questions support or beta testers ask most often.
Étape 1
Plan around pre-install questions
Find out what people search for before they look at a store listing.
- List the tasks the app helps with and the questions people search while trying to do each task without it.
- Note the apps and manual methods people use today, so comparisons are honest and specific.
- Decide which questions deserve a full article and which belong on the landing page.
- Choose one cluster to cover first, built around the main thing the app does.
Étape 2
Create web companions to the listing
Write pages that explain the app in more depth than the store allows.
- Write a feature overview page with real screenshots and a plain explanation of each screen.
- Write how-to articles for the main tasks, showing both the manual method and the app.
- Write a privacy and permissions page that explains why the app asks for each permission.
- Keep feature names and screenshots identical to the version in the store.
Étape 3
Publish with the release
Make the web pages and the store listing go live together.
- Publish the landing page and overview before the store listing is approved, ready to go public with it.
- Link every article to the store badges and to the overview page.
- Add a changelog page and post an entry for every release, linked from the store listing.
- Plan the next articles from the questions that arrive in the first weeks.
Étape 4
Measure installs from the web
Separate visitors who arrive from search from those who arrive from the store.
- Use the store consoles’ campaign links on your website, so web-referred installs are counted separately.
- Check which articles appear in search in your search console and for which questions.
- Update screenshots and how-to steps whenever the interface changes.
- Retire articles about features that no longer exist rather than leaving them live.
Erreurs fréquentes
- A website that repeats the store description and adds nothing a visitor could not read there.
- Screenshots from a beta that no longer match the released app.
- How-to articles that only work if the reader already has the app installed.
Où Opus Rank vous aide
Des tutoriels pour les parties de ce plan que vous pouvez réaliser dans Opus Rank.
- Build a topical map
Plan the clusters of task and comparison articles around the app.
- Generate an article: every option on the form
Choose the article type and audience for each how-to.
- Featured and in-article images
Add images to articles alongside your own screenshots.
Playbooks associés
Transformez un playbook en articles publiés
Planifiez les sujets, générez des brouillons dans votre propre ton et publiez-les sur votre site depuis un seul espace de travail.