Products SEO & GEO Agent Paid Ads Agent Website Agent Conversion Agent
How it works Pricing FAQ Blog Book a call

Consumer app content: what keeps users opening your app

Updated · 6 min read

Short answer Users come back to an app for timely, useful content at the right moment: a short onboarding, push notifications they opted into, in-app tips, App Store in-app events, release notes and a well-timed rating prompt. Apple and Google limit each one: marketing pushes need explicit opt-in, and rating prompts show at most a few times a year.

Want help applying this to your business? Talk it through on a free 30-minute call.

Book a call

What content keeps app users coming back?

People reopen an app when it gives them something they want at the moment they want it. For a small business app (a studio's class booking app, a restaurant's ordering app, a habit or game app from a two-person team), that content comes in six places, and Apple and Google set rules for each.

WhenContentThe rule that limits it
First openShort onboarding, tips next to the featureApple: fast, fun and optional
After a real actionAsk permission for notificationsAndroid 13+: off until the user allows; iPhone: permission needed before any notification
OngoingPush notificationsMarketing only with explicit opt-in and an in-app way to opt out
Inside the appIn-app messages and tipsYour own app; Firebase In-App Messaging is free
In the storeIn-app events, promotional text, "What's New" notesApple: up to 10 events live at once; Google Play's version is mostly for games and very large apps
After successRating promptApple: three times per 365 days; Google: a hidden quota

Email and text messages work too, but they fall under marketing law, not app store rules. See email and text marketing for a service business.

How do I onboard new app users?

Teach by doing, in as few screens as possible, and let people skip. Apple's design guidelines put it this way:

"Ideally, people can understand your app or game simply by experiencing it, but if onboarding is necessary, design a flow that's fast, fun, and optional." (Apple Human Interface Guidelines: Onboarding)

Apple also suggests a set of small tips shown next to the feature they explain, instead of one long tour, and putting off settings people don't need yet. A booking app's first screen should be the schedule, not a five-page tour.

Can I send push notifications to app users?

Yes, for things users want, and for marketing only after they say yes. Apple's App Review Guidelines (4.5.4):

"Push Notifications should not be used for promotions or direct marketing purposes unless customers have explicitly opted in to receive them via consent language displayed in your app's UI, and you provide a method in your app for a user to opt out from receiving such messages."

Apple's design guidelines add that you need an in-app settings screen where people can change that choice, and must never mark a marketing push "Time Sensitive", the level that breaks through Focus modes.

On Android, a new install on Android 13 or later starts with notifications off. Google's developer guide says the app "must wait to send notifications until after you request the new permission and the user grants that permission" (Android Developers: Notification runtime permission). It recommends asking in context, after a user action such as tapping a bell icon or placing an order, or after the third or fourth launch, and notes that users can see how many notifications your app sends each day.

What to send: a class is about to start, an order is ready, a streak is about to break, a new feature they asked for. One message with a reason beats three reminders.

What are in-app messages?

In-app messages are banners or cards shown while someone is already using the app: a tip, a new feature, an offer. They need no notification permission because the user is already there. Firebase lists Cloud Messaging (push) and In-App Messaging among its no-cost products (Firebase: Pricing), so a small team can send both without paying a messaging vendor.

How do I use the app store to bring users back?

Use the store's own content slots. On Apple's App Store:

  • In-app events. Timed events (a challenge, a premiere, a live class, new content) show as cards on your product page, in search results and in recommendations, and people can ask the App Store to notify them when an event starts. You can have up to 15 approved events in App Store Connect and 10 published at a time (Apple Developer: In-App Events). Apple says daily tasks, plain price promotions and general awareness campaigns are not good candidates.
  • Promotional text. Up to 170 characters above your description, changeable "without requiring an updated submission" (App Store Connect Help).
  • What's New. Up to 4,000 characters per version. Write what the user gets, not "bug fixes".

Google Play's matching feature, promotional content, is open to all games. For apps that aren't games, it requires millions of monthly users or tens of thousands of dollars in monthly spend in supported categories (Google Play: Premium growth tools). Most small apps on Google Play don't qualify, so they rely on release notes, notifications and in-app messages.

When should my app ask for a rating?

After the user finishes something that went well, never on first launch, and only with the store's own prompt. Apple's App Review Guidelines (5.6.1) say to use the provided prompt and "we will disallow custom review prompts." Apple's documentation adds:

"Be aware that the system displays the review prompt to a user a maximum of three times within a 365-day period." (Apple Developer: Requesting App Store reviews)

Google Play enforces its own quota and does not publish the number. Its rules say the app "shouldn't ask the user any questions before or while presenting the rating button or card," such as "Do you like the app?" (Android Developers: In-App Review API). Neither store's prompt should sit behind a "Rate us" button, because it may not appear. For a button, link to your store page instead. Asking only happy users for reviews is review gating; for the rules on other review sites, see asking for reviews.

How do I know if my app content is working?

Watch whether people come back, not how many saw a message. Firebase Analytics is free (Firebase: Pricing); use it to see how many users come back. To learn what users want, ask one short in-app question, but never just before the rating prompt. Change one thing at a time, such as the onboarding or the timing of the notification permission request, and compare users who joined before and after it.

Example

Illustrative cases. Numbers are invented.

A yoga studio with a booking app

The app asks for notification permission right after the first class is booked: "Want a reminder an hour before class?" Six in ten users say yes. Marketing messages about new workshops go only to users who also ticked a separate opt-in, with a switch in Settings to turn them off.

A two-person puzzle game

The team runs a monthly weekend tournament as an App Store in-app event, and Google Play promotional content too, since all games qualify. The rating prompt appears after a player wins their fifth level, never during play.

A local bakery's ordering app

The owner has no developer time. They update the App Store promotional text each season ("Pumpkin loaves are back through November"), write real release notes, and send a "your order is ready" push that customers asked for.

FAQ

Do I need permission to send push notifications?

On iPhone, any notification needs the user's permission first. On Android 13 and later, new installs start with notifications off until the user allows them. Marketing pushes on iPhone also need explicit opt-in in your app.

How often can my app ask for a review?

Apple shows its prompt at most three times per user in 365 days, however often your app asks. Google Play uses a quota it doesn't publish; asking more than once in about a month may show nothing.

Can a small Android app use Google Play promotional content?

Usually not. It is open to all games, but apps that aren't games need large user or spend numbers and a supported category.

Is a blog useful for an app?

Yes, if it answers questions people search before they download. See whether a small business needs a blog.

Different for you?

Keep learning

NextSaaS content marketing: content that turns readers into trialsSaaS content marketing for a small software company: which pages to publish first, how to write comparisons and case studies legally, and how to count trials.

Ask us one question

One line is enough. We reply by email.

Sources

  1. Apple: App Review Guidelines (4.5.4 Push Notifications, 5.6.1 App Store Reviews)
  2. Apple Human Interface Guidelines: Managing notifications
  3. Apple Human Interface Guidelines: Onboarding
  4. Apple Human Interface Guidelines: Ratings and reviews
  5. Apple Developer: Requesting App Store reviews
  6. Apple Developer: In-App Events
  7. App Store Connect Help: Platform version information
  8. Android Developers: Notification runtime permission
  9. Android Developers: Google Play In-App Review API
  10. Google Play: Premium growth tools eligibility
  11. Firebase: Pricing