App Store Featured Placements: How Teams Get Picked

App Store featured placements look like luck from the outside. Apps appear on the Today tab, in Google Play's editorial collections, and at the top of category browse — and nobody seems to know how they got there. The truth is most featured placements are not luck. They are the result of a structured pitch process, a product that fits an editorial theme, and submissions sent before specific deadlines. Teams that understand the process pitch successfully; teams that don't get picked at random or never.

This article explains how Apple's App Store editorial team and Google Play's editorial team actually select featured apps in 2026, the criteria they apply, the pitch process for each store, and the realistic timelines to expect.

Why featured placements matter

A single Today tab feature on the App Store can produce 100,000 to 1 million additional installs over 1 to 3 days, depending on category and placement. A Google Play "Editor's Choice" inclusion produces meaningful long-tail discoverability beyond the initial spike. The value is real: featured placements are some of the highest-quality install traffic available because users who tap from editorial trust the curation.

The cost: most teams never apply, or apply once with a thin pitch, or pitch the wrong feature to the wrong moment.

How Apple selects

The App Store editorial team in 2026 operates with a published submission process and a hidden editorial calendar. The visible mechanism is the App Store Connect "Featuring nomination" form. The hidden mechanism is the calendar of editorial themes the team is producing for the next 8 to 12 weeks.

The criteria Apple uses

Apple does not publish their full rubric, but consistent patterns from successful features:

Visual craft. A design-aware app with a distinctive UI is the single highest-weighted criterion.
Story. Apps with a strong human story (the developer's background, the problem the app solves, the community it built) are favored.
Topical relevance. Apps that align with an upcoming Apple editorial theme (back-to-school, World Mental Health Day, a hardware launch) have a much higher chance.
Technical adoption. Apps that use new Apple frameworks (the latest SwiftUI, WidgetKit, App Intents, Live Activities) get bonus attention.
Quality bar. App must be free of obvious bugs, performant, and meet accessibility standards.

The Apple pitch process

The flow:

Submit through App Store Connect → Featuring nomination form. Available 4 to 8 weeks before each major release.
Submit during the named windows. Apple announces opens for specific themes (e.g., "Featuring our favorite design apps in September") — these have hard deadlines.
Provide assets in the form. App icon, key screenshots, a short developer story, a written pitch (3 to 5 paragraphs).
Mention applicable Apple frameworks. If you adopted a new framework this year, name it explicitly.
Wait. Most successful pitches do not get a response until the feature appears.

Pitches submitted outside named windows often go unread.

How Google Play selects

Google's editorial process is similar in shape but different in mechanics. The Play Console has an "App content" section that includes editorial submission forms, and Google runs themed "collections" that the team builds toward.

The criteria Google uses

Google's published guidance plus consistent feature patterns suggest:

Quality benchmarks. Crash-free rate, ANR rate, and uninstall rate must be above category benchmarks.
Visual quality. Strong screenshot and feature graphic design.
Reviews and rating. Generally 4.4+ rating with healthy review volume.
Active maintenance. App is updated regularly; not abandoned.
Localization. Apps serving multiple major languages are favored for global features.
Material Design adoption. Apps using current Material guidelines get a small bonus.

The Google pitch process

Submit through Play Console → App content → Featuring opt-in.
Maintain the metadata Google checks. Feature graphic, promo video, descriptive long description.
Submit detailed app information. What's new, why this matters now, target audience.
Stay above quality benchmarks. A pre-feature drop in crash-free rate kills a pending feature.
Track your "Editor's Choice" eligibility. Google surfaces eligibility status in the console.

Unlike Apple, Google sometimes responds proactively to invite apps to apply for specific features.

What gets you picked: 5 patterns

The patterns common to apps that successfully land features:

A distinctive visual identity. Both stores feature design-led apps disproportionately.
Topical relevance to the editorial calendar. Aligning with a published theme is the single biggest lift.
A clean story. "We built this because..." with a real human reason. Editorial teams write the captions; a clear story makes the caption easy.
Recent meaningful release. A major update is a natural feature trigger.
Technical adoption of new platform frameworks. Editorial teams care about the platform's own roadmap.

What does not get you picked

The mistakes that submit a weak pitch:

Pitching a generic feature ("we have AI now") with no specific story
Submitting a pitch but having an outdated screenshot set or store listing
Crash-free rate or app quality below category benchmarks
Pitching the same week as your launch (editorial calendars are set 8+ weeks ahead)
No video or weak feature graphic on Google Play
A pitch that reads like a press release ("the leading platform for...")

Timeline expectations

For a quality app pitching for the first time:

First Apple Today tab feature: 6 to 18 months from first pitch.
First Google Editor's Choice: 4 to 12 months from first pitch.
Category browse top placements: Driven by ASO and conversion, not editorial — see ASO content for that.
Repeat features after the first: Faster if the relationship is established.

Patience matters. Many apps that became featured staples were rejected on their first 2 to 3 pitches.

The 5-step process to maximize odds

The flow Semnexus recommends:

Get the app to feature-quality on craft and quality benchmarks first. Pitching before you are at this bar wastes your shot.
Identify the next 2 to 3 editorial themes you fit. Read both stores' editorial calendars and trade press.
Tailor a pitch per theme. Don't send the same pitch for every opportunity.
Submit through the official forms only. Cold-emailing editorial teams rarely works in 2026.
Track every submission and follow up at intervals. A pitched-and-forgotten app rarely gets picked.

Frequently asked questions

Can a paid relationship guarantee a feature? No. Both Apple and Google explicitly reject paid editorial placement. App Store ads (Apple Search Ads) are separate from editorial.

Does having a Apple Design Award or similar nomination help? Yes, materially. Recognition signals quality in a way the editorial teams trust. Apply for Apple Design Awards, Google's #Androidify partnerships, and adjacent recognition programs.

Are smaller markets (non-English locales) easier to get featured in? Generally yes. Country-specific editorial slots are less competitive than US/UK. Apps that localize well can land features in smaller markets first.

What about indie developer programs (App Store Small Business Program, Indie Corner)? These have separate submission flows. Indie-focused features exist on both stores and are worth pursuing if you qualify.

How do I keep the relationship after the first feature? Stay in touch through subsequent updates. Send a short note when you ship a notable release. Don't pitch the same theme repeatedly; come with new angles.

If you are preparing a featured placement pitch or running an ASO program that should support editorial visibility, the Semnexus mobile app marketing team handles pitch writing, asset prep, and submission strategy as part of ASO engagements. The app development team handles the cases where pre-feature quality work (crash-free rate, framework adoption) requires product changes.