+150 XP

SaaS · How platforms squeeze the apps built on top of them

In 2008, Apple opened the App Store and told developers they had found a goldmine: a built-in audience of millions, one distribution channel, no need to build their own payment rails. By the early 2020s, some of those same developers (Spotify, Epic Games, Basecamp) were suing Apple, testifying before Congress, and lobbying regulators in Brussels. Same platform. Same 30% cut it had charged from day one. What changed was the size of the businesses now trapped inside it.

This is the lifecycle every platform ecosystem eventually reveals: welcome the apps, grow the pie, then reach back in and take a bigger slice. This lesson breaks down the mechanics platforms use to do it.

Why platforms need third-party apps at all

A platform is a business that creates value primarily by connecting two or more groups: buyers and sellers, developers and users, merchants and shoppers. Think Apple's iOS, Salesforce's CRM (customer relationship management) infrastructure, or Shopify's e-commerce backend.

No platform can build every feature its users want. So it opens an "app store" or "marketplace" layer: Apple's App Store, Salesforce's AppExchange, Shopify's App Store. Third-party developers fill gaps (accounting integrations, loyalty programs, shipping tools) that would take the platform years to build itself.

Early on, incentives align. The platform wants developers to join because more apps make the platform stickier for end users. Developers want in because the platform hands them distribution they couldn't otherwise afford.

This is the honeymoon phase. It never lasts once an app category proves it can generate serious revenue.

The three levers of the squeeze

Platforms reclaim value from their ecosystems through three repeatable mechanics.

1. Take-rate changes (the toll booth)

The simplest lever: raise or restructure the cut the platform takes on transactions.

Apple's headline App Store commission has been 30% on most digital goods and subscriptions since 2008. It has two main 15% exceptions. The Small Business Program, introduced in 2021, applies to developers earning under $1 million a year (Apple's official terms). Separately, subscriptions drop to 15% after a subscriber's first year, regardless of developer size. The number itself matters less than the fact that Apple, not the developer, sets it. It also applies to relationships the developer originated: a user who found an app through word of mouth has historically still paid through Apple's in-app purchase system on iOS.

Salesforce's AppExchange works through partner agreements rather than a public consumer-style rate card. ISV (independent software vendor) partners typically pay Salesforce a share of the revenue from apps built on its platform. Every listed app must also pass a paid security review, and deep OEM (original equipment manufacturer) arrangements can carry steep terms.

Shopify shows how a platform can move the toll booth without touching the headline rate. In 2021 it announced that developers would pay 0% on their first $1 million of App Store revenue each year and 15% above that. In 2025 it changed the threshold from annual to lifetime revenue (Shopify's revenue share terms). The rate stayed at 15%, but an established app now pays it every year after crossing the threshold once. Shopify also earns through Shopify Payments, pushing merchants toward its own payment rails with extra fees for using third-party processors.

2. Bundling (build the feature, kill the market)

The second lever: once a third-party app category proves demand, the platform builds its own version and bundles it for free or near-free.

The classic example outside SaaS is Microsoft bundling Internet Explorer into Windows, which triggered the landmark *United States v. Microsoft* (1998 to 2001) antitrust case. Inside SaaS, the pattern repeats constantly:

  • Shopify launched Shopify Email, Shopify Shipping and Shopify Collabs, competing with third-party apps (Klaviyo for email, ShipStation for shipping, affiliate platforms) that built their businesses in the Shopify ecosystem.
  • Salesforce has repeatedly absorbed functionality that used to require AppExchange add-ons, from native analytics to AI features under the Einstein and later Agentforce brands.
  • Apple has bundled flashlights, screen recorders and password managers into iOS over the years, wiping out entire micro-categories of App Store developers overnight.

Bundling works because the platform doesn't need to be as good as the incumbent app. "Good enough, free and pre-installed" beats "better, but $4.99/month and requires a download" for most users.

3. Data and API access restrictions (closing the tap)

The third lever is subtler and often more devastating: restricting the data or APIs (application programming interfaces, the technical channels that let outside software talk to the platform) that third-party apps depend on.

Facebook cut off developers' access to friend-graph data in 2015 after building an ecosystem around it, killing many social apps that depended on that data. Twitter (now X) sharply restricted free API access in 2023, forcing many third-party clients and analytics tools to shut down or pay steep new fees.

In SaaS, Salesforce sets API call limits by pricing tier, so an AppExchange partner's product can be throttled or made uneconomical for customers on lower Salesforce plans. Shopify has periodically tightened checkout customization APIs, restricting how deeply third-party apps can modify the checkout flow. Security is part of the reason. Protecting Shopify Payments and Shop Pay from being routed around is another.

The mechanism is quiet but total. You don't need to ban a competitor's app. You only need to make the plumbing it relies on slower, costlier or off-limits.

Knowledge check

1. Why do platforms initially open their ecosystems to third-party developers rather than building every feature themselves?

2. According to the lesson's framing of the platform lifecycle, what typically triggers a platform to start 'squeezing' an app category it previously welcomed?

3. What is the key distinction between the 'honeymoon phase' and the 'squeeze phase' of the platform-developer relationship, given that the take-rate (like Apple's 30% cut) may stay identical throughout?

MULTIPLE CHOICE

4. Select ALL correct answers about what defines a 'platform' business in this lesson's sense.

Select all the correct answers.

MULTIPLE CHOICE

5. Select ALL correct answers about why large, successful third-party developers become especially vulnerable to platform squeezes over time.

Select all the correct answers.

Why platforms can get away with it: the power dynamic

This comes down to switching costs and distribution control.

An app built on Shopify's infrastructure cannot easily "leave" Shopify without its merchant customers rebuilding their entire storefront elsewhere. An iOS app cannot reach iPhone users except through Apple's store, absent regulatory intervention. This asymmetry is the core power dynamic of the module: the platform owns the distribution chokepoint, and the app is a guest, no matter how large it grows.

Regulators have started pushing back. The EU's Digital Markets Act (DMA, applicable since 2023) designates large platforms as "gatekeepers." It forces Apple to allow alternative app stores, sideloading (installing apps outside the official store) and alternative payment systems on iOS in the EU. Apple has responded with new fee structures for developers who use these options, and the European Commission has fined it under the DMA, so the fight over the toll booth continues in a new form.

In the US, the *Epic Games v. Apple* litigation began with a 2021 ruling. A much stronger order followed in 2025, when a court found Apple had violated the original injunction and barred it from charging commission on purchases made through external links. Apple has challenged parts of that order on appeal, so the final shape of US link-out rules may still shift. It is still a meaningful crack in the toll booth.

The countervailing power in this dynamic comes from regulators (the European Commission, US courts, the FTC) and from large developers with the revenue and legal budget to litigate (Epic, Spotify). Occasionally coordinated developer lobbying helps too, as with the Coalition for App Fairness. Small developers rarely have this leverage alone. They absorb the squeeze or exit the category.

Why Apple and Epic Games Are Fighting

Watch on YouTube

A simple worked illustration

Take two subscription productivity apps on iOS, both charging $10/month.

The small one has 5,000 subscribers.

  • Gross revenue: $50,000/month, or $600,000/year, under Apple's $1M threshold
  • At the standard 30%: Apple takes $15,000/month, the developer keeps $35,000
  • In the Small Business Program at 15%: Apple takes $7,500/month, the developer keeps $42,500

The large one has 100,000 subscribers.

  • Gross revenue: $1,000,000/month, about $12M/year, far too big for the Small Business Program
  • First-year subscribers are charged 30%. Subscribers past their first year drop to 15%
  • If half the base is past year one, Apple takes $150,000 + $75,000 = $225,000/month, and the developer keeps $775,000

For the small app, the program is worth $90,000 a year, often the difference between profit and loss. The large app's margin depends on retention, which Apple's rate structure rewards. Both cases show why threshold and eligibility rules are a site of negotiation and lobbying, not an abstract policy detail.

Key Takeaways

  • Platforms extract value from their app ecosystems with three mechanics: changing take rates, bundling competing features natively, and restricting data or API access.
  • Take-rate changes can be quiet. Shopify kept its 15% rate but switched its $1M threshold from annual to lifetime revenue, which raised costs for established apps.
  • Platforms recruit developers when they need ecosystem breadth, then reclaim value once a category proves profitable enough to matter.
  • Power is asymmetric because platforms control distribution and switching costs are high, so small developers absorb the squeeze while large players (Epic, Spotify) and regulators push back.
  • The EU's Digital Markets Act and *Epic v. Apple* have forced concrete changes to fees and payment options. Platforms keep adapting their terms in response, and enforcement varies by region.
  • When evaluating any SaaS ecosystem play, ask which lever the platform could pull against you, and how much of your distribution and data access runs through someone else's toll booth.