Apple Enforces Age Verification Gates While Google Doubles Down on Developer Identity Checks

Age Verification Becomes a Conversion Bottleneck

Apple activated mandatory age verification enforcement in Australia, Brazil, and Singapore on February 24, 2026. Users in these markets cannot download apps rated 18+ until their adult status has been confirmed through Apple's systems. The change builds on the January 31, 2026 deadline that required all apps to complete Apple's revised age rating questionnaire, which introduced 13+, 16+, and 18+ tiers alongside the existing 4+ and 9+ ratings.

The shift introduces measurable friction. Apps carrying an 18+ rating now face an additional pre-install gate that intercepts users before they reach the product page action button. Conversion rates in these three markets will compress. Studios distributing mature-rated content should expect a near-term dip in organic installs from these geos, particularly if the app relies on impulse discovery rather than intent-driven search.

The enforcement mechanism does not differentiate between genuine age-restricted content and apps that accidentally triggered the 18+ threshold through careless responses in the Age Rating questionnaire in wiki:app-store-connect. Review your app's rating carefully. If the rating is higher than the content warrants, resubmit the questionnaire before the policy expands to additional markets.

Medical Device Disclosure Now Required on App Store Product Pages

Apple is requiring apps distributed in the European Economic Area, United Kingdom, and United States to declare their regulated medical device status starting immediately for new submissions. Existing apps in scope must comply by early 2027 or lose the ability to submit updates.

The requirement applies if the app meets either of two criteria:

• Its primary or secondary category is Health & Fitness or Medical
• It is marked as containing frequent references to Medical or Treatment Information in the Age Rating questionnaire

Regulated medical device apps function independently or as part of a system for diagnosis, prevention, monitoring, or treatment of diseases and physiological conditions. These apps may require registration or authorization from bodies like the U.S. Food and Drug Administration. The App Store will now display the device status directly on the product page to increase customer transparency.

If your app is not a regulated medical device, you must explicitly select "No" in App Store Connect. Failure to declare a status by early 2027 will block app updates. The policy does not create new regulatory obligations, but it does surface existing compliance gaps in public-facing store listings. Apps that have avoided FDA registration despite meeting functional criteria for a medical device will now face immediate visibility of that noncompliance.

This change intersects with wiki:app-store-policy enforcement trends that increasingly require substantiation of health claims. Studios that ship meditation, cycle tracking, symptom checkers, or diagnostics-adjacent features should audit whether their app crosses the regulatory threshold and document the decision in writing.

Google Blocked 1.75 Million Apps in 2025 and Extends Developer Verification to All Channels

Google's 2025 safety report shows the platform blocked 1.75 million apps from Google Play, up significantly from prior years. The company also prevented 160 million spam ratings and reviews and stopped review-bombing campaigns that would have caused an average 0.5-star rating drop across targeted apps.

AI now accelerates the review process. Google's models detect policy violations faster and surface malicious patterns earlier in the submission pipeline. The tightening extends beyond the Play Store itself. Google detected 27 million malicious apps via sideloading channels in 2025, double the 13 million flagged in 2024. The spike in off-store threats is driving Google's next enforcement layer: mandatory developer verification.

Starting March 2026, all developers must complete identity verification to distribute apps on certified Android devices, whether through Google Play, alternative stores, or sideloading. The process began in early access in October 2025 and is now opening to the full developer base. Verification requires government-issued ID and corporate registration documents for business accounts.

The policy removes anonymity from Android distribution. Developers who previously operated behind shell entities or used disposable accounts to test the boundaries of wiki:app-store-policy compliance will no longer have that option. The change reduces the volume of fraudulent, clone, and spammy apps entering the ecosystem, which improves the signal-to-noise ratio for ranking signals like wiki:star-rating, engagement, and keyword relevance.

Studios that integrate Play Games Services, run consistent LiveOps, and qualify for Google's Level Up program will see compounding benefits as the competitive landscape cleans up. The new "You" tab in Google Play surfaces gamer profiles, cross-game stats, daily play streaks, progress tracking, Leagues, and the Gemini-powered Sidekick overlay. Apps that do not activate these features will face a widening visibility gap.

AI Fraud Techniques Cost Users $893 Million

Cybercrime losses in the United States reached $21 billion in the prior year, driven primarily by investment and cryptocurrency scams. AI-enabled fraud techniques accounted for $893 million of that total. Voice cloning, deepfake videos, and forged documents are now standard tools in social engineering attacks.

The shift has implications for user trust and onboarding friction. Apps that request sensitive permissions, handle financial transactions, or facilitate peer-to-peer communication will face heightened scrutiny from both platform reviewers and users who have been burned by fraud. Expect Apple and Google to tighten identity verification requirements for apps in financial services, dating, and marketplace categories.

Studios should audit their onboarding flows for signals that reduce perceived risk. Transparent data safety privacy disclosures, clear contact information, and verifiable business credentials are no longer optional. Users are more likely to abandon apps that feel opaque or that rush through permissions requests without context.

What to Do Now

• Check your app's age rating in App Store Connect. If you carry an 18+ rating due to overcautious responses in the Age Rating questionnaire, resubmit with accurate answers. Conversion rate compression in Australia, Brazil, and Singapore is already live.
• Declare medical device status by early 2027 if your app falls into Health & Fitness, Medical, or triggers the Medical or Treatment Information flag. Delaying will block updates.
• Complete Google Play developer verification before March 2026. The process requires government-issued ID and takes time. Do not wait until you need to push an urgent update.
• Integrate Play Games Services, run LiveOps, and activate the Level Up program if you publish games on Android. The "You" tab surfaces player activity and progress. Apps that do not participate will lose visibility as Google shifts discovery toward live content.
• Audit user trust signals in your onboarding flow. AI fraud is reshaping user expectations. Apps that feel anonymous or that skip context when requesting permissions will see higher drop-off rates.

Compliance is no longer a backlog item. It is a conversion rate and visibility multiplier. The platforms are tightening enforcement, and the apps that adapt early will capture the installs that fall away from competitors who delay.