Commission reductions signal regulatory influence on platform economics
The long-standing 30% standard commission is fragmenting. As of March 15, Apple reduced its App Store commission on the China mainland storefront from 30% to 25%, with corresponding reductions for Small Business Program participants (from 15% to 12%). The change applied automatically — no developer action required — and marks the first time Apple has publicly acknowledged regional commission variance driven by regulatory negotiation.
Meanwhile, Google announced a settlement with Epic Games that restructures Play Store commissions globally. The new base rate for in-app purchases from new installs drops to 20% (from 30%), with subscriptions at 10%. However, developers in the US, EEA, and UK face an additional 5% billing fee when using Google Play Billing. The new structure takes effect by June 30, 2026 in those regions, with global rollout completed by September 2027.
For practitioners, the immediate impact is unit economics. A 5-point margin improvement on every transaction in China, or a 10-point improvement on Play installs, changes LTV calculations and payback periods. Pricing strategies that were marginal under 30% suddenly become viable. Developers prioritizing these markets should model revised monetization funnels now — not after the changes land.
Europe already operates at a 17% effective rate under the Digital Markets Act. The precedent is clear: wiki:app-store-policy frameworks are no longer globally uniform. Revenue modeling must now account for regional variance in platform fees.
Promo code deprecation forces migration to Offer Codes
Apple discontinued the legacy IAP promo code system on March 26. Existing promo codes remain valid until expiration, but no new codes can be generated. The replacement — Offer Codes — supports all IAP types (consumables, non-consumables, subscriptions) with eligibility segmentation (new, active, lapsed users), redemption limits, and human-readable code strings.
The change is more than cosmetic. Legacy promo codes were fire-and-forget distribution tools with no segmentation or budget control. Offer Codes enable targeted promotional funnels with spend caps and attribution. For wiki:conversion-rate-optimization-cro practitioners, this means acquisition campaigns can now be structured with the same precision as paid ads — distinct offers for re-engagement, first-time conversions, or winback.
Developers relying on promo-driven acquisition or retention flows should audit existing campaigns and rebuild them in the new system before legacy codes expire.
Security failures reveal persistent gaps in app review
On April 14, Apple removed a fake Ledger Live app that had stolen millions in cryptocurrency from at least 50 users over a seven-day period (April 7–13). Three victims lost seven-figure sums: $3.23 million in USDT, $2.08 million in USDC, and $1.95 million across BTC, ETH, and stETH. Stolen funds were traced to KuCoin deposit addresses associated with a centralized mixing service.
The same day, Apple pulled Freecash, a data-harvesting app that had climbed the top charts over several months by tricking users during onboarding. Both incidents raise the same question: how did these apps pass wiki:app-review-process in the first place, and why did enforcement take a week after the first theft reports surfaced?
When OpenAI launched its official Sora mobile app in late 2025, the App Store was flooded with over a dozen "Sora" and "Sora 2" branded fakes within days. Those clones accumulated hundreds of thousands of downloads and significant revenue before removal. The pattern is consistent: malicious actors exploit the review process, users pay the price, and removal comes only after external pressure.
For app developers, the takeaway is not just reputational risk from lookalike scams. It is that brand aso enforcement — even with registered trademarks — relies on external documentation and persistent pressure. Successful removals require side-by-side comparisons, legal letters, and direct engagement with platform reviewers. The dispute process is opaque, slow, and not designed to preempt harm.
Compliance deadlines and SDK requirements tighten
Apple set a hard deadline of April 28, 2026 for all App Store submissions: apps must be built with iOS 26, tvOS 26, visionOS 26, or watchOS 26 SDKs. This is not a grace period — it is four weeks from the March announcement. Developers still shipping on iOS 25 SDKs risk rejection at submission.
On the Android side, developer verification becomes mandatory by September 30, 2026 in Brazil, Indonesia, Singapore, and Thailand. The new Android Developer Verifier requires biometric authentication, a 24-hour waiting period, and device registration. Developers who have completed identity verification in Play Console are enrolled automatically; others must complete the process or lose the ability to distribute apps in those markets.
Google also reached Platform Stability with Android 17 Beta 3 in late March, locking APIs and behavioral models ahead of the expected June stable release. New restrictions on runtime code modification and mandatory support for resizable windows and aspect ratios will directly affect android vitals scoring and Play Store ranking.
The operational implication: compliance is no longer a background task. Missing an SDK migration deadline or failing to complete developer verification blocks distribution. These are now hard gates in the publishing pipeline.
Discovery surfaces and featuring priorities shift
Google redesigned Play Store discovery flows in March, emphasizing personalized collections and algorithmic recommendations over manual browsing. The shift mirrors App Store trends toward machine-driven surfaces and away from editorial curation — except in high-visibility featuring slots tied to platform priorities.
Apple announced WWDC26 for June 8–12, which historically signals the next wave of App Store featuring themes. iOS 27, macOS 27, and Apple Intelligence updates will reshape what the platform promotes through app store featuring and search result weighting. Developers targeting featuring opportunities should align metadata and creative assets with announced platform capabilities as soon as beta SDKs drop.
The march toward AI-driven discovery continues. Apps that do not surface in algorithmic recommendations — whether through quality signals, engagement metrics, or metadata relevance — increasingly operate in a visibility dead zone. Manual search and direct linking remain viable, but the majority of installs now originate from surfaces developers do not directly control.
What to do now
- Remodel unit economics for China mainland (25% commission) and Google Play (20% base + 5% billing fee in select regions). Update LTV and payback calculations accordingly.
- Migrate promo code campaigns to Offer Codes with segmentation and budget controls. Legacy codes expire on their original schedules — no extensions.
- Complete SDK migrations before April 28 (iOS 26+) to avoid submission rejection. Plan testing cycles now.
- Register for Android Developer Verifier if not already enrolled through Play Console identity verification. September 30 is the compliance deadline for four key markets.
- Document brand assets and file trademarks if not already done. Clone apps bypass review; enforcement depends on having registration certificates ready to submit.
- Monitor subscription metrics for anomalies in Day 0 cancellations, D35 conversion rates, and involuntary churn — early indicators of brand confusion from copycats.
- Audit apps against Android 17 requirements for resizability, aspect ratio flexibility, and runtime code restrictions. Non-compliance will degrade vitals scoring post-launch.