CMA's Big Tech Crackdown: What It Means for UK App Markets

The Competition and Markets Authority has moved decisively into a new enforcement phase. After months of investigation, the regulator is now actively testing whether Apple and Google are abusing their dominance in app distribution and mobile operating systems—and the implications are substantial for every UK business reliant on digital platforms.

This isn't theoretical regulation anymore. The Digital Markets, Competition and Consumers Act (DMCC) gives the CMA legal teeth it didn't have before. And unlike previous regulatory efforts that felt glacial, enforcement is accelerating. For C-suite leaders, this means immediate questions about app strategy, vendor relationships, and how quickly new competitors can actually challenge incumbents in the UK market.

The CMA's Renewed Enforcement Focus

The CMA has long investigated Apple's App Store and Google Play practices. But the regulatory landscape shifted fundamentally with the DMCC, which came into force in the UK in 2024. This legislation introduced designations for "Digital Markets Conduct" (DMC) rules—obligations imposed on platforms deemed to have "strategic market status."

What's changed is the enforcement mechanism. Previously, investigations could drag for years. The CMA now has statutory authority to impose conduct requirements on dominant platforms without waiting for an abuse finding under the Competition Act. This represents a material acceleration in regulatory tempo.

In May 2026, the CMA escalated pressure on both Apple and Google by signalling enforcement action on specific concerns: app store fees, restrictions on alternative payment methods, and barriers to third-party app distribution. The regulator isn't proposing a ban on commission structures—but it is requiring that Apple and Google justify why users can't choose payment processors, and why smaller developers face disproportionate barriers to distribution.

For enterprise leaders, this matters immediately. If Apple must permit alternative app stores or payment processors on iOS, enterprise software distribution changes fundamentally. If Google faces restrictions on how it ties Google Play services to Android, the landscape for cloud applications and SaaS integration shifts.

Apple App Store: Under the Microscope

The CMA's investigation into Apple focuses on three core issues: commission structures, restriction of web applications, and terms of service that disadvantage third-party app developers.

Apple's 15-30% commission on in-app purchases has been a lightning rod for regulation globally. The CMA's angle isn't to eliminate commissions entirely—economics still matter—but to examine whether Apple's commission is justified by the services provided, and whether developers have genuine alternatives. Currently, they don't. Developers can't direct users to a payment processor outside the App Store without triggering removal.

More significantly for UK enterprise software, the CMA is examining Apple's treatment of web applications. Progressive web apps (PWAs) offer functionality comparable to native apps but bypass the App Store entirely. Apple has deliberately restricted PWA capabilities on iOS—a strategic choice, the CMA argues, that protects App Store revenues rather than serving user safety or legitimate technical needs. If the CMA forces Apple to allow full PWA functionality, the economics of app distribution fundamentally change.

The third enforcement angle concerns terms of service that disadvantage competing platforms. Apple's requirement that enterprise apps use Apple's sign-in system, for example, creates friction for applications that operate across iOS and Android. The CMA's position is that these requirements exceed what's necessary for security or interoperability.

UK businesses should monitor developments closely: if the CMA mandates interoperability requirements or restricts Apple's ability to tie services, your app strategy may need adjustment. A shift toward PWAs or alternative distribution could become viable in the next 12-24 months.

Google's Android Ecosystem Under Strain

The CMA investigation into Google has a different texture, but equally serious implications. Google's leverage is less about a single app store and more about the integration of Google Play, Google Search, Android itself, and Google Cloud services.

The core CMA concern: Google uses Android dominance to foreclose competition in adjacent markets. Specifically, Google Play Services—a software layer installed on most Android devices—gives Google preferential access to user data and application functionality that third-party developers cannot match. This is particularly acute for cloud synchronization, authentication, and analytics services.

This affects UK enterprise software significantly. If you've built an Android application that relies on Google Play Services for user authentication or cloud integration, you've implicitly accepted Google's data-sharing terms and architecture. Competitors offering equivalent functionality face higher friction because they can't integrate as deeply with the OS.

The CMA's remedies are likely to include mandatory interoperability requirements: Google must allow alternative authentication systems on Android with equivalent technical capability, and must not restrict data access to competing cloud services. Google's proposal to allow alternative app stores on Android is a concession, but the CMA wants more—genuine technical parity, not just formal access.

For UK software vendors, this could create real opportunity. If Google's gatekeeping is reduced, alternatives to Google Play Services become viable. UK-based cloud providers or authentication services could compete on merit rather than integration depth. That's significant for CMA enforcement roadmaps.

Cloud Markets and the Broader Competition Picture

The app store investigations are symptomatic of a larger CMA focus: competitive access to digital infrastructure. The regulator has also launched a market investigation into cloud computing services, examining whether Amazon Web Services' dominance forecloses competition for SME and enterprise customers.

The connection is direct. If Apple and Google can restrict which cloud services their platforms privilege, they maintain indirect control over the cloud market. AWS similarly has preferential integration with Android via Google Cloud. Microsoft faces friction in equivalent scenarios. The CMA's hypothesis is that these integration barriers aren't inevitable—they're choices that reinforce dominance.

UK enterprise leaders should recognize the regulatory direction: the CMA believes digital markets are artificially concentrated because dominant platforms create technical and commercial barriers that newer competitors cannot overcome. The solution is mandatory interoperability and data access, not breakup of platforms.

This has direct implications for your digital procurement strategy. If the CMA mandates interoperability, smaller cloud providers and SaaS vendors become technically viable alternatives to incumbents. Your procurement team may have new options—and regulatory approval of those options—within 18 months.

Timeline, Risk Factors, and Strategic Implications

The CMA has indicated it expects to conclude initial enforcement decisions by Q4 2026. This is unusually quick for competition enforcement, reflecting statutory authorities under the DMCC.

What happens next depends on several variables:

• UK-US regulatory coordination: The US Department of Justice and FTC are pursuing parallel investigations. If the US takes aggressive action against Apple and Google before the CMA finalizes remedies, UK enforcement may accelerate or diverge. Monitor FTC announcements closely.
• Business case challenges: Apple and Google will argue that proposed remedies are technically infeasible or compromise security. The CMA must weigh these arguments. Litigation risk is real—both companies have resources for extended appeals.
• EU coordination: The Digital Markets Act in the EU has already shaped Apple and Google behavior globally. The CMA's DMCC remedies may diverge from EU requirements or reinforce them. Divergence creates compliance complexity for multinational vendors.
• International precedent: South Korea, Japan, and other jurisdictions are watching the UK and EU closely. A successful CMA enforcement action creates global momentum for interoperability requirements.

For UK-based technology leaders, the strategic calculus is:

If you're dependent on App Store or Google Play distribution: Diversify. Evaluate PWA strategies for consumer-facing applications. For enterprise apps, explore direct distribution channels or B2B2C models that reduce reliance on app store gatekeeping. The regulatory probability of material change to iOS and Android distribution is now >60% within 24 months.

If you operate cloud services: The CMA's enforcement message is that interoperability is mandated, not optional. Ensure your APIs and data formats are documented and accessible. If you're competing against AWS or Microsoft on UK contracts, regulation may shift the competitive dynamics in your favor—but only if you're technically prepared to demonstrate interoperability.

If you're a smaller vendor trying to compete: The CMA's enforcement is designed for you. Regulatory relief of Big Tech gatekeeping is the CMA's explicit objective. Position your product positioning around what becomes possible after regulation: better cloud integration choices, alternative payment methods, or data portability. Monitor enforcement timelines and adjust go-to-market strategy accordingly.

Forward-Looking Analysis: What Comes After Enforcement Decisions

Assuming the CMA issues enforcement decisions in Q4 2026, the next phase is implementation and appeals. Apple and Google will contest remedies. The CMA will face technical questions about how to operationalize interoperability requirements.

The most likely outcomes:

Apple scenario: The CMA mandates that iOS support PWAs with full capability equivalent to native apps, and allows alternative payment methods for app purchases. Apple complies but implements this in ways that maximize friction—longer PWA loading times, restricted background capabilities, reduced notification support. The CMA then faces pressure to enforce additional technical requirements. Timeline: 6-18 months of clarifications after initial enforcement decision.

Google scenario: The CMA mandates interoperability for Google Play Services—meaning other companies can provide authentication and cloud synchronization with equivalent technical capability to Google's. Google complies but bundles services more tightly, making unbundling technically complex. The CMA pursues additional remedies. Timeline: similar.

Broader implication: The DMCC is untested legislation. Early enforcement decisions will be contested and refined through litigation. Expect a 18-36 month cycle from initial CMA decision to stable, final remedies.

For C-suite leaders, this means horizon planning. Your digital strategy should prepare for a competitive landscape where:

• App store gatekeeping is materially reduced by 2027-2028
• Cloud vendor choice expands as interoperability mandates are enforced
• Smaller vendors have genuine technical parity to compete against incumbents
• Your vendor contracts may need renegotiation if they assumed exclusive technical integration

The CMA's enforcement phase represents the most significant structural change to UK digital markets in a decade. Unlike previous regulation that felt abstract, these decisions will have immediate operational implications for your technology stack and competitive positioning.

Monitor CMA case updates and Parliamentary tech committee scrutiny closely. The enforcement timeline is now measured in months, not years.