App Store Editorial Isn't Luck: Two Stores, Two Doors
App Store Editorial and Google Play featuring are two different doors: a nomination versus a promotional event. Here is what to fix before you submit.
Someone in the weekly meeting asks whether you can get on the App Store Today tab. Within a minute, three theories are on the table: you have to pay Apple, you need a connection, or your rating has to hit some magic number. None of them are true. There is no public place to buy a featuring slot, and no relationship that substitutes for one. But it is not a lottery either. Both stores give you a door. The doors just do not look alike.
The short version
App Store editorial comes down to two things: what you write in the nomination you file in App Store Connect, and whether your product page holds up when an editor opens it. Google Play has no nomination step at all. It asks you to build a concrete promotional event first, then request featuring inside the flow that creates that event. One platform trades a document for attention. The other trades ready-to-run assets for exposure. Decide which one you are doing before you assign the work.
Apple's door: a written nomination
App Store Connect has a Featuring Nominations section. You create a nomination and describe what you are pushing: a launch, a significant update, or new in-app content such as a seasonal campaign or an event. Access is role-gated. The account holder, admins, app managers and marketing roles can submit. This is why engineers often cannot find the menu — the role is missing, not the feature.
You can file nominations one at a time or import a batch via CSV. The difference matters: a single nomination saves as a draft first, while a CSV import submits immediately and can only be edited afterwards. The dashboard splits into Drafts, Submitted and Archived — your only sane record of what you asked for.
Google's door: an event first, a placement second
Play runs it the other way around. Featuring is not a standalone application; it rides on promotional content: Grow users, Store presence, Promotional content. You create an event, define its dates, countries, copy and assets, and request featuring inside that same flow.
Two constraints are worth memorising. An event cannot be submitted earlier than 60 days before its start date, and approval can take up to four days, so Google recommends submitting at least four days ahead. Miss that and your event goes live while review is still chewing on it. The second is eligibility: promotional content is open to all games, while apps need to qualify for premium growth tools. Check the current official guidance before you ship, because this is exactly the kind of rule that moves.
The two teams look for different things
Apple does not publish a checklist, but it does publish what its editors weigh: whether the experience is cohesive, UI design and usability, use of new platform capabilities, a fresh angle in a familiar category, accessibility, localisation quality, and the product page itself — screenshots, previews, description, ratings and reviews. Read that list twice and you notice almost all of it is about the product. Only the last item is about marketing material.
Google's framing is different in kind: core value, user experience, technical quality, privacy and security, plus stability signals such as Android vitals and whether your listing assets meet the bar. It cares whether the thing runs well on real devices, not whether the team has a good story.
That difference should reshape your prep work. For Apple, spend the time on screenshots, preview video and narrative. For Google, go fix crash rates, ANR, device compatibility and asset compliance first.
What actually goes into a nomination
The most common waste I see is a nomination written like a company profile: founding year, headcount, tech stack. An editor reads dozens of these a day. None of that helps them decide whether this becomes a story.
Write three things instead. What changed, described as a specific behaviour rather than "a fully upgraded experience". Why it matters to users, meaning who now skips a step in which situation. When you want it to appear, tied to a release, a holiday, or a local market moment. If the update has a visible interface change, attach something they can look at. If you did real accessibility or localisation work, say so — Apple lists both as considerations.
Google has no nomination to write, but the same information lands in event copy: what the event is about, what a user sees after tapping, whether the assets match the build.
Fix the listing before you submit
Both stores work on the same premise: a placement uses the listing you already shipped, not a parallel set of assets. So the page comes first.
On the App Store side, that means title, subtitle, promotional text, the first two screenshots, the preview video and the opening paragraph of your description. Promotional text is the one field you can change without resubmitting, and it is the field most teams leave empty for months.
On the Play side: app name, short description, full description, feature graphic, screenshots and video, plus the event assets. One rule trips people up — no ranking claims, prices or "number one" badges in icons or screenshots. That is a metadata violation, not a clever creative.
Then check a switch. Play Console has an external marketing setting under store settings. Turning it off restricts promotion of your app across Google-owned properties. Teams disable it to stay quiet during launch, then wonder why their featuring requests never seem to move.
Timing is where most submissions die
Apple's own wording: give the team a minimum of two weeks notice, and for wider consideration submit up to three months in advance. The three months is the part people skip. Editorial themes and collections are planned ahead. A nomination filed late is competing for a slot that was decided weeks ago.
Google's 60-day ceiling and four-day review feel more forgiving, but events expire. When the event ends, the placement ends, which makes it a fit for a launch or a sale moment and a poor substitute for ongoing exposure.
What both stores share: a nomination has to hang on something happening. No release, no event, no visible change, and the submission reads as a request for attention with nothing behind it.
When not to submit
First, right after launch, with no retention or rating data. Ratings and reviews are an explicit consideration at Apple, and Google folds user feedback into quality. Submitting now shows a product with no evidence.
Second, when the assets and the build disagree. A screenshot showing a screen that does not exist is a policy problem on Play and a credibility problem at Apple, and credibility does not come back cheaply.
Third, when the listing is not ready. If the first two screenshots cannot explain what the app does, and the description opens with adjectives, a placement would land traffic on a page that cannot convert it.
Fourth, when you treat featuring as a substitute for paid acquisition. Placements are spikes; they do not replace steady keyword and campaign work, and expecting one to fix growth usually ends in disappointment.
How to judge whether it worked
Do not use "did we get it" as the only measure — you do not control that. What you control is the process: how many nominations you file, how consistently, how finished the listing is each time.
Once traffic arrives, watch three things: the shape of the organic download curve, whether conversion drops against your baseline because the audience changed, and whether retention returns to normal afterwards. The third gets ignored and it is the clearest signal of whether the exposure brought the right people.
If you want a second pair of eyes
If you are still unsure which door applies to you, how to write the nomination, or why your last submission produced silence, the rest of the answer sits in your release calendar and your listing. We (Youou) build two-store listing and submission systems, and often turn "we ship versions but have nothing to say" into a schedule someone can run. Bring your release plan.
What to do next
1. Check the role on your App Store Connect account: account holder, admin, app manager or marketing. Without one of them, the nominations menu never appears. 2. Open Promotional content in Play Console and confirm whether your app is eligible and which upcoming moment you could attach an event to — check the current official guidance before you ship. 3. Audit the first two screens of your listing as if they were page one of a proposal. Can a stranger tell what problem the app solves within seconds? 4. Build one quarterly table with releases, campaigns and submission dates on the same line. Give nominations at least two weeks, and push earlier when you want wider consideration.
Want your app to rank for the keywords that matter?
Get a Quote