How to Get Featured by Apple and Google (2026)

A feature placement from Apple App Store editorial or Google Play editorial is one of the biggest single-day install events you can have as an indie dev. Lifts of 50-500% in installs are common for feature placements, plus residual organic ranking benefit.

But "submit yourself for feature" is not really a thing. Editorial teams find apps in specific ways. This is the realistic path.

What "featured" actually means

Apple App Store

Multiple feature surfaces:

• Today tab story — full-screen editorial story.
• Apps tab "We Love" / "App of the Day" — banner placement.
• Games tab equivalent for games.
• Editorial collections — themed groupings ("Our Favorite Habit Trackers").
• Featured in category — within a specific category.

Plus auto-curated:

• New apps we love.
• Trending.
• Apps for [X event/season].

Google Play

• Editor's Choice badge.
• Featured collections on the Apps / Games tab.
• Trending Now.
• Country-specific editorial.

Both have multiple tiers — being in "Featured in Productivity" is meaningful but smaller than being App of the Day.

What editorial teams look for

Common patterns across feature decisions (based on what gets featured + Apple/Google's published criteria):

1. Distinctive product

Editorial features apps that are clearly different from the top 10 in their category. A "another todo app" doesn't get featured. A "todo app for ADHD" might.

2. Quality design

• Native platform conventions (Human Interface / Material).
• Polish — animations, transitions, micro-interactions.
• No bugs in editorial review.
• Latest platform features used (widgets, Live Activities, etc.).

3. Editorial story

Editorial teams need a story to tell. "An indie dev who spent 3 years building a meditation app for nurses" is a story. "App #4 from a portfolio studio" usually isn't.

4. Topical relevance

Apple and Google plan editorial around seasons, events, and themes. Pitches that align with what's coming up have higher hit rate.

• Mental Health Awareness Month: meditation, journaling.
• Pride Month: LGBTQ+ apps.
• Back-to-school: education.
• Earth Day: sustainability.

5. Platform feature adoption

Apps that use new Apple/Google features prominently get editorial preference. New OS releases come with editorial pushes for apps that exemplify new APIs.

• Apple: Live Activities, Vision Pro, AI integrations.
• Google: new Material You design, new Android features.

6. Quality reviews

Editorial won't feature apps with ratings below ~4.5 stars. The bar is real.

How to actually get featured

Path 1: Pitch directly

For Apple, you can:

• Pitch via App Store Connect → "Suggest your app for featuring."
• Email editorial via your developer support contact.
• Use partnership/marketing contacts if you have them.

For Google:

• Submit via Play Console → "Nominate for Editorial."
• Same pitch process via support.

The pitch itself:

• Lead with the story. Why is your app different? Why does it exist?
• Highlight feature use (Live Activities, new APIs).
• Show traction (downloads, reviews, growth).
• Time it to relevant editorial cycles (90 days before a season).
• Include a video / GIF demonstrating the app.

Path 2: Get found

Most features come from editors who discover apps via:

• Top charts. Climbing the charts gets editorial attention.
• Curator newsletters and press. The Verge, TechCrunch, Indie Hackers — editorial teams read these.
• Twitter / X. Apple and Google design teams are active there.
• Designer / dev community awards (Apple Design Awards).

You can't "make" yourself found, but you can:

• Get reviews from indie newsletters / publications.
• Submit to Apple Design Awards (annual, big deal).
• Be active in mobile design / dev communities.

Path 3: Use new platform features prominently

When Apple/Google announces a new feature at WWDC or Google I/O, they're explicitly looking for "lighthouse apps" using it well. If you ship a polished implementation in the first weeks, editorial often features you.

Recent examples:

• Apps using Apple Vision Pro got heavy editorial early.
• Apps using Live Activities at iOS 16 launch got prominent placement.
• Google Play frequently features Material You / Android adaptive apps.

Action: at WWDC / Google I/O, identify 1-2 features your app could meaningfully use. Ship by the OS launch.

Path 4: Build editorial relationships

For sustained editorial relationships (you get featured multiple times over years), build personal relationships:

• Attend Apple developer events (annual labs, design awards).
• Attend Google I/O / Android Dev Summit.
• Network with editorial through agencies and partner managers.
• Maintain a partner manager relationship if you qualify (some Apple categories have account managers).

This is a long-term play. Years, not months.

What kills your chances

• Generic apps. Editorial won't feature your todo app #50.
• Poor reviews. Below 4.5 stars = unlikely.
• Marketing-heavy pitch. "We're the #1 productivity app" — editors filter this immediately.
• No editorial story. Just numbers without narrative.
• Misaligned timing. Pitching for "summer" in November isn't relevant.
• Pitching every release. Save it for genuine milestones.

What to do after getting featured

Make the most of it:

Immediately

• Have onboarding ready for a 5-10× traffic spike.
• Check server / backend capacity for the spike.
• Have a paid acquisition test ready to scale alongside the organic lift (campaigns should be approved and budgeted).
• Monitor crashes — feature-driven users are less tolerant.

Week of feature

• Track the install spike carefully.
• Track retention of feature-acquired users. Often lower D1 retention than organic.
• Update screenshots / video if you can — feature visitors are higher-intent and convert better with polished assets.

Months after feature

• Capitalize on the lift with paid acquisition while organic ranking is up.
• Pitch follow-up stories to media — features can compound press attention.
• Refresh listings with the credibility boost.

Featured doesn't guarantee long-term success

Many featured apps see a temporary install spike then return to baseline. The feature itself rarely changes retention or monetization mechanics.

What converts a feature into compounding growth:

• Product is genuinely strong (feature-acquired users retain).
• Organic ranking lift sustains after the feature placement ends.
• You convert the spike into reviews (which compound).

Common mistakes

• Pitching cold without an editorial story. Won't get read.
• Pitching during launch week. Editors are buried then.
• Pitching every release. Save it for real milestones.
• Skipping the polish. Editorial features quality.
• Ignoring platform features. Easy editorial pitch path.
• Not capitalizing on the spike. Feature week is a window — use it.

Run an audit before pitching

Before you pitch, your listing must be polished. Run a free ASO audit — editorial teams check the same dimensions (screenshots, icon, description quality, ratings).

Related reading

• The Indie ASO Audit Checklist 2026
• App Store Conversion Rate Optimization
• App Icon Design for ASO 2026
• App Store Connect AB Testing Guide 2026
• Product Hunt App Launch Strategy 2026
• The Complete ASO Guide for Indie Developers

Try the tools

• Free ASO audit
• Listing Analyzer
• Screenshot Lab