Platform Transparency and Regulatory Disclosure Become Mandatory
Apple now requires all health and medical apps distributed in the European Economic Area, United Kingdom, and United States to declare their regulated medical device status directly on the App Store product page. Apps whose primary or secondary category is Health & Fitness or Medical — or that are marked as containing frequent references to medical or treatment information in the age rating questionnaire — must provide this status in App Store Connect, along with relevant regulatory information such as contact details and safety disclosures.
New apps meeting these criteria must declare their status immediately to distribute in these regions. Existing apps have until early 2027 to comply. After that deadline, developers who have not declared their status will be blocked from submitting updates. Apps that are not regulated medical devices can simply select "No," but the field itself is now mandatory.
This change serves two purposes. It gives end users transparency about whether the app they are installing is subject to oversight by bodies like the U.S. Food and Drug Administration, and it forces developers to self-classify in a way that can be audited. The shift reflects growing regulatory scrutiny of digital health tools and the platform's desire to preempt liability by surfacing regulatory status before installation.
Age Verification Enforcement Adds Friction to 18+ Installs
Apple activated new age verification enforcement in Australia, Brazil, and Singapore in late February 2026. Users in these markets are now blocked from downloading apps rated 18+ unless their adult status has been confirmed through Apple's systems. This builds on the January 31, 2026 deadline by which all apps and games were required to complete Apple's updated age rating questionnaire — which introduced 13+, 16+, and 18+ tiers alongside the existing 4+ and 9+ ratings.
The immediate impact is a drop in wiki:conversion-rate for 18+ apps in these three markets. Adding friction to the install flow — even a justified gate like age confirmation — will reduce the percentage of users who complete the download. Developers with 18+ ratings should expect lower organic install counts from Australia, Brazil, and Singapore, and should monitor wiki:conversion-rate-optimization-cro metrics closely to understand the magnitude of the drop.
Apple also revised its User-Generated Content guideline (1.2), requiring apps with social or creator content to implement stronger moderation systems. These systems must include content filtering, reporting tools, user blocking, and clear contact information. Apps centered on anonymous chat, bullying, or explicit content may be removed outright. The guidance is clear: ignoring proper moderation infrastructure may result in removal from the App Store.
Google Blocked 1.75 Million Apps and Is Scaling Developer Verification
Google's annual Android and Google Play safety report for 2025 showed the platform blocked 1.75 million apps from distribution and removed 160 million spam ratings and reviews. The company's AI-powered review systems are now operating at scale, detecting threats both on and off the Play Store. Malicious apps detected via sideloading channels rose from 13 million in 2024 to 27 million in 2025, a shift that directly motivated Google's upcoming developer verification policy.
Starting in March 2026, Google opened its Android Developer Verification process to all developers. Previously in early access since late 2025, the process requires developers to verify their identity to distribute apps on certified Android devices — whether through the Play Store, alternative stores, or sideloading. This mandatory verification will reduce the volume of fraudulent, clone, and spammy apps entering the ecosystem, improving the signal-to-noise ratio for ranking signals like wiki:ratings-and-reviews, engagement, and keyword relevance.
Google also blocked average 0.5-star rating drops from review bombing campaigns in 2025. This protects legitimate apps' ratings from manipulation, but it also means that any spike in reviews — organic or otherwise — will be scrutinized. Incentivized review campaigns that violate review management guidelines face immediate suppression. Developers should expect tighter enforcement and faster detection of manipulation.
Framework Requirements and Developer Agreement Updates
Apple updated its Developer Program License Agreement to support new features and clarify data privacy requirements. The updates specify requirements for use of the Foveated Streaming framework, Family Controls framework, Accessory Notifications framework, and Accessory Live Activities framework. Developers must review and accept the updated terms to continue development. Translations of the updated agreement will be available on the Apple Developer website within one month.
These updates are not optional. Failure to accept the revised terms will block submission of new builds and updates. The changes reflect Apple's pattern of embedding compliance guidelines directly into the licensing process, ensuring developers acknowledge new framework policies before accessing platform features.
Fraud Detection and AI-Enabled Scams Are Shaping User Trust
Cybercrime cost US victims nearly $21 billion in the previous year, with investment and cryptocurrency scams being the most prevalent. AI-enabled fraud techniques — including voice cloning, deepfakes, and forged documents — accounted for approximately $893 million in losses. This is the first year AI-related scams were tracked separately in federal reporting.
For app developers, this context matters. Users are increasingly wary of apps that request sensitive permissions, store payment information, or facilitate financial transactions. Trust signals like data safety privacy disclosures, clear privacy policies, and transparent data handling are no longer optional for conversion optimization — they are baseline requirements to avoid triggering user skepticism shaped by external fraud trends.
The intersection of fraud detection, platform enforcement, and regulatory compliance is tightening. Developers must treat app review process and app store policy adherence as active disciplines, not checkbox exercises. The cost of non-compliance is no longer just a rejected build — it is lost update capability, removal from key markets, or visibility suppression through algorithmic filtering.
Takeaways for Practitioners
- Declare medical device status immediately if your app is in Health & Fitness or Medical categories, or references medical information in age ratings. Missing the early 2027 deadline will block updates.
- Monitor conversion rates in Australia, Brazil, and Singapore if your app carries an 18+ rating. Age verification friction will reduce installs; adjust UA spend and targeting accordingly.
- Implement moderation infrastructure if your app supports user-generated content. Apple's revised UGC guideline (1.2) is enforceable now, and removal is a real outcome.
- Complete Google's developer verification process as soon as it opens in March 2026. Verification will be mandatory for distribution, and delaying it may block future releases.
- Audit your review acquisition strategy to ensure compliance with Google's anti-manipulation policies. AI detection is live and suppressing incentivized reviews at scale.
- Update privacy disclosures and data safety labels to reflect the heightened user skepticism shaped by $21 billion in annual cybercrime losses. Transparency is now a conversion factor.