The EU’s €430M Google Play Fine Gives Web Checkout More Strategic Weight
An app store can be the door while the web becomes the deal desk. That is the commercial signal inside the European Commission’s latest Google decision. The headline number is €890 million, but the part web app builders should study is the separate €430 million fine tied to Google Play. Brussels says Google restricted developers from telling users about alternative offers and sending them to purchase on websites or through other app stores.
This is not a new browser API, a surprise PWA installation feature, or a rule that puts installable web apps inside Google Play. It is something more commercial: a decision about whether a store may control the route from app discovery to payment. If the ruling changes that route in practice, the open web becomes a more credible place to price, sell, activate, and manage app services—even when the customer first arrives through a native store.
What the European Commission decided
The Commission announced two Digital Markets Act non-compliance decisions on July 23. It fined Google €460 million for favoring its own shopping, hotel, transport, and sports services in Search, and €430 million for its Google Play anti-steering practices. Together, the fines total €890 million.
The Play decision is unusually direct about the role of the web. Under the DMA, the Commission says developers distributing through Google Play must be able to tell customers, free of charge, about alternative and often cheaper offers, then direct those customers to complete a purchase on a website or in another app store. Its finding was that Google did not meet that obligation: developers were prevented from freely communicating and promoting offers or concluding contracts through channels of their choice.
The regulator did not say Google can never earn anything from a customer acquired through Play. It accepted that Google may charge for facilitating the initial acquisition. The problem, it said, was that the level of steering-related fees and the length of time those fees continued went beyond what the DMA permits.
Google has been ordered to end the non-compliance and has 60 days to comply. The Commission says continued failure could lead to periodic penalties of up to 5% of Google’s total worldwide turnover. Google may appeal. In comments reported by the Associated Press, the company argued that the decision would degrade products and dismantle safety protections on Google Play. That dispute matters because the eventual implementation—not the fine by itself—will determine what developers and users actually experience.
Why this matters to web app businesses
App stores have traditionally bundled three jobs together: discovery, trust, and payment. The web can perform all three, but store rules and platform defaults have often made it difficult for a developer to move a user from a native app to an owned web relationship. Anti-steering restrictions are powerful because they do not merely set a commission; they shape what the product is allowed to say at the exact moment a customer is ready to buy.
The Commission’s decision challenges that control in Europe. For founders, it creates a stronger case for treating the website or installable web app as core product infrastructure rather than a marketing page attached to a store listing. A native app can remain a discovery and engagement surface, while a secure web experience handles plan comparison, checkout, account administration, upgrades, and cross-device continuity.
That model is especially relevant to subscription products, creator tools, media services, education platforms, productivity software, and other businesses where the customer relationship extends far beyond a single download. It also matters to teams with both a PWA and a native Android app. Their web app can become the consistent commerce and account layer across desktop, mobile browser, and installed experiences.
There is an important limit: the decision does not guarantee better economics. Google’s final fee structure, the permitted placement and wording of links, eligibility rules, and the amount of friction in the handoff will decide whether web checkout is genuinely competitive. A legal right to steer can still produce a poor funnel if the interface is buried, the warning language is alarming, or the account transition breaks.
The product work now moves to the handoff
If native-to-web steering becomes easier, developers inherit more responsibility for the quality and safety of the journey. Sending someone to “the website” is not a strategy. The destination has to feel like a continuation of the product.
- Preserve context. The web flow should recognize the plan, product, or creator the user selected before leaving the app, without exposing sensitive information in a URL.
- Make identity continuous. Authentication, account recovery, passkeys, and session handling should reduce repeated sign-ins while respecting browser security boundaries.
- Earn trust at checkout. Clear pricing, recognizable domains, transparent renewal terms, accessible controls, and strong payment security become part of the app experience.
- Design the return path. After purchase, users should land in the correct app or web state. Deep links, verified associations, and resilient fallbacks matter.
- Offer installation when it helps. A well-timed PWA install path can turn a one-off browser checkout into an ongoing owned channel, but it should follow user value rather than interrupt payment.
This is where installable web apps can gain leverage without pretending to replace native distribution overnight. A high-quality PWA can keep the relationship coherent after checkout: the same account, current subscription state, saved content, notifications where supported, offline resilience where useful, and an icon on the user’s device. The browser is no longer just the place a store sends people to pay; it can be a durable product surface.
What did not change
The Commission has not altered service workers, web app manifests, browser installation prompts, Android’s Trusted Web Activity model, or iOS support. It has not required Google Play to accept PWAs as store listings, and it has not removed the security and consumer-protection duties that apply to developers. The decision is an EU enforcement action aimed at Google’s designated gatekeeper services, not a worldwide rewrite of app-store commerce.
That distinction prevents a regulatory story from becoming false product hype. Web teams should not redesign checkout on the assumption that every Play restriction disappeared today. They should prepare an excellent owned flow, follow the implementation details, and test only the options that are actually available to their app, category, and market.
What IndApp watches next
The next 60 days are more important than the €430 million number. IndApp will watch how Google changes its steering terms, which surfaces may carry external offers, whether developers can communicate price differences clearly, and how the permitted acquisition fee and charging period are defined. We will also watch for an appeal and for any interim effect on implementation.
The product signals matter just as much as the legal text. Do users trust a browser handoff from an installed app? Can passkeys and verified links make the transition feel native? Will developers use the new freedom to build better offers, or simply reproduce a confusing checkout outside the store? And will a completed web purchase lead naturally into an installable web experience that the customer controls?
The durable takeaway is not that app stores are finished. It is that discovery, installation, payment, and retention no longer have to live in one controlled channel. Europe has put more pressure on Google to let developers connect those layers themselves. For web app companies, that makes the quality of the open-web product—and the trust it earns—a more strategic asset.
Further reading
Recent news
