Why Big Tech’s Walled Gardens Are Cracking: Antitrust, App Stores, and the Future of Mobile
This unbundling of Big Tech’s “walled gardens” could lower prices, spur new app business models, intensify competition in search and browsers, and change what users expect from their phones—while raising fresh questions about security, privacy, and regulatory fragmentation.
Antitrust and platform regulation have moved from niche policy debates to center stage in global tech. The mobile ecosystem—once tightly controlled by Apple’s App Store and Google Play—is being re‑architected in real time by court rulings, legislation like the EU’s Digital Markets Act (DMA), and enforcement actions across the U.S., U.K., South Korea, and beyond. At stake is who controls distribution, payments, and default choices on the devices billions of people rely on every day.
This article explains why app stores and defaults have become a prime target for regulators, how Apple and Google are responding, what it means for developers and users, and why the coming decade may see a partial “unbundling” of Big Tech’s walled gardens rather than their outright dismantling.
Mission Overview: Why App Stores Are in the Antitrust Crosshairs
For more than a decade, the dominant mobile business model has revolved around tightly controlled app stores:
- 30% (or 15%) commissions on digital goods and subscriptions.
- Exclusive in‑app payment rules, barring many apps from steering users to cheaper external payment options.
- Strict review and content policies, sometimes blocking categories like game streaming, cloud gaming, or certain financial products.
- Deep integration with defaults—pre‑installed apps, search and browser defaults, maps, messaging, and ads.
Regulators increasingly argue that this structure creates a classic bottleneck: a small number of gatekeepers stand between developers and users, raising prices and constraining innovation.
“When a company is both a powerful platform owner and a market participant on that platform, it has the ability and incentive to tilt the playing field.” — Margrethe Vestager, Executive Vice-President of the European Commission for A Europe Fit for the Digital Age
Consequently, the “mission” of current antitrust and platform‑regulation efforts is not to ban app stores or operating systems, but to open up critical layers: distribution options, payment systems, and defaults that shape user behavior at scale.
Technology of Regulation: How Laws Are Re‑Architecting App Ecosystems
While not “technology” in the software sense, modern platform rules are almost like protocols: they define what’s allowed at the interface between developers, users, and platform operators. Several key regimes are now in play.
European Union: The Digital Markets Act (DMA)
The DMA, fully applicable from 2024–2025, designates Apple, Google, Meta, Amazon, Microsoft, and others as “gatekeepers” and imposes specific obligations on them. For mobile OS and app stores, core DMA requirements include:
- Allowing alternative app stores or sideloading on designated platforms (e.g., iOS in the EU).
- Permitting third‑party payment systems and “steering” to external payment options.
- Enabling users to easily change defaults for browsers, search engines, and other core services.
- Prohibiting self‑preferencing in ranking or recommendation systems for the gatekeeper’s own services.
Apple and Google have released region‑specific updates to comply. These often include new APIs, entitlements, and fee structures—quickly scrutinized by regulators and developers to determine whether they offer meaningful openness or amount to “compliance theater.”
United States: Antitrust Cases and Proposed Rules
In the U.S., the approach leans more on traditional antitrust litigation and agency enforcement:
- The U.S. Department of Justice (DOJ) and several states have active cases against Google over search, ad tech, and allegedly exclusionary agreements with OEMs and carriers.
- The FTC and state attorneys general have brought actions challenging platform self‑preferencing and acquisitions aimed at choking off nascent threats.
- Congress has debated but not yet passed broad platform laws; instead, targeted bills (e.g., for app store competition) continue to resurface.
Other Jurisdictions: South Korea, U.K., and Beyond
South Korea’s “anti‑Google law” requires app stores to allow third‑party billing, influencing similar initiatives in other countries. The U.K.’s Digital Markets, Competition and Consumers Act (DMCC) empowers the Competition and Markets Authority to impose conduct requirements on firms with “Strategic Market Status.”
The common thread is clear: gatekeeper platforms must support more open interfaces for distribution, payments, and defaults, even if their exact obligations differ by jurisdiction.
Technology: How App Stores, Payments, and Defaults Actually Work
To understand the impact of regulation, it helps to see how app store “plumbing” operates today and how it might evolve.
Distribution: From Single Storefront to Multi‑Channel
Historically:
- iOS: Distribution was almost entirely via Apple’s App Store, with enterprise profiles and TestFlight as limited exceptions.
- Android: Google Play dominated, but sideloading and alternative stores (Samsung Galaxy Store, Amazon Appstore) have long existed, though often with friction and security warnings.
Under emerging rules—especially in the EU—users will increasingly see:
- Alternative app stores focused on gaming, productivity, open‑source apps, or regional content.
- Direct distribution via secure links or signed packages, possibly mediated by browsers or device management tools.
- New trust models, where reputation, cryptographic signatures, or curated lists (e.g., from nonprofits) help assure users of app integrity.
Payments: In‑App Purchase (IAP) vs. Third‑Party Billing
Platform in‑app purchase systems were designed to be:
- Frictionless—few taps, stored credentials, family sharing.
- Globalized—handling currencies, tax, refunds, and fraud detection.
- Highly monetized—with 15–30% commissions on digital sales and subscriptions.
Open‑up initiatives now require:
- Third‑party billing providers integrated via standardized APIs.
- “Steering” rights so apps can link users to external checkout flows (e.g., on the web) with potentially lower prices.
- Transparent fee disclosures so users understand when platform fees still apply to external payments.
From a developer perspective, this is technically non‑trivial. They must integrate:
- Multiple payment SDKs (Stripe, Adyen, PayPal, local wallets, etc.).
- Subscription lifecycle management outside of Apple/Google systems.
- Enhanced support for refunds, chargebacks, and tax compliance.
Defaults: The Hidden Architecture of User Choice
Defaults matter. Behavioral economists have repeatedly shown that most users stick with the pre‑selected option. On mobile, defaults affect:
- Which search engine your browser uses.
- Your default browser and in‑app web view handler.
- Default maps, assistants, and messaging apps.
Regulatory mandates now require more visible and meaningful choice screens. These will likely be implemented as:
- On‑boarding flows that prompt users to select key defaults at setup.
- Settings panels with clearer options and explanations for changing defaults later.
- APIs allowing third‑party apps to register as candidates for default roles.
Scientific Significance: Competition, Economics, and User Welfare
Antitrust in digital markets is an applied science problem sitting at the intersection of industrial organization, behavioral economics, and computer science. The unbundling of app stores touches several key research themes.
Market Power and Two‑Sided Platforms
App stores are two‑sided (or multi‑sided) platforms connecting developers and users, with cross‑side network effects: the more users on a platform, the more valuable it is to developers—and vice versa.
Economic research (e.g., work by Jean Tirole and others) shows that such platforms can:
- Sustain high fees while remaining attractive due to lock‑in and network effects.
- Use self‑preferencing to extend power from one market (OS/app store) into adjacent markets (music, cloud gaming, ads).
- Shape innovation direction by determining which apps and business models are viable.
Behavioral Effects of Defaults and Friction
Default search engines dramatically affect usage. Evidence from the U.S. v. Google Search case, and earlier studies of browser choice screens in the EU, suggests:
- Even minor choice friction can entrench incumbents.
- Prominence on a choice screen (first slot, pre‑checked option) heavily biases selection.
- Transparent, neutral choice screens can measurably increase diversity of services used.
“Defaults are powerful; changing them is often enough to change market outcomes.” — Tim Wu, Columbia Law School professor and former White House advisor on competition policy
Innovation and Entry
A core question is whether high platform fees and restrictive rules:
- Delay or suppress entry of innovative but low‑margin apps (e.g., education, health, public‑interest tools).
- Push developers toward ad‑supported models that may be worse for privacy and user experience.
- Discourage competing app stores or payment systems that could specialize in niche segments.
Early empirical evidence is mixed but suggests that lower commissions and more flexible rules can support more experimentation—especially among smaller developers.
Milestones: Key Cases, Laws, and Turning Points
The journey toward unbundling Big Tech’s walled gardens is marked by several landmark events.
Epic Games v. Apple and Parallel Litigation
- 2020–2021: Epic bypassed Apple’s in‑app purchasing, triggering Fortnite’s removal and a high‑profile lawsuit.
- Outcome: U.S. courts largely upheld Apple’s model but required limited anti‑steering remedies (allowing links to external payment options), subject to ongoing appeals and interpretation.
While not a total win for Epic, the case catalyzed public scrutiny of app store economics and informed later regulatory efforts.
EU Commission Decisions and the DMA Rollout
- 2018–2022: Major EU decisions against Google on Android tying, search bias (Google Shopping), and ad tech practices, combined with significant fines.
- 2023–2025: Gatekeeper designations and DMA compliance deadlines trigger fundamental changes to iOS and Android in the EU, including alternative stores and new payment options.
South Korea’s Anti‑Google Billing Law
South Korea became the first country to explicitly require app stores to allow alternative billing systems. While initially focused on Google, the law set a precedent for targeted intervention on in‑app payments, encouraging similar proposals in other markets.
U.S. Search and App Store Scrutiny
- U.S. v. Google (Search): Challenging default search deals that made Google the preset option on browsers and mobile devices.
- Emerging U.S. app store cases: Ongoing investigations around self‑preferencing and exclusionary practices, with potential for structural or conduct remedies later in the decade.
Impact on Developers and Startups
For developers, the unbundling of platform control is both an opportunity and a new layer of complexity.
New Opportunities
- Lower effective fees: Third‑party payment options and competing stores can reduce transaction costs, improving unit economics, especially for subscription‑based apps and content platforms.
- New business models: Apps previously blocked—such as full‑fledged cloud gaming services, certain financial products, or experimental media formats—may gain viable distribution paths.
- Specialized app stores: Curated stores for privacy‑focused apps, enterprise tools, or indie games could differentiate on policy, discovery, and revenue share.
Operational and Technical Overhead
On the downside, developers now face:
- Regulatory fragmentation: Maintaining different builds, in‑app flows, and feature flags for the EU, U.S., U.K., South Korea, and others.
- Complex payment stacks: Integrating multiple payment processors, handling tax across jurisdictions, and reconciling payouts from several app stores.
- Support and security risks: Users may encounter more varied installation paths and billing issues, increasing support surface area.
A practical strategy many teams adopt is to:
- Design a modular billing architecture with clear abstraction layers.
- Use feature flags and remote configuration to swap flows by region.
- Rely on well‑supported SDKs and compliance tools rather than building everything in‑house.
Tools and Resources Developers May Find Useful
While I cannot guarantee current pricing or stock, developers often pair regulatory shifts with upgrading their testing setups. For example:
- A reliable multi‑device testing station, such as a modern Apple MacBook Pro with Apple Silicon, can help teams debug region‑specific builds and app store flows efficiently.
Impact on Users: Choice, Price, and Security
For ordinary users, changes often show up subtly—new prompts, pricing variations, or additional options in settings—rather than dramatic overnight shifts.
Benefits for Users
- Potentially lower prices for digital goods and subscriptions, as developers pass some fee savings through.
- More choice of apps and defaults—for browsers, search engines, messaging, and maps.
- Access to new app categories that were previously restricted or economically unviable.
Risks and Trade‑offs
Unbundling also comes with new responsibilities:
- Security: Sideloading and alternative stores can increase exposure to malware if not carefully vetted. Users should favor reputable sources and pay attention to permissions.
- Privacy: Some third‑party app stores or billing systems may have weaker privacy protections than first‑party solutions.
- Usability: More prompts and choice screens can create decision fatigue if not well‑designed.
“Security is a process, not a product. As we open platforms, we must also upgrade our norms and tools for staying safe.” — Bruce Schneier, security technologist and lecturer at Harvard Kennedy School
Practical Tips for Users
- Install apps primarily from trusted stores or well‑known developers.
- Review permissions and reviews before installing from new sources.
- Regularly check default settings for browser, search, and tracking preferences.
- Use password managers and two‑factor authentication for third‑party payment accounts.
Challenges: Compliance, Security, and Regulatory Fragmentation
Even if the direction of travel is clear—toward more openness—the path is fraught with implementation challenges.
Platform Compliance vs. “Compliance Theater”
A recurring criticism is that some changes are more cosmetic than substantive. Examples include:
- Alternative payment options that still attract new platform fees, limiting economic benefits.
- Complex eligibility rules or technical requirements that only large developers can realistically meet.
- Choice screens designed in ways that nudge users back to incumbents.
Security and Trust in More Open Ecosystems
Opening distribution and payments must be balanced with:
- Robust code‑signing and notarization to prevent malware.
- Stronger app review and reputation systems across multiple stores.
- Clear liability frameworks when third‑party stores or billers fail.
There is ongoing debate over how much gatekeeping is necessary for security versus how much is simply rent‑seeking.
Global Fragmentation
Divergent rules create a de facto experiment across jurisdictions, but also:
- Increase compliance costs for global apps.
- Complicate user experiences when traveling or moving between regions.
- Encourage geofencing features, where capabilities depend on locale, potentially undermining a unified open internet.
Looking Ahead: Possible Scenarios for the 2026–2030 Landscape
As of 2026, we are in an early transitional phase. Several plausible future paths stand out:
Scenario 1: Managed Openness
- Alternative app stores and payments become normalized but curated—with strong security baselines and clear rules.
- Platform fees fall modestly, but app stores remain profitable and widely used for discovery, updates, and trust.
- Defaults become more contestable, yet incumbents keep significant share due to brand and quality.
Scenario 2: Competitive Fragmentation
- Multiple major app stores coexist, some operated by device makers, carriers, or large publishers.
- Developers tailor offerings to different stores with varying revenue shares and feature sets.
- Users juggle several accounts and update mechanisms; security outcomes depend heavily on store governance.
Scenario 3: Regulatory Overreach and Backlash
- Complex rules stifle new business models or create significant compliance burdens.
- Security incidents linked to less‑controlled channels trigger calls to re‑tighten platform control.
- Some jurisdictions roll back or soften requirements after negative side effects emerge.
The actual outcome may blend elements of all three, with different regions gravitating toward different equilibria.
Conclusion: The Slow Unbundling of Walled Gardens
App stores and default settings are no longer mere UX details—they are critical levers of economic power and innovation. As regulators force Apple, Google, and other giants to open up distribution, payments, and defaults, we are witnessing a structural shift in how digital markets operate.
For users, this promises more choice and, in some cases, better prices and more diverse services. For developers, it offers new monetization models and competitive opportunities, balanced against greater technical and regulatory complexity. For policymakers, it is an ongoing experiment in calibrating openness, safety, and incentives for innovation.
The walled gardens of Big Tech are unlikely to vanish, but their walls are being lowered and perforated. The next few years will determine whether these openings become genuine gateways for competition or simply new façades on the same old fortresses.
Additional Resources and Further Reading
For readers who want to dive deeper into the legal, economic, and technical dimensions of app store antitrust, the following resources are useful starting points:
- EU Digital Markets Act overview (European Commission): https://digital-strategy.ec.europa.eu/en/policies/digital-markets-act
- U.S. DOJ Antitrust Division: https://www.justice.gov/atr
- UK Competition & Markets Authority digital page: https://www.gov.uk/government/collections/digital-markets-research
- Epic Games v. Apple court documents summary (Stanford Law): https://law.stanford.edu/projects/epic-games-v-apple-case-resources/
- Tim Wu’s writings on net neutrality and platform power: https://scholarship.law.columbia.edu/faculty_scholarship/1775/
- Bruce Schneier on security and openness: https://www.schneier.com/
- Video explainers on the DMA and app store competition (YouTube, various creators): https://www.youtube.com/results?search_query=eu+dma+app+stores
- Discussion and analysis on LinkedIn by antitrust scholars and policy makers: https://www.linkedin.com/search/results/content/?keywords=app%20store%20antitrust
References / Sources
Selected key sources informing this overview:
- European Commission – Digital Markets Act: https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32022R1925
- European Commission competition cases on Google: https://competition-policy.ec.europa.eu/public-consultations/concluded/antitrust-cases-google-search-shopping_en
- U.S. v. Google Search (DOJ): https://www.justice.gov/opa/pr/justice-department-sues-monopolist-google-violating-antitrust-laws
- South Korea Telecommunications Business Act amendments: https://www.law.go.kr (in Korean)
- UK Digital Markets, Competition and Consumers Act (DMCC) information: https://www.gov.uk/government/collections/digital-markets-competition-and-consumers-bill
- Stanford Law School – Epic Games v. Apple resource hub: https://law.stanford.edu/projects/epic-games-v-apple-case-resources/