Project ideas from Hacker News discussions.

Google will expand age checks on Android worldwide till the end of the year

Original Article

Hacker News Discussion

📝 Discussion Summary (Click to expand)

Top 5 themes in the discussion

#	Theme	Representative quote
1	Invasive age‑verification feels like state‑level surveillance	“This smells like Soviet Union. The next step will be a requirement to confirm your identity …” – cynicalsecurity
2	Google’s Play‑Age‑Signals API reinforces lock‑in	“To request a user’s age range and sharing status, you call the Play Age Signals API (beta) from your app at runtime…” – dmantis
3	Effective parental controls are still lacking; responsibility lies with parents	“I wish Motorola all the best with their GrapheneOS partnership…” – dmantis (referencing parental‑control expectations)
4	High‑cost devices & market pressure exacerbate the debate	“The rumored Motorola devices are even more expensive… At least with pixels you can get the a series for as little as $400 on sale.” – superloika
5	Privacy‑preserving technical fixes (e.g., ZKPs, UUIDs) are proposed	“With ZKP, if you make a business out of reselling tokens you get with your own identity, eventually they will see that you use orders of magnitude more tokens than normal people.” – ininy

All quotations are taken verbatim from the HN thread (HTML entities have been fixed).

🚀 Project Ideas

Privacy‑First Age Attestation SDK

Summary

Provides cryptographic age proof without sharing personal identifiers or granting third‑party access to user data.
Enables apps to request “over‑18” status while preserving privacy.
Users keep all verification data on‑device.

Details

Key	Value
Target Audience	App developers, privacy‑conscious users, OS vendors
Core Feature	On‑device zero‑knowledge age attestation using self‑signed attestation certificates
Tech Stack	Rust + WebAssembly, Android NDK, iOS Swift, Jewel‑Crypto, TUF for key management
Difficulty	Medium
Monetization	Revenue‑ready: Subscription tier for enterprise API usage + optional premium “custom attestation” service

Notes

HN users repeatedly lament that “Google’s age‑signals API forces ID uploads” – this solves that by keeping verification local.
Aligns with calls for “open, decentralized age verification” and would relieve concerns about surveillance creep.

On‑Device Age Metadata Layer for Android

Summary

Adds a native OS‑level age range field that apps can read via a privacy‑preserving API.
Parents set the age once during device setup; the OS stores it securely and never transmits it.
Apps can tailor content based on the immutable age range without needing external verification.

Details

Key	Value
Target Audience	Android OEMs, app developers, privacy advocates
Core Feature	System‑level “AgeRange” property exposed through a read‑only binder interface
Tech Stack	AOSP (Java/Kotlin), Android Framework, SELinux policies, Kotlin Coroutines
Difficulty	Low
Monetization	Hobby

Notes

Directly addresses concerns that “age verification should be configured by parents, not forced by Play Services.”
Fits with discussions about “device‑admin controls” and would likely be praised by privacy‑focused HN commenters.

Self‑Sovereign Age Credentials Platform

Summary

A decentralized service that issues verifiable age credentials (e.g., “over‑18”) using DID‑based zero‑knowledge proofs.
Users hold the credential in a personal wallet; services verify it without seeing the underlying identity.
Credential can be revoked or refreshed automatically (e.g., birthday transition).

Details

Key	Value
Target Audience	Individuals, developers of age‑restricted services, regulators
Core Feature	Issuance and verification of privacy‑preserving age credentials via W3C VC / DID
Tech Stack	Node.js (TypeScript), Ceramic DID, Polygon ID, React Native wallet UI
Difficulty	High
Monetization	Revenue‑ready: Tiered verification fees for high‑volume enterprises + optional compliance consulting

Notes

Mirrors HN’s desire for “government‑issued but privacy‑preserving” verification and avoids reliance on Google/Apple.
Offers a concrete alternative to “upload passport to sketchy third party” complaints.

Age‑Tagged App Marketplace

Summary

A curated app store where each app publishes an official age rating tag (e.g., “13+”, “18+”).
Users can filter or block apps based on their personal age settings without needing per‑app verification flows.
Developers set a single age tag at submission; the marketplace enforces it client‑side.

Details

Key	Value
Target Audience	End‑users, app developers, platform maintainers
Core Feature	Automatic age‑rating enforcement through a browsable catalog with user‑configurable filters
Tech Stack	Django + PostgreSQL, React front‑end, GraphQL API, Docker Swarm
Difficulty	Medium
Monetization	Hobby (open‑source) with optional donation‑based support for moderation

Notes

Directly answers “need for age‑rated apps without invasive verification” discussed in HN threads.
Provides a practical utility that could replace current Play Store age‑range hacks.

Open‑Source Age Verification Patcher for Android Apps

Summary

A tool that patches APKs to replace the default age‑verification call with a configurable mock response (e.g., “over‑18”).
Users run the patcher once; the modified APK no longer forces ID uploads and can use a user‑provided age setting.
Maintains original app functionality while removing intrusive verification.

Details

Key	Value
Target Audience	Power users, modders, privacy‑focused Android enthusiasts
Core Feature	Automated byte‑code injection to intercept `ageRangeSource` and supply a static value
Tech Stack	Java (JEB Decompiler), Python script wrapper, apktool, Gradle signing
Difficulty	Medium
Monetization	Hobby

Notes

Appeals to HN’s frustration with “developer‑forced age checks” and “privacy‑invasive APIs.”
Could spark discussion about user rights to modify client behavior without legal risk.

Government‑Backed Zero‑Knowledge Age Token Service

Summary

A public service that issues cryptographically signed age tokens using a national digital ID infrastructure.
Tokens are short‑lived, can be presented to any service for age validation without revealing identity.
Tokens can be verified offline, ensuring no persistent tracking.

Details

Key	Value
Target Audience	Citizens, regulators, service providers requiring age gates
Core Feature	Zero‑knowledge age attestation tokens issued by state‑trusted CA, verifiable via open‑source client lib
Tech Stack	Go (Hyperledger Besu), BLS signatures, WebAssembly front‑end, Rust verification library
Difficulty	High
Monetization	Revenue‑ready: Minimal processing fee per token batch + API usage tier

Notes

Directly addresses “need for privacy‑preserving government‑issued age proof” voiced in HN debates.
Offers a concrete implementation path that could be cited as a model for future standards.