The App Store Freedom Act Is Back—and Web Apps Should Pay Attention
America’s app-store debate has moved out of the archive and back into a congressional hearing room. On July 22, a House Energy and Commerce subcommittee included the App Store Freedom Act in a hearing on consumer protection legislation. The proposal would require the largest integrated app-store operators to permit installation outside their own stores, allow third-party defaults, open access to operating-system features, and loosen their control over payments and developer communications.
That sounds like a major distribution reset. It is not one—not yet. The hearing did not pass the bill, amend it, or send it to the House floor. Congress.gov still lists H.R. 3209 as introduced, with its formal legislative status unchanged. No founder should rewrite a mobile roadmap because of this hearing alone. The news is that a proposal with direct consequences for digital distribution has returned to an active policy forum after spending more than a year at the introduced stage.
What the proposal would actually require
The bill defines a covered company by scale and control rather than naming particular businesses. It applies to a company that controls both an operating system and an app store with more than 100 million users in the United States. That design plainly focuses attention on the largest integrated mobile platforms, but the legal test is the definition in the bill—not a list of brands.
Under the introduced text, a covered company would have to provide readily accessible ways for users to:
- Choose a third-party app or app store as a default.
- Install third-party apps and app stores through channels other than the platform owner’s store.
- Hide or remove apps and app stores supplied or preinstalled by the covered company or its partners.
The proposal would also require access to operating-system interfaces and hardware or software features on terms equivalent to those available to the platform owner and its business partners. It would prohibit tying store access to the platform’s payment system, penalizing developers for different prices elsewhere, restricting legitimate communications with users about offers, and using certain nonpublic developer data to compete with an app.
Those provisions would be enforced by the Federal Trade Commission and, in specified circumstances, by states. The text provides for an additional civil penalty of up to $1 million per violation. Even if both chambers passed the bill and a president signed it, it would not switch on immediately: the FTC would first issue implementation guidance, with the bill allowing up to 180 days after enactment for that step.
Why web-app teams belong in this conversation
The proposal never uses the term progressive web app. It does not modify service workers, Web App Manifests, browser installation prompts, push notifications, background execution, or any other browser capability. It would not suddenly make an iPhone or Android device treat every web app like a deeply integrated native application.
But the text is broader than a conventional fight over downloadable binaries. Its definition of an app includes an electronic service, while its definition of an app store includes a publicly available website or other electronic service that distributes apps. Another provision would prevent a covered company from imposing less favorable terms merely because an app gives users access to a third-party app through remote electronic services rather than a download.
That language potentially matters to cloud-delivered products, browser-based services, streaming applications, and hybrid products in which a native shell connects users to substantial functionality delivered over the web. The exact reach would depend on amendments, FTC guidance, and potentially litigation. Still, the bill is not written solely around files downloaded from a storefront.
For PWA-first companies, the strategic signal is more complicated than “open stores are good for the web.” The open web already offers something legislation is trying to recreate for native software: direct distribution through a URL, control over commercial relationships, and the ability to update without submitting every release to a central marketplace. Those advantages remain available now, without waiting for Congress.
More permissive native distribution could nevertheless reduce the cost of maintaining a companion application, a Trusted Web Activity, or another hybrid route into mobile operating systems. It could also make it easier for developers to communicate web pricing and alternative services to users. On the other hand, if native distribution becomes substantially less restrictive, some companies may feel less pressure to adopt a web-first strategy simply to escape store rules. The competitive effect would depend on implementation, not the bill’s title.
Distribution freedom still needs a trust layer
The political fight is already being framed around the familiar trade-off between choice and safety. Supporters argue that dominant stores can use distribution, payments, defaults, and private platform access to disadvantage competitors. A technology-industry coalition opposing the proposal argues that mandatory alternative distribution could increase exposure to fraud, malware, harmful content, and privacy risks.
Neither position should be treated as a complete technical answer. The bill contains exceptions related to intellectual property, sanctions, national security, warranties, and customer support, but it does not prescribe a full security architecture for alternative stores. If distribution opens, trust would depend on the quality of developer verification, signing, permission design, revocation, reputation signals, browser protections, and user-facing explanations.
Web apps already live inside their own version of this tension. HTTPS, origin isolation, browser permissions, sandboxing, and transparent URLs create meaningful safeguards, but they do not guarantee that every service is honest or well built. Open distribution works best when users can verify who is responsible, understand what access an application requests, and leave without losing control of their data.
What changes now—and what IndApp watches next
For users and developers, nothing changes today. Apple, Google, browser vendors, app stores, and web-app platforms operate under the same rules they did before the hearing. The practical value of this moment is as an early signal: U.S. lawmakers are again discussing whether mobile distribution should behave more like an open market and less like a single controlled channel.
IndApp will watch for concrete movement rather than speeches:
- A committee markup, vote, substitute text, or formal amendment.
- Changes to the 100-million-user threshold or the definition of an app.
- Explicit treatment of browsers, browser engines, PWAs, and remote electronic services.
- Security requirements attached to third-party installation and app stores.
- Rules governing external offers, web payments, defaults, and access to operating-system capabilities.
The web-app opportunity is not that Congress might rescue open distribution. The opportunity is that installable web apps already demonstrate what direct software delivery looks like when access begins with a link. If the App Store Freedom Act advances, that model will become even more relevant to the debate over how software should reach users—and who gets to control the route.
Further reading
Recent news
