Adobe: “Switch to Chrome” Is Not Acceptable

Adobe Studio tells users to switch to Google Chrome because other browsers are not supported. Browser-specific development undermines interoperability, user choice, and the open web--and can largely be avoided by following established web standards.

1 views

By. Jacob

Jacob Kristensen (Turbulentarius) is a Web Developer based in Denmark. He is currently pursuing a Bachelor's degree in Web Development at Zealand, focusing on learning React and refining his existing skills.

Edited: 2026-08-10 08:43

Seeing a message like “Switch to Chrome desktop — This browser isn't supported yet” in 2026 is unacceptable, especially from a company like Adobe. The web is an interoperable platform built around open standards, not a delivery mechanism for applications tied to whichever browser a developer happens to prefer. Requiring customers to install Google Chrome instead of building a properly compatible web application is a regression toward the browser-specific development practices the industry should have left behind decades ago.

Cross-browser compatibility is not some mysterious or unsolved problem. Modern web development has established standards, specifications, compatibility data, feature detection, progressive enhancement, graceful degradation, fallbacks, and mature testing tools precisely so developers can build applications that work across different browser engines. When implementations differ, developers can detect capabilities and provide alternative implementations where necessary. This is ordinary web development work. A website should target the web platform and the capabilities it requires—not an arbitrary browser brand.

There is also little apparent justification for such a restriction in a comparatively conventional web interface. If Adobe genuinely requires a capability that Firefox, Safari, or another modern browser cannot provide, then Adobe should identify that specific capability and handle its absence appropriately. What it should not do is simply inspect the user's browser, reject it wholesale, and instruct the customer to switch to Chrome. That is not a meaningful compatibility strategy; it is shifting the burden of inadequate cross-browser support from the developer onto the user.

The fact that Studio is described as being in beta does not make this acceptable. Beta software can contain bugs, incomplete functionality, and unfinished interfaces. Cross-browser testing may uncover problems that still need fixing. None of that changes the fundamental responsibility of a web developer to build against established standards and provide reasonable compatibility across modern browsers. “Beta” describes the maturity of a product; it should not be used as an excuse to abandon basic web-development practices.

The situation is particularly objectionable when it affects paying Adobe customers. A customer purchasing access to a web-based service should not also be required to adopt Google's browser simply because Adobe has decided not to support other modern browsers. Browser choice belongs to the user. Customers may choose Firefox, Safari, or another browser for reasons involving privacy, accessibility, operating-system integration, organizational policy, personal preference, or simply because they do not want to use Google Chrome. None of those choices should prevent access to a web application without a genuine and unavoidable technical reason.

Browser-specific development also causes damage beyond the immediate inconvenience. Telling users to “just use Chrome” encourages a browser monoculture in which developers increasingly test against one implementation rather than against web standards. That gives the dominant browser engine disproportionate influence over what effectively constitutes the web and creates exactly the kind of vendor dependence that open standards are intended to prevent. HTML, CSS, ECMAScript, standardized Web APIs, accessibility standards, and decades of accumulated cross-browser development practice exist so that websites can target the web—not Google Chrome.

Adobe is not a small developer experimenting with its first web application. It is one of the world's major software companies, sells professional software and services to paying customers, and has ample engineering resources. It should therefore be held to a considerably higher standard than “please install the browser we tested this with.” If compatibility problems exist, Adobe should fix them. If browser implementations require different approaches, Adobe should implement those approaches. If a particular feature genuinely cannot be supported somewhere, Adobe should detect and isolate that specific limitation rather than blocking the entire application.

The solution is neither novel nor complicated in principle: follow established web standards, use standardized APIs where possible, implement appropriate fallbacks where implementations differ, test across independent browser engines, and fix compatibility problems when they are found. This is basic professional web development. Users—especially paying customers—should not be expected to change browsers to compensate for a company's failure to do it properly.