Urgent Need for a System-Level Age Range API on Android (Inspired by Apple's Innovation)

[Diljeet Kumawat]

Dear Google Mobile Ads SDK Team and fellow Android Developers,

I'm writing today to highlight a significant challenge we, as app developers, face in delivering truly age-appropriate experiences and advertising, particularly in light of evolving privacy regulations like COPPA and GDPR. I believe a system-level Age Range API on Android, similar to what Apple has recently announced, would be a transformative solution.

Currently, if our app has a mixed audience (e.g., rated 4+ but intended for both children and older teens/adults, like many casual games or utility apps), the burden falls entirely on the developer to implement and maintain an in-app age gate. While we strive for neutrality and compliance, this approach has inherent limitations:

1. User Honesty: Users, especially children eager to access certain features, may not accurately provide their age, undermining our efforts to serve appropriate content and ads.

2. Developer Burden: Creating and maintaining robust, legally compliant age gates is complex. It requires careful UI design, data persistence, and continuous monitoring of changing regulations, diverting resources from core app development.

3. Fragmented Experience: Every app requiring age-gating forces the user through a similar, often repetitive, process.

Apple's recent introduction of a Declared Age Range API for iOS 26 (and potentially earlier iOS versions via updates) addresses these challenges head-on. This API empowers developers to request an age range (e.g., 13-15, 16-18, 18+) from the system in a privacy-preserving way, with parental consent mechanisms handled at the OS level. This single, standardized approach allows developers to:

• Serve age-appropriate ads (non-personalized for younger users) reliably.

• Filter content or disable features (like social sharing) for specific age groups.

• Significantly simplify their compliance efforts by offloading a complex, sensitive task to the platform.

We desperately need a similar capability on Android. Imagine the impact:

• Seamless User Experience: Users provide their age range once to the system, and apps can then retrieve this information (with consent), leading to a smoother, less intrusive experience.

• Enhanced Child Safety: Developers could more effectively ensure younger users are protected from inappropriate ads and content, not just based on their app's general rating, but on the user's declared age range.

• Fairer Monetization: For mixed-audience apps, it would create a clearer path to serve personalized ads to adult users while strictly adhering to non-personalized ad policies for minors, without the guesswork.

• Developer Empowerment: Freeing up countless developer hours spent on age-gating logic, allowing us to focus on creating richer, more engaging app experiences.

Google has always been a leader in developer tools and responsible advertising. Providing an Android Age Range API would be a monumental step forward for privacy, developer productivity, and creating a safer digital environment for all users.

Please consider prioritizing the development of such an API. It would demonstrate a deep understanding of the challenges developers face daily and reinforce Android's commitment to building a secure and developer-friendly ecosystem.

Thank you for your time and consideration.

Yours' Sincerely,

Diljeet Kumawat - A fellow Android Developer since 2012

[Mobile Ads SDK Forum Advisor]

Hi,

Thank you for contacting the Mobile Ads SDK Support team.

That's a great point. Thanks for the suggestion to integrate an Age Range API for Android, similar to the one which was introduced in iOS 26.I will inform the wider team about this and will get back to you once I receive any updates on it.

Kindly note that our support channel can only best assist you with regards to Google Mobile Ads SDK implementation and technical issues.

Thanks,
 

Mobile Ads SDK Team

Feedback
How was our support today?

               
[2025-07-28 12:59:56Z GMT] This message is in relation to case "ref:!00D1U01174p.!500Ht01swvO4:ref" (ADR-00320773)