TL;DR
Honest metadata is a trust signal and a review pass. Claim only what the app does, name the limits plainly, and match screenshots to the real build for better reviews.
Your listing is where trust is won or lost, and where store review starts. Apple and Google both compare what you claim against what the app actually does before a human even tests it. Overstate the features and you get a rejection, or worse, one-star reviews from users who feel misled.
Claim what is true
- Describe features the app actually has, not ones on your roadmap.
- Name the limits plainly, like offline-only or one platform for now.
- Match screenshots to the real build, since reviewers compare them.
- Be clear about what is free versus behind the subscription.
- When unsure, undersell a little so users are pleasantly surprised.
The description sets the expectation, and the app has to meet it. Say exactly what it does: "tracks up to five habits offline" beats a vague "the ultimate habit app." Specific honesty tells the browser you are straight with them, and it keeps your early reviews strong.
Match the listing to the build
Back up your description with screenshots that match the real app. A shot of a feature you have not built looks great until a reviewer opens the app and it is missing, which triggers a rejection under Apple's rules. Show the app you actually shipped, not the one you imagine.
Honest metadata is also good review discipline. If the app is a simple utility, describe it as a simple utility rather than dressing it up as an all-in-one platform. Matching claims to reality keeps your listing believable, your reviews positive, and your review passes clean.
Common questions
How careful do I need to be with feature claims?
Very. Claim only what the app actually does. Reviewers compare your listing against the real build before approving it, and users who feel misled leave one-star reviews. Underpromising protects both your review pass and your reputation.
How detailed should I be about limits?
Name them plainly - offline only, one platform for now, tracks up to five items. Specific honesty beats a vague superlative and builds trust with the browser, while also setting expectations that keep reviews positive.
Do screenshots need to match the real app?
Yes. Screenshots must reflect the actual build. A shot of a feature you have not shipped gets caught when a reviewer opens the app, which triggers a rejection under Apple's guidelines. Show what you actually built.
Does honesty affect how I price the app?
It should. Describe and price the app for what it is. A simple utility described honestly and priced fairly keeps reviews strong, while overselling a basic app to justify a high price backfires in feedback.
What happens if I overstate what the app does?
You risk a rejection when reviewers compare the listing to the build, plus one-star reviews from users who feel misled. Overstating features to win downloads almost always backfires once people actually open the app.
Is it bad to call my app the best or ultimate?
It reads as inflated and reviewers dislike unbacked superlatives. Describe what the app does and who it is for instead. Specific, honest claims convert better and keep you clear of review flags for misleading metadata.
Keep going
Get your listing claims checked for $9/month
Get the other 14 in the app pricing stack, plus the full App Store Launch Club community - $9/mo, cancel anytime.
Join the Club