Mobile app website content checklist
A mobile app site has to show the app on a phone, link to the right store and answer privacy and support questions before the stores ask. The usual delays are store listing assets, a privacy policy address and the real pricing.
Where to start
- Privacy and data. The stores need the policy address and honest data answers, so this page has the hardest deadline.
- Home. The app name, hero screenshot and launch status set the whole page and take one meeting to settle.
- Features and screenshots. Screenshots come in several sizes from several places, so ask early.
- Pricing and purchases. Prices in the store consoles must match the page, so confirm them before the copy is written.
- Support and help. A support address and five answers are quick to supply and are needed for the store listings.
The checklist
Home
Visitors arrive from a store listing, an ad or a search, and they need the app name, a phone screen and a download button in the first view.
- App name as listed in the stores Short text, requiredSpell it exactly as it appears in the App Store and Google Play, including any subtitle. Mismatched names confuse people who search for it.
- One-line description of the app Short text, requiredSay what a person does with it and who it is for, in under 12 words. Example: 'Water your houseplants on time with one tap.'
- Hero phone screenshot Image upload, requiredThe best single screen of the app, taken from a real device or simulator with demo data. Send the original file with no device frame added.
- Platforms supported Multiple choice, requiredTick every platform you ship today. Anything marked coming soon is handled in the launch status field.iPhoneiPadAndroid phoneAndroid tabletApple WatchWeb appMac
- Launch status Single choice, requiredPick where the app stands now. It decides whether the main button says download, join the beta or join the waitlist.Live in both storesLive in one storeBeta testingComing soon with waitlist
- App Store link LinkThe address of the listing on the App Store. Use the direct link from the store page, not a search result.
- Google Play link LinkThe address of the listing on Google Play. Check it opens on a phone that has the store installed.
Features and screenshots
People compare apps by screens and by the three things each one does well, and this page fails when it lists every feature.
- Top features with short descriptions Long text, requiredPick three to six features. For each, give its name in the app and one sentence on what the person gets from it.
- Store screenshots in original size Image upload, requiredThe same screenshots you uploaded to the stores, at their original size. The designer places them in device frames so they match the store listing.
- App preview video File uploadThe preview you made for the store as an MP4, or a link to a screen recording under 30 seconds. Send it without a soundtrack you do not own.
- Accessibility features Multiple choiceTick what the app supports today. Visitors with access needs look for this before downloading.Screen reader supportDynamic text sizingDark modeReduced motionHigh contrastCaptions
- Languages supported Short textList the interface languages by name. If translations are partial, say which parts.
- Latest release notes Long textThe most recent version number and what changed, in the words you gave the store. The page can show a short recent-updates list.
Download and requirements
A visitor on the wrong device or an old operating system leaves frustrated, so the page has to state what the app runs on.
- Minimum operating system versions Short text, requiredThe lowest iOS and Android versions the app supports, as in the store listing. Check them against the current build.
- Account needed to use the app Yes or no, requiredSay whether a person must create an account before using any feature. The page explains the signup step if so.
- Works offline Yes or noSay whether the main features function without a connection. If only some do, name them in the next field.
- Offline limits and sync details Long textWhat works offline, what needs a connection and when data syncs. Keep it to facts a support agent would also say.
- QR code destination LinkThe single address the QR code on the page should open. Smart links that route to the right store by device work well.
Pricing and purchases
Pricing confuses people when a free app has paid parts, so the page needs to say what costs money and how to cancel.
- Pricing model Single choice, requiredPick the one that best describes the app today. The page copy follows from it.FreeFree with adsFree with in-app purchasesPaid downloadSubscription
- Subscription plans and prices Long textEach plan's name, price, billing period and what it includes. List prices in the main currencies you sell in, and state the date they apply from.
- Free trial terms Long textLength of the trial and what happens at the end. Match the wording you submitted to the stores.
- How to cancel a subscription Long textThe steps a subscriber takes in each store, in your words. Link to the store's own help page if you prefer.
- Refund policy Long textSay who handles refunds, usually the store, and what you do if someone writes to you directly. Keep it consistent with your terms.
Support and help
Stores require a support address, and users go to the site first when something breaks, so this page deserves real answers.
- Support email address Short text, requiredA shared address several people read, such as support@. It is also the address the stores list for the app.
- Help centre or FAQ link LinkThe address of an existing help site. If none exists, the designer builds a short FAQ from your answers below.
- Top how-to questions Long text, requiredThe five questions people send most often, each with the answer you give. Include one about restoring purchases.
- Bug report process Long textHow someone reports a bug: a form, an in-app button or an email. Say which details you want, such as device model and app version.
- Expected response time Short textHow quickly you answer, such as 'within two working days'. Promise only what the team keeps to.
Privacy and data
Both stores require a privacy policy address and honest data answers, and the site is where users check them.
- Privacy policy address Link, requiredThe live address of the policy. The stores ask for it, so the site must carry the same page.
- Types of data the app collects Multiple choice, requiredTick what the app and its libraries collect. Match the answers you gave in the store privacy labels.Contact detailsLocationUsage dataDevice identifiersPurchase historyHealth or fitness dataDiagnosticsNone
- Store privacy labels match the policy Yes or no, requiredConfirm someone has compared the store privacy labels with the policy and they say the same thing.
- Third-party tools inside the app Long textAnalytics, ads, crash reporting and login providers, each with its name. The policy and the labels both have to include them.
- How a person deletes their account Long text, requiredThe steps in the app and an email route for those who cannot sign in. Check the rules where you operate and the store rules for account deletion.
- Aimed at children Yes or no, requiredSay whether the app targets young children. If yes, the rules where you operate may add duties for the site, so confirm who reviews it.
Press kit and brand
Journalists and bloggers need clean files, and the team usually has them in six places, so gather them once.
- App icon file File upload, requiredThe 1024 by 1024 pixel PNG used in the stores, with no rounded corners added. The designer applies the shape needed for each platform.
- Logo and wordmark files File upload, requiredSVG files of the wordmark, the symbol and a white version for dark backgrounds.
- Brand colours Colour, requiredHex codes from the app's design system or its icon. Name the colour the app uses for buttons.
- Brand fonts FontThe typefaces in the app and the store images. Say if they are system fonts, and which licence covers any custom ones.
- Short and long app descriptions Long textOne description of about 50 words and one of about 150, for press and directories. Use the store text if it is accurate.
- Developer name and legal entity Short text, requiredThe name on your developer accounts, and the registered company behind it. Check the rules where you operate for what the footer must show.
- Terms of use address LinkThe live address of the terms. If the app has paid plans, the stores expect it to be easy to find.
What clients get stuck on
Store assets in the right sizes
Screenshots live in a designer's file and in the store dashboards at several sizes. Ask for the original exports and the app icon master, so you do not rebuild or stretch them.
A privacy policy that does not match the app
Policies written for an early version miss new analytics or login tools. Ask whoever submits to the stores to compare the policy, the labels and the real SDK list before launch.
Pricing set in the store dashboards
Prices vary by country in the store consoles, and the founder may not know each. Ask for a screenshot of the console and decide which currencies the site shows.
Launch dates that move
Apps slip during store review. Ask what the site should say if approval is late, and build the buttons so one setting switches between waitlist and download.
Screenshots with real user data
Founders often capture screens from their own account, with names and locations visible. Ask for a demo profile, and retake any screen that shows personal details.
Copy the checklist
Plain Markdown you can paste into a doc or an email.
# Mobile app website content checklist
## Home
- [ ] App name as listed in the stores (Short text, required)
- [ ] One-line description of the app (Short text, required)
- [ ] Hero phone screenshot (Image upload, required)
- [ ] Platforms supported (Multiple choice, required)
- [ ] Launch status (Single choice, required)
- [ ] App Store link (Link)
- [ ] Google Play link (Link)
## Features and screenshots
- [ ] Top features with short descriptions (Long text, required)
- [ ] Store screenshots in original size (Image upload, required)
- [ ] App preview video (File upload)
- [ ] Accessibility features (Multiple choice)
- [ ] Languages supported (Short text)
- [ ] Latest release notes (Long text)
## Download and requirements
- [ ] Minimum operating system versions (Short text, required)
- [ ] Account needed to use the app (Yes or no, required)
- [ ] Works offline (Yes or no)
- [ ] Offline limits and sync details (Long text)
- [ ] QR code destination (Link)
## Pricing and purchases
- [ ] Pricing model (Single choice, required)
- [ ] Subscription plans and prices (Long text)
- [ ] Free trial terms (Long text)
- [ ] How to cancel a subscription (Long text)
- [ ] Refund policy (Long text)
## Support and help
- [ ] Support email address (Short text, required)
- [ ] Help centre or FAQ link (Link)
- [ ] Top how-to questions (Long text, required)
- [ ] Bug report process (Long text)
- [ ] Expected response time (Short text)
## Privacy and data
- [ ] Privacy policy address (Link, required)
- [ ] Types of data the app collects (Multiple choice, required)
- [ ] Store privacy labels match the policy (Yes or no, required)
- [ ] Third-party tools inside the app (Long text)
- [ ] How a person deletes their account (Long text, required)
- [ ] Aimed at children (Yes or no, required)
## Press kit and brand
- [ ] App icon file (File upload, required)
- [ ] Logo and wordmark files (File upload, required)
- [ ] Brand colours (Colour, required)
- [ ] Brand fonts (Font)
- [ ] Short and long app descriptions (Long text)
- [ ] Developer name and legal entity (Short text, required)
- [ ] Terms of use address (Link)
Questions about this checklist
Do we need a website to publish an app in the stores?
The stores ask for a privacy policy address and a support contact, and a site is the usual place for both. A one-page site with those two items is the minimum most teams ship with.
Should the site use a smart link or two separate store buttons?
Use two buttons on desktop and a single smart link in shared posts. A visitor on iPhone who lands on a Google Play button leaves, so detect the device where you can.
Can we show the app before it is approved?
Yes, with a waitlist or beta signup and screenshots from the build. Avoid store badges until the listing is live, since a dead link looks worse than a waitlist.
Related checklists
SaaS landing page
A SaaS landing page has to say who the product is for, show it working and give a price or a clear next step. Real screenshots, customer permission to use names and a pricing page that is still changing cause most of the delay.
Developer tools
A developer tool site has to get an engineer from the home page to a working install in minutes, with code that runs as written. The delays come from sample code nobody tested, benchmark claims and docs owned by another team.
Browser extension
A browser extension site has to show what the extension does in ten seconds and say plainly what it can see in the browser. Most delays come from store listing details, permission explanations and screenshots that match the current version.