I never made a formal decision to quit Firefox.There was no final crash, no single broken website, and no dramatic moment when I exported my bookmarks and swore never to come back. For a while, Firefox was simply my browser. Brave was installed as the backup browser, the one I opened when I wanted to test something, compare behavior, or get around an occasional compatibility issue.Then the roles quietly reversed.At some point, I started opening Brave first. Firefox became the backup. Later, I realized I barely opened it at all.That transition matters because I suspect this is how Firefox loses a lot of users. Most people do not publish an angry goodbye post. They do not uninstall it immediately. They just start using another browser a little more often because it feels faster, works better with a certain website, blocks more junk out of the box, or gets out of their way.Eventually, the backup browser becomes the default.That is exactly what happened to me, and it is a pretty good summary of what has happened to Firefox as a product. It was not killed by one catastrophic decision. It was weakened by years of technical delays, strategic confusion, unnecessary trust failures, abandoned features, badly communicated experiments, and a habit of disappointing the exact users most likely to defend it.The result is brutal.Firefox once had close to one-third of the worldwide browser market, a level of influence reflected in Mozilla’s 2010 State of the Internet report. By August 2026, StatCounter estimated its worldwide desktop share at about 5.3%. Across desktop and mobile combined, its share has generally remained in the low single digits.Calling that a statistical rounding error is obviously a bit dramatic. Firefox still has more than 200 million users according to Mozilla, and that is not a small number of people. Market-share trackers and Mozilla’s own active-client measurements also count different things, so they should not be treated as interchangeable.Still, compared with Chrome’s dominance, Safari’s control of Apple devices, and Edge’s privileged position on Windows, Firefox has become a marginal browser in the broader market.The uncomfortable part is that Mozilla did not merely lose to stronger distribution.It repeatedly made Firefox harder to love.Firefox used to stand for something obviousFirefox originally had a crystal-clear reason to exist.Internet Explorer had become slow, insecure, stagnant, and deeply tied to Microsoft’s control of Windows. Firefox offered a faster, cleaner, more standards-friendly alternative that could be customized in ways Internet Explorer users had never seen.The pitch was simple:It was not controlled by Microsoft.It respected open web standards.It had a huge extension ecosystem.It gave power users control.It worked across operating systems.It felt like software built by people who actually used the web.Installing Firefox was not just a technical choice. For many people, it was a statement about what the web should be.Mozilla won the first browser war because Firefox was meaningfully different.Then Chrome arrived and changed the basis of competition.Google did not just build a browser. It built a distribution machine around a browser. Chrome appeared on Google’s homepage, came preinstalled on Android, integrated tightly with Google accounts, and benefited from the growing popularity of Gmail, YouTube, Google Docs, Maps, and the rest of Google’s ecosystem.Firefox was still competing as a browser.Chrome was competing as the front door to an entire platform.Mozilla needed Firefox to become faster, simpler, more reliable, and more attractive than ever. Instead, it spent years catching up technically while repeatedly weakening the product’s original identity.Chrome attacked Firefox where it was already vulnerableIt is easy to forget how heavy Firefox could feel during parts of the late 2000s and early 2010s.Long-time users remember slow startups, memory problems, UI freezes, tabs dragging down the entire browser, and extensions making everything progressively less stable. Not every user experienced all of those problems, and modern Firefox is a completely different product, but the reputation was real.Chrome arrived with a clean interface and a multi-process architecture. If one tab crashed, the entire browser was less likely to go down with it. The UI felt responsive. JavaScript performance became a headline feature. Chrome made Firefox look old almost overnight.Mozilla knew it had to modernize Firefox, but the response took far too long.The Electrolysis project, usually called e10s, was Mozilla’s effort to turn Firefox into a multi-process browser. Mozilla itself described the work as a “long overdue modernization” in 2016. Internet Explorer had begun adopting a multi-process architecture in 2008, Chrome launched with one that same year, and Safari followed in 2011.Firefox did not begin rolling out its first major multi-process phase to regular users until Firefox 48 in August 2016.That delay was devastating.For years, the public comparison was not between Chrome and the Firefox Mozilla hoped to ship someday. It was between Chrome and the Firefox people had installed on their computers right then. Chrome felt modern while Firefox was rebuilding its foundations behind the scenes.Firefox Quantum finally arrived in November 2017 and was a genuinely impressive release. Mozilla claimed it was more than twice as fast as Firefox had been six months earlier, with significant improvements to responsiveness and memory use.But Firefox Quantum also exposed the core problem with Mozilla’s timing.It was the browser Firefox needed years earlier.By 2017, Chrome was no longer the new browser people were experimenting with. It had become the default browser for a huge portion of the internet. Websites were increasingly tested against Chromium first. Companies had standardized on Chrome. Users had their bookmarks, passwords, history, and Google accounts synced into it.Firefox finally got competitive at the exact moment switching costs had become much higher.Mozilla modernized Firefox by breaking what loyal users lovedThe Firefox 57 transition is probably the clearest example of Mozilla making a technically understandable decision in the most damaging possible way.Legacy Firefox extensions could reach deeply into the browser. They could modify the interface, change tab behavior, access internal systems, and transform Firefox into something almost completely different.That power created serious problems.Legacy extensions could hurt performance, interfere with multi-process Firefox, break after updates, expand the attack surface, and make browser development significantly harder. Mozilla needed a more stable and secure extension model.So Firefox moved to WebExtensions, an API largely designed around the cross-browser extension model already used by Chrome and other browsers.From an engineering perspective, the transition made sense.From a user perspective, Firefox 57 walked into people’s homes and unplugged half their setup.Extensions that had defined Firefox for years suddenly stopped working. Some were eventually ported. Others returned with fewer capabilities. Many disappeared completely because the newer APIs could not reproduce what they had done before.Mozilla had announced the transition and established compatibility milestones, giving developers time to prepare, but that did not change the result for users. When Firefox 57 arrived, legacy extensions simply no longer loaded.The people most affected were not casual users who had installed a coupon extension and forgotten about it. They were Firefox’s power users. These were the people running elaborate tab-management setups, custom interfaces, download tools, privacy extensions, automation systems, and workflows built specifically around Firefox.They were also Mozilla’s unpaid sales team.Power users recommended Firefox to friends, installed it on family computers, defended it in technical discussions, reported bugs, developed extensions, wrote tutorials, and helped other users configure it.Mozilla traded the unique power of Firefox’s extension ecosystem for a safer and more maintainable model that looked increasingly similar to Chrome’s.Again, the technical rationale was real. Firefox could not preserve every internal API forever while also shipping a secure multi-process browser.The strategic cost was also real.Firefox lost part of what made it Firefox.Firefox became more like Chrome without gaining Chrome’s advantagesThis is the part I think Mozilla never fully solved.If Firefox was going to become easier to maintain by adopting a more Chrome-compatible extension system and simplifying parts of the interface, it needed to gain something equally valuable in return.Instead, it moved closer to the mainstream browser model while keeping all of its competitive disadvantages.Firefox did not gain:Android’s default-browser positionWindows integrationApple’s hardware ecosystemGoogle’s service ecosystemChromium’s dominant developer mindshareChrome Web Store scaleOEM installation deals at Chrome’s levelEnterprise policies backed by a major operating-system vendorFirefox gave up some of its uniqueness without becoming the easiest browser to adopt.That is a terrible middle position.Casual users had little reason to leave Chrome, Safari, or Edge. Power users had fewer reasons to remain loyal to Firefox. Mozilla was slowly sanding down the features that differentiated Firefox while competing against companies that controlled operating systems, search engines, cloud platforms, advertising networks, and hardware ecosystems.Mozilla kept redesigning the browser while users wanted consistencyBrowsers are not social media apps. Most people do not want them visually reinvented every few years.A browser is infrastructure. It is closer to an operating system shell or a code editor. Once users develop muscle memory, unnecessary interface changes become a tax.Firefox has gone through multiple major visual redesigns:Australis in 2014Photon with Firefox Quantum in 2017Proton in 2021Additional sidebar, tab, profile, and AI-related redesign work in later releasesEach redesign was presented as cleaner, simpler, more modern, or more focused. That language is standard for any design launch. The practical result was that long-time users repeatedly had to adjust to changed menus, spacing, tab appearance, removed icons, relocated actions, and new defaults.The Proton redesign in 2021 was particularly irritating for users who valued information density.Firefox introduced large floating tabs and more generous spacing while hiding its compact-density option behind an about:config preference and labeling it unsupported. For a browser with a disproportionately technical audience, reducing information density felt completely backward.The design itself was not objectively terrible. Some people liked it. That is not really the point.The point is that Mozilla was spending goodwill on cosmetic churn when its users were asking for stability, compatibility, performance, and features that competitors already had.When your browser has lost most of its market share, changing the shape of the tabs is not a comeback strategy.Firefox removed tab groups, then celebrated bringing them back nine years laterNothing captures Mozilla’s strange product instincts better than the history of tab groups.Firefox introduced Panorama, a visual tab-grouping system, years before tab organization became a major browser trend. It was unusual and powerful, especially for users who kept large browsing sessions open.Mozilla removed Panorama from Firefox in 2016, officially describing it as a rarely used feature. Users were directed toward extensions as replacements.Then Firefox 57 killed the legacy extension architecture that had allowed extensions to integrate deeply into the browser.That sequence matters:Mozilla removed a native power-user feature.Users were told extensions could replace it.Mozilla replaced the extension system with a more restricted one.Firefox spent years without a proper native equivalent.Tab groups finally returned as a built-in feature in 2025.Mozilla’s 2025 announcement about the return of tab groups described them as the most requested feature in the history of Mozilla Connect.That should not only be interpreted as evidence that Mozilla listened.It is also evidence that users had been asking for years.Firefox originally had an ambitious approach to tab organization, removed it, watched competitors normalize tab groups, and then reintroduced a more conventional implementation almost a decade later.That is not leadership. It is recovering from your own product decision.Basic browser features kept arriving years lateFirefox has often been technically innovative under the hood, but the everyday product has regularly lagged behind competitors in visible features.Native vertical tabs arrived in 2025 after years of requests, extensions, and custom CSS workarounds. Microsoft Edge had already made vertical tabs a mainstream feature.Modern profile management also received a proper user-friendly rollout in late 2025. Firefox technically had profiles for years through about:profiles and command-line options, but that was not comparable to the obvious profile switchers offered by Chromium browsers.Tab groups returned in 2025.Desktop web-app support returned in a limited form for Windows starting with Firefox 143. As of 2026, the official feature remains Windows-specific, while Chromium browsers have treated installable web apps as a regular desktop feature for years.This pattern hurts Firefox because users do not evaluate browsers based on architectural purity. They notice that a feature exists in one browser and does not exist in another.It does not matter that advanced users can reproduce half of those features with extensions, CSS hacks, hidden preferences, containers, separate profiles, or shell scripts.The mainstream user sees a missing button.The developer sees another support request.The power user sees another feature Mozilla might finally ship five years later.Firefox’s mobile strategy never recoveredDesktop Firefox is niche. Mobile Firefox is even more marginal.That is a massive problem because mobile browsing accounts for such a large percentage of global web traffic. A browser cannot be a mainstream global product while barely participating in the mobile market.On Android, Chrome has an overwhelming distribution advantage. It comes preinstalled on most devices, connects to a Google account during setup, and is integrated into an operating system controlled by Google.Mozilla cannot magically fix that.Still, Firefox has made its own mobile mistakes.The transition to the rebuilt Firefox for Android, code-named Fenix, created a faster and more modern foundation using GeckoView. It was important work, but the migration initially supported only a limited selection of recommended extensions.Existing users who had chosen Firefox Android specifically for its extension support saw unsupported add-ons disabled. Mozilla did not restore broader extension support on stable Firefox for Android until late 2023.Once again, the engineering explanation was reasonable. Mozilla wanted extensions to be secure, reliable, and suitable for mobile screens.Once again, the user experience was simple: features disappeared.Firefox’s strongest mobile differentiator was extension support, particularly content blockers and privacy tools. Restricting that ecosystem during a major migration weakened one of the few reasons Android users had to choose Firefox over Chrome.On iOS, the situation is even harder because Apple historically required third-party browsers to use WebKit. Firefox on iPhone could offer Firefox Sync, interface choices, and Mozilla services, but it could not bring Gecko to the platform in the same way it could on desktop and Android.Mozilla tried to fight on mobile by launching Firefox OS, but that became another strategic detour.Firefox OS was a brave idea at the worst possible timeFirefox OS was not a stupid concept.Mozilla correctly understood that control of the mobile operating system would shape the future of the web. Android and iOS were turning open websites into secondary citizens behind native app stores, proprietary APIs, and platform rules.Mozilla wanted a mobile operating system where web technologies were the application platform.That aligned perfectly with its mission.The problem was execution and timing.Firefox OS entered a market where Android and iOS already had rapidly growing app ecosystems, major hardware partners, developer attention, and huge corporate backing. Mozilla targeted affordable devices and carrier partnerships, but low price alone could not compensate for the lack of popular apps.Users did not buy smartphones based on the philosophical beauty of HTML5 applications. They wanted WhatsApp, Instagram, banking apps, games, maps, media services, and everything their friends were already using.Mozilla eventually admitted that it had failed to create a compelling, differentiated value proposition and had not built a complete ecosystem. Smartphone development stopped after Firefox OS 2.6, with the remaining technology redirected toward connected devices and televisions.I understand why Mozilla tried it. A future dominated by Android and iOS was clearly dangerous for the open web.But there was still an opportunity cost.While Chrome was taking over desktop browsing and Google was securing the mobile market, Mozilla spent time, management attention, community energy, and engineering resources trying to build an operating system.Firefox needed ruthless focus.Mozilla chose a moonshot.Product sprawl became a habitFirefox OS was not the last time Mozilla looked beyond the browser for growth.Over the years, Mozilla has been connected to or invested in products and initiatives including:PocketFirefox RelayMozilla VPNFirefox MonitorMozilla HubsMozilla SocialFakespotMozilla.aiMozilla VenturesAdvertising technologyAI-powered browser featuresConnected-device experimentsSome of these products are useful. Product diversification is also financially understandable because Mozilla is dangerously dependent on search revenue.The problem is that Mozilla repeatedly looked like an organization searching for a business model while its flagship product kept shrinking.Pocket is a great example.Mozilla integrated Pocket directly into Firefox in 2015 and acquired the company in 2017. Some Firefox users disliked having a third-party service inserted into the browser, especially one that was initially not fully aligned with the open, built-in nature they expected from Firefox.Pocket later became deeply connected to Firefox’s New Tab recommendations and Mozilla accounts. In 2023, Pocket users were required to transition to Firefox accounts to continue signing in.Then Mozilla shut Pocket down on July 8, 2025.Fakespot followed an even faster version of the same pattern. Mozilla acquired it in 2023, integrated its Review Checker into Firefox, and shut the service down in 2025.Mozilla’s explanation was that the products no longer fit a sustainable model and resources would be redirected toward Firefox and newer features.That may have been the correct decision by 2025.It still raises the obvious question: why were these acquisitions and integrations the priority in the first place?Users were watching Mozilla acquire, integrate, promote, restructure, and eventually discontinue products while basic Firefox features remained missing or arrived years late.The trust failures were often worse than the features themselvesFirefox’s strongest asset has never been raw market power.It has been trust.Mozilla cannot outspend Google, Microsoft, or Apple. It cannot preinstall Firefox across billions of devices. It cannot tie the browser to the world’s largest search engine, desktop operating system, mobile platform, or premium hardware ecosystem.What it can do is be the company users trust more than those competitors.That means Mozilla has less room for avoidable mistakes.Unfortunately, it has repeatedly made decisions that looked especially bad coming from a privacy-focused organization.The Mr. Robot extension was an unbelievable self-inflicted woundIn December 2017, Mozilla automatically installed an extension called Looking Glass in Firefox as part of a promotional collaboration with the TV show Mr. Robot.The extension was installed in a disabled state and did not collect user data. Users still saw a mysterious add-on with a cryptic description appear in their browser without choosing to install it.That is exactly the kind of behavior Firefox users expect from malware.Mozilla later apologized and admitted that it should have given users the choice to install the extension. Its Looking Glass retrospective went even further, acknowledging that the extension had been deliberately given a misleading name to preserve the surprise of the promotion.Think about how absurd that is.Mozilla had spent years teaching people to watch for suspicious extensions. Then it used Firefox’s internal experiment infrastructure to silently place a mysteriously named promotional add-on into users’ browsers.The extension did not need to steal data to be a trust failure.Mozilla proved that it was willing to use privileged browser access for a marketing stunt.That is the opposite of what Firefox’s relationship with its users was supposed to mean.The Cliqz experiment was another “what were they thinking?” momentAlso in 2017, Mozilla ran a Firefox experiment in Germany using technology from Cliqz, a company in which Mozilla had invested.Less than one percent of users downloading Firefox from Mozilla’s main download page in Germany received a version with Cliqz recommendations enabled by default.That version also included Cliqz’s data-collection system. Mozilla’s own announcement stated that browsing activity, including visited URLs, would be sent to Cliqz servers. Mozilla explained that Cliqz attempted to remove sensitive information and discarded users’ IP addresses after collection.The privacy engineering may have been thoughtful.The product decision was still terrible.Firefox users should not have to wonder whether the browser they downloaded from Mozilla sends visited URLs to a company involved in a recommendation experiment.Mozilla described transparency as part of its “No Surprises” privacy principle, but publishing a blog post does not magically make a surprising default unsurprising.Most users do not monitor Mozilla’s press center before installing a browser.Sponsored content slowly changed Firefox’s personalityMozilla needs revenue. Firefox is free, browser development is extremely expensive, and Mozilla cannot fund an independent engine using goodwill alone.I do not expect Firefox to survive without commercial partnerships.I do expect Mozilla to understand that ads inside Firefox are not emotionally neutral for its audience.Mozilla experimented with sponsored Directory Tiles, later ended that advertising experiment, integrated Pocket recommendations into the New Tab page, introduced sponsored suggestions in the address bar, and continued developing privacy-preserving advertising systems.Each individual feature can be defended.Sponsored tiles can be disabled. Sponsored suggestions are supposed to be relevant. Mozilla’s newer systems use privacy-preserving techniques. The current Firefox Privacy Notice explains what data is processed and gives users controls.The problem is cumulative.Firefox increasingly behaves like a product looking for surfaces to monetize:The New Tab pageRecommended storiesSponsored tilesAddress-bar suggestionsSearch partnershipsAdvertising measurementPrivacy-preserving ad infrastructureMozilla argues that advertising is part of the web and that it can build a less invasive version of it.That is a legitimate position.It is also not why most people install Firefox.People do not leave Chrome because they are excited to experience Mozilla’s interpretation of advertising. They leave Chrome because they want less Google, less tracking, less manipulation, and fewer commercial systems inserted into their browser.Mozilla keeps trying to explain why its advertising is better.Its users keep asking why their browser company is becoming an advertising company at all.Firefox Suggest was technically clever and strategically tone-deafFirefox Suggest added contextual and sponsored suggestions to the address bar.The initial 2021 version was presented with controls for users who wanted a richer suggestion experience. Mozilla explained that enabling the more advanced contextual suggestions could involve sending what users typed, city-level location data, and interaction information to Mozilla.By 2026, Mozilla had developed a more privacy-preserving architecture for real-time suggestions in the United States. Queries could be sent through Oblivious HTTP, separating the query from the user’s IP address so no single party received both.That is good privacy engineering.It does not completely solve the trust problem.The address bar is one of the most sensitive surfaces in a browser. People type URLs, searches, fragments of private thoughts, internal company addresses, medical questions, and all kinds of accidental information into it.Mozilla should treat any feature involving address-bar input as radioactive.Even if the data is encrypted, proxied, de-identified, minimized, and covered by a detailed privacy notice, the default should be obvious and conservative. The burden should not be on users to understand Oblivious HTTP before deciding whether their address-bar input is handled appropriately.A privacy feature that requires five paragraphs of architecture explanation has already lost most normal users.The privacy-preserving attribution controversy was mostly a communication failureFirefox 128 introduced an experimental Privacy-Preserving Attribution API.The idea was to help websites measure whether ads led to conversions without using traditional cross-site tracking. Mozilla limited the experiment to an origin trial and intended to test it only on Mozilla-controlled websites.The setting appeared under “Website Advertising Preferences,” which immediately caused backlash because it was enabled as part of the browser’s default configuration for eligible users.Privacy group noyb filed a complaint, arguing that Mozilla had activated the system without proper consent.There is an important detail that many angry headlines missed: Mozilla later stated that the experiment was never activated, was limited in scope, and was eventually removed.So no, Firefox did not suddenly become conventional ad-tracking spyware in version 128.But Mozilla still created the controversy by failing to understand its audience.If your privacy-focused browser adds something called “Allow websites to perform privacy-preserving ad measurement,” and the visible setting is checked by default, people are going to be suspicious.The phrase “privacy-preserving advertising” might sound reassuring inside Mozilla. To many Firefox users, it sounds like “tracking, but please trust us.”When trust is the product, perception is not a secondary concern.The 2025 Terms of Use backlash was completely predictableIn February 2025, Mozilla introduced formal Terms of Use for Firefox and updated the browser’s privacy notice.The original wording said users granted Mozilla a nonexclusive, royalty-free, worldwide license to use information uploaded or input through Firefox to help users navigate, experience, and interact with online content.Mozilla explained that it needed limited rights to process information required for browser functionality and did not claim ownership over user data.Users still hated the wording.And honestly, how could Mozilla not see that coming?A privacy-focused browser company introduced a broad license covering information users input through the browser. Even if lawyers considered the language standard, Firefox users were never going to interpret it casually.Mozilla revised the wording within days, clarifying that the license was limited to operating Firefox and doing what users requested.The quick revision was good.The need for it showed that Mozilla had once again underestimated how little ambiguity its audience would tolerate around user data.The Terms of Use incident was not proof that Mozilla intended to steal browsing data or train AI models on everything typed into Firefox.It was proof that Mozilla’s leadership and legal communication had become disconnected from the expectations attached to the Firefox brand.Buying an ad-tech company made the identity crisis worseIn 2024, Mozilla acquired Anonym, a company building privacy-preserving digital advertising infrastructure.Mozilla’s position is that advertising will continue to fund the web, so somebody needs to build advertising systems that do not depend on mass surveillance. Anonym’s systems are designed to reduce data exposure through encryption, aggregation, trusted execution environments, and differential privacy.Again, the technical argument is not ridiculous.The brand argument is much harder.Mozilla is financially dependent on search advertising, places sponsored content in Firefox, experiments with ad measurement, and now owns advertising infrastructure.At some point, “we are fixing advertising” starts to look uncomfortably similar to “advertising is becoming our business.”The average user does not evaluate the cryptographic privacy properties of ad infrastructure. The average user sees a company that sells itself as the alternative to surveillance capitalism getting deeper into advertising.Mozilla may believe it can reform the industry from within.Its users may reasonably conclude that the industry is reforming Mozilla.Mozilla’s dependence on Google is the giant contradiction behind everythingMozilla’s finances make the Firefox story much more complicated.According to Mozilla’s audited 2024 financial statements, Mozilla Foundation and its subsidiaries reported about USD 680.4 million in total revenue and support. Roughly USD 498.2 million came from royalties, primarily generated through search-engine placement in Firefox.The same financial statements said that approximately 86% of Mozilla’s contract revenue came from a single customer in 2024.The customer is not named in that particular note, but court records in the Google search case discuss Mozilla’s agreement with Google, and Google remains Firefox’s default search engine in the United States.So Firefox, one of the last major alternatives to Google’s browser engine, depends heavily on money generated by making Google Search the default.That does not mean Google controls Firefox development. It does not mean Mozilla employees are secretly taking orders from Chrome. It does not prove that Google pays Mozilla purely to create the appearance of browser competition.But the incentives are uncomfortable.Google benefits when Firefox sends users to Google Search. Mozilla benefits when Firefox users generate search revenue. Mozilla needs the money to develop Gecko and Firefox, which compete with Google’s Chromium and Chrome.Firefox is fighting Google with money earned from Google.That is not a stable independence model. It is a hostage situation with excellent accounting.Mozilla knows this, which is why it keeps trying to diversify into subscriptions, VPNs, advertising, AI, investments, and new products.Unfortunately, those diversification attempts have also helped blur Firefox’s identity and distract Mozilla from the product that generates most of its leverage.The Yahoo switch showed how much defaults matterIn 2014, Mozilla replaced Google with Yahoo as the default Firefox search engine in the United States.The decision was part of a broader regional search strategy. It also gave Mozilla a financially attractive alternative to Google.Google later regained the default position.What makes this episode interesting is how clearly it demonstrated the power of defaults. Evidence discussed in Google’s antitrust case showed that changing Firefox’s default search engine significantly affected Google search traffic from Firefox users. Mozilla’s response to proposed Google antitrust remedies also emphasized how deeply search agreements and defaults affect independent browsers.Most users do not change defaults.This is exactly why Firefox has such a hard time growing. Chrome is tied to Android and Google’s services. Edge is built into Windows. Safari is built into Apple devices. Firefox usually requires a deliberate download, installation, data import, account setup, and default-browser change.Firefox has to be chosen.Its competitors mostly have to be accepted.Mozilla cannot control that structural disadvantage, but it can make sure Firefox is worth the effort. Too often, it has done the opposite by creating friction for the people who already made that choice.The executive-pay and layoff optics were awfulMozilla announced layoffs affecting approximately 250 employees in August 2020, around a quarter of its workforce at the time.Mozilla explained that pandemic-related economic conditions had made its previous financial plan unworkable. The restructuring was supposed to help the organization focus on sustainable products and long-term stability.Layoffs are sometimes necessary. Browser engineering is expensive, and Mozilla’s finances are unusual.But the layoffs became much harder to defend emotionally when Mozilla Foundation’s public tax filings showed extremely high executive compensation.Mozilla Foundation filings reported millions in annual compensation for Mitchell Baker from a related organization, including approximately USD 6.9 million for 2022.People can debate whether that compensation reflected multiple responsibilities, long-term incentives, bonuses, prior commitments, or market-based executive pay.Users and laid-off employees see a simpler picture:Firefox was losing market share.Mozilla was cutting staff.Product initiatives were being closed or restructured.Executive compensation was increasing into the millions.That is a leadership optics disaster.In 2024, Mozilla Foundation also laid off roughly 30% of its staff and eliminated parts of its previous organizational structure. It is important to distinguish Mozilla Foundation from Mozilla Corporation, which directly develops Firefox, but users rarely care about the corporate diagram.They see Mozilla.When an organization says resources are limited while paying executives millions and repeatedly funding projects that later disappear, people naturally question its priorities.Firefox’s compatibility problem became a self-reinforcing loopFirefox is not simply “bad at web standards.”That criticism is too simplistic.Gecko has introduced important technologies, Firefox has often pushed standards forward, and Mozilla sometimes refuses to implement APIs because it has legitimate privacy or security objections.The real problem is market power.Developers test where the users are. Most users are on Chromium-based browsers or Safari. That means Chromium receives more production testing, more bug reports, more workarounds, and more attention from large web companies.A typical web team often works like this:Build the feature in Chrome.Check it in Safari.Maybe test it in Firefox before release.Fix Firefox only if the problem is obvious or enough users complain.That is bad development practice, but it is economic reality.Once Firefox’s market share falls, companies invest less in Firefox testing. Reduced testing produces more Firefox-specific bugs. Those bugs make users believe Firefox is incompatible. Users switch to Chrome, Edge, or Brave. Firefox’s share falls further, giving companies even less reason to test it.That loop is incredibly difficult to break.Google services have also faced repeated complaints from Firefox users involving performance, unsupported experiences, or browser-specific behavior. Sometimes the problem is a genuine Gecko bug. Sometimes it is poor browser detection. Sometimes the site is optimized around Chromium behavior rather than standards.Users do not care whose fault it is.They click a button in Firefox, it fails, and then it works in Brave.Guess which browser they open next time?“Works best in Chrome” is the new “Best viewed in Internet Explorer”Firefox originally helped defeat a web where developers built websites around Internet Explorer-specific behavior.Now Chromium is becoming the new default implementation of the web.Chrome, Edge, Brave, Opera, Vivaldi, Arc, and many smaller browsers all rely on Chromium or its Blink rendering engine. They may have different privacy models and interfaces, but websites generally see them as members of the same technical family.Firefox stands outside that family with Gecko.That makes Firefox incredibly important.It also makes Firefox inconvenient.Every time I use Brave instead of Firefox, I get excellent compatibility while still avoiding some of Chrome’s worst defaults. Brave blocks ads and trackers out of the box, supports Chrome extensions, and benefits from the enormous amount of testing websites already receive on Chromium.From a practical perspective, that combination is difficult for Firefox to beat.From an ecosystem perspective, it is worrying.Brave competes with Chrome as a product, but it does not create a fully independent browser-engine ecosystem. My switch from Firefox to Brave reduced Google’s control over some parts of my browsing experience, but it also increased the dominance of Chromium’s underlying technology.That contradiction is real.I still made the switch.Users choose the browser that works for them today, not the browser architecture that might produce a healthier web ten years from now.Brave did not need to be perfect. It only needed to be easierI do not think Brave is perfect.It has crypto-related features many users do not care about. It has made its own controversial decisions. Some people dislike its business model, referral history, rewards system, or promotional features. It is still built on Chromium.But Brave understood something Mozilla repeatedly forgot: the default experience matters more than the theoretical configuration.After installing Brave, users immediately get aggressive tracker and ad blocking. Most websites work because they already work in Chrome. Chrome extensions are available. The interface is familiar. Users can turn off much of the extra Brave-specific functionality if they do not want it.Firefox can also be configured into an excellent privacy browser.That word “configured” is the problem.Firefox has Enhanced Tracking Protection, Total Cookie Protection, containers, strong extension support, DNS-over-HTTPS options, fingerprinting protections, and many advanced preferences.But too much of Firefox’s appeal is hidden behind knowledge.You need to know which settings to change, which extensions to install, which about:config values matter, which privacy protections might break websites, and which pieces of Firefox’s New Tab experience to disable.Brave’s pitch is visible immediately.Firefox’s pitch often requires a tutorial.Firefox keeps chasing trends instead of owning its identityMozilla’s recent AI strategy repeats a familiar pattern.Firefox began experimenting with chatbot access in the sidebar, local AI for tab-group suggestions, summarization tools, AI search partnerships, and plans for deeper AI integration.Some of this work is technically interesting. Local AI for tab organization is far more privacy-friendly than sending every tab title to a cloud service. Giving users a choice of AI providers is better than locking them into one vendor.But Firefox users are not begging Mozilla to turn the browser into another AI platform.Many of them chose Firefox specifically because they were tired of large technology companies inserting fashionable features into every product.When Mozilla talks about becoming an AI browser while still catching up on ordinary browser features, users hear the same old story:“Your long-standing requests are difficult, but we found resources for the current industry trend.”To Mozilla’s credit, it listened to some of the backlash. Firefox 148, released in February 2026, added centralized AI controls, including a single switch to block current and future generative AI features. Mozilla reinforced that approach in September 2026, presenting AI integration as a user choice rather than an unavoidable direction.That is a good correction.The fact that Firefox needed an “AI kill switch” to reassure its own audience says a lot about how far Mozilla’s priorities had drifted from what those users wanted.Mozilla often confuses technical privacy with emotional trustThis is probably the most important distinction in the entire Firefox story.Mozilla engineers frequently build systems with real privacy protections:Local processingData minimizationAggregationEncryptionOblivious HTTPDifferential privacyDistributed aggregationPartitioned cookiesAnti-fingerprinting systemsBlocking APIs preserved for extensionsThat work matters.But users do not experience privacy as a white paper. They experience it as a relationship.If a browser silently installs a promotional extension, users feel betrayed even if the extension collects nothing.If a browser sends visited URLs to an experiment partner, users feel tracked even if sensitive information is filtered out.If sponsored suggestions appear in the address bar, users feel monetized even if queries pass through a privacy-preserving proxy.If an advertising API is enabled for an origin trial, users feel opted in even if the trial never actually runs.If Terms of Use request a broad license, users feel ownership slipping away even if Mozilla’s lawyers intended something narrow.Mozilla keeps explaining why its systems are technically safer than the alternatives.Its users keep saying, “I did not ask for this.”Both sides may be factually correct. Only one side gets to decide whether Firefox remains installed.Mozilla underestimated the value of its difficult usersPower users can be annoying.They complain about every spacing change. They depend on obscure features. They customize unsupported CSS. They file bugs for workflows used by a tiny percentage of the market. They hate simplified menus. They resist telemetry. They demand explanations for every network request.They are also the reason Firefox survived as long as it did.Mozilla sometimes treated low usage as proof that a feature could be removed. That approach ignores the difference between user count and user value.A feature used by 1% of Firefox users might be irrelevant.Or it might be the exact feature keeping the most influential 1% from leaving.The user with 40 extensions, a custom userChrome.css, containers, vertical tabs, unusual proxy settings, and a carefully organized profile is not an average user. That person might also be the system administrator who installs browsers for an entire company or the developer who recommends Firefox to thousands of readers.Firefox did not need to become a museum where nothing could ever change.It did need to understand that its demanding users were part of its distribution strategy.Mozilla could never match Google’s marketing power.It had something Google could not easily buy: genuine loyalty.Then it repeatedly converted that loyalty into resentment.Firefox is now trapped between two audiencesMozilla appears to want Firefox to satisfy two very different groups.The first group wants a simple mainstream browser:Clean interfaceEasy onboardingSyncProfilesTab groupsAI assistanceContent recommendationsBuilt-in servicesMinimal configurationThe second group wants a powerful independent browser:Deep customizationMinimal commercial contentStrong privacy defaultsFull extension capabilitiesTransparent networkingAdvanced tab controlPredictable UINo AI unless explicitly requestedNo sponsored suggestionsNo hidden experimentsTrying to serve both groups is not impossible.The problem is that Mozilla often disappoints the second group while failing to attract the first.Mainstream users still have no compelling reason to leave Chrome, Safari, or Edge. Firefox does not have superior distribution, ecosystem integration, or universally better website compatibility.Power users, meanwhile, see Mozilla simplifying interfaces, experimenting with ads, restricting old extension capabilities, and introducing trendy features they did not request.Firefox becomes too unusual for mainstream users and not unusual enough for enthusiasts.Brave found a cleaner position: familiar Chromium compatibility with aggressive blocking enabled by default.Firefox’s position is harder to explain.“Use Firefox because an independent browser engine is important to the future of the open web” may be true, but it is not a strong consumer pitch.It sounds like homework.Firefox still does several things betterDespite everything I have criticized, I do not want Firefox to disappear.Firefox remains one of the only serious cross-platform browsers with an engine independent of Chromium and WebKit. Gecko’s survival matters because web standards should not be decided by a single implementation.Firefox also made the right decision around Manifest V3.Google’s version of Manifest V3 removes the old blocking webRequest behavior that powerful content blockers relied on. Chrome has phased out Manifest V2 extensions, affecting the original version of uBlock Origin.Mozilla implemented Manifest V3 compatibility while continuing to support blocking webRequest and Manifest V2 for the foreseeable future.That means Firefox can still run the full version of uBlock Origin rather than forcing users onto the more limited uBlock Origin Lite available for Chromium’s restricted model.This is exactly what Firefox should be doing.Do not copy Chrome where Chrome is making the browser worse.Firefox also has excellent features such as:Multi-Account ContainersTotal Cookie ProtectionEnhanced Tracking ProtectionStrong anti-fingerprinting optionsBroad Android extension supportLocal translationOpen-source developmentExtensive enterprise configurationAn independent rendering engineModern Firefox is fast. It is secure. It is technically capable. On many systems and workloads, it performs extremely well.The tragedy is not that Firefox is a bad browser.The tragedy is that Firefox became a good browser after millions of people had stopped caring.Firefox’s biggest enemy was not Chrome. It was erosionChrome obviously caused enormous damage to Firefox.Google had superior distribution, more money, control of Android, ownership of major web services, and the ability to promote Chrome directly to billions of users.Apple locked Safari into its ecosystem.Microsoft turned Edge into a Chromium browser and aggressively pushed it through Windows.Those advantages are impossible to ignore.But external competition does not explain the whole decline.Chrome did not force Mozilla to remove Panorama.Chrome did not force Mozilla to break legacy extensions on a fixed deadline without complete replacements for advanced use cases.Chrome did not force Mozilla to hide compact mode.Chrome did not install Looking Glass in Firefox.Chrome did not run the Cliqz experiment.Chrome did not write Firefox’s 2025 Terms of Use.Chrome did not acquire Pocket and Fakespot before shutting them down.Chrome did not choose Mozilla’s executive compensation.Chrome did not decide how Mozilla communicated advertising experiments.Chrome created the pressure.Mozilla decided how to respond to it.Too often, that response consumed the trust Firefox needed to survive.What Mozilla should have done, and should still doFirefox probably cannot return to a 30% global market share. The distribution landscape is too different now.But Mozilla can stop treating decline as inevitable.Make Firefox the unquestioned priorityFirefox should not feel like one product inside a portfolio of experiments.It is Mozilla’s source of relevance, distribution, revenue, credibility, and influence over web standards. Without Firefox, Mozilla becomes another technology-policy organization with a collection of side projects.Every major investment should answer one question:Does this make Firefox more useful, more trusted, or more difficult to replace?If the answer is no, it should face an extremely high bar for funding.Stop spending trust on opt-out experimentsFeatures involving advertising, sponsored content, AI, query processing, data collection, or third-party services should be easy to understand and easy to reject.Where practical, controversial integrations should be opt-in.Not hidden behind a preference.Not explained only in a blog post.Not technically disabled while the visible checkbox is enabled.Not launched first and clarified after the backlash.Firefox cannot afford another Looking Glass moment.Turn power users back into advocatesMozilla should provide stable, documented customization hooks rather than relying on unsupported CSS and hidden preferences.Firefox should be the browser for people who want control.That does not mean restoring the unsafe extension model from 2016. It means designing safe modern APIs for the kinds of customization users clearly want.Mozilla should see advanced users as partners, not edge cases.Beat Chromium on defaults, not only possibilitiesFirefox already has many powerful privacy capabilities.Those advantages need to be visible immediately after installation.A user should not need a privacy guide to understand why Firefox is better. The first-run experience should clearly demonstrate tracking protection, containers, extension freedom, import tools, and customization without becoming an exhausting setup wizard.Obsess over compatibilityMozilla cannot control which browser developers test first.It can make Firefox compatibility failures expensive for itself to ignore.That means investing heavily in web compatibility, reporting broken sites clearly, working with major services, improving developer tools, and shipping practical interoperability fixes quickly.Moral superiority does not fix a broken checkout button.Ship boring features before fashionable onesProfiles, tab groups, vertical tabs, web apps, split views, session management, media support, password workflows, and mobile parity are not exciting conference topics.They are why people keep using a browser.Firefox does not need to predict every trend. It needs to stop arriving years late to obvious ones.Be honest about moneyMozilla should say clearly:Search agreements fund Firefox.Ads and sponsored content generate revenue.Browser-engine development is expensive.Complete financial independence from large technology companies does not currently exist.Diversification may involve paid products and commercial partnerships.Users can handle uncomfortable truth better than carefully polished mission language that avoids the obvious contradiction.Mozilla should also make it easier for people to pay directly for Firefox-related services without turning the browser into an advertising surface.Would I switch back?I would not rule it out.Firefox still has technical and philosophical advantages Brave cannot reproduce while remaining Chromium-based. Full uBlock Origin support is a meaningful advantage. Gecko matters. Containers are excellent. Mozilla’s privacy work is often genuinely impressive.But switching back cannot feel like charity.I do not want to use a browser because I feel personally responsible for preserving engine diversity. I want to use it because it is the best tool for how I browse.That is the standard Firefox must meet.Brave started as my helper browser because it was useful when Firefox was not. Over time, those exceptions became routine. The routine became a habit, and the habit became my default.Firefox did not lose me with one terrible release.It lost me one small inconvenience at a time.One site that worked better in Chromium.One feature that arrived late.One redesign I did not need.One removed capability.One questionable experiment.One Mozilla announcement that seemed focused on everything except making Firefox impossible to replace.That is how a browser with hundreds of millions of users ends up feeling invisible.Not with an explosion.With attrition.Firefox may survive, but survival is not the same as relevanceFirefox is not dead.Mozilla still has significant financial resources, more than 200 million Firefox users by its own measurement, an experienced engineering organization, and one of the world’s most important independent browser engines.But Firefox has moved from shaping mainstream browser behavior to defending its continued existence.That should terrify anyone who cares about the open web.If Gecko disappears, Chromium will not merely have more users. It will have even more power to define which APIs matter, how browser extensions work, how advertising systems operate, and which implementation effectively becomes the web standard.I want Firefox to succeed for that reason.I just do not think users owe Mozilla loyalty because the alternative is scary.Mozilla has to earn that loyalty again.It has to stop behaving as though Firefox’s mission makes product mistakes less important. The mission makes those mistakes more important because Firefox has fewer advantages to fall back on.Google has distribution.Apple has hardware.Microsoft has Windows.Brave has Chromium compatibility and aggressive defaults.Firefox had trust, customization, independence, and a community willing to fight for it.Mozilla spent years weakening three of those four.The final one, independence, may keep Firefox alive.It will not automatically make people use it.