filips123

filips123/PWAsForFirefox

JavaScript MPL-2.0 Dev Tools Single maintainer risk

A tool to install, manage and use Progressive Web Apps (PWAs) in Mozilla Firefox

3k stars
69 forks
recent
GitHub +5 / week

3k

Stars

69

Forks

87

Open issues

23

Contributors

v2.18.4 23 Jun 2026

AI Analysis

PWAs for Firefox is a tool that enables Mozilla Firefox to install and run Progressive Web Apps as standalone desktop applications with native-like experiences. It serves web developers and end users who want PWA functionality in Firefox, which lacks native PWA installation support compared to Chromium-based browsers. This is a specialized solution for Firefox users seeking PWA capabilities, not a general-purpose browser tool.

Dev Tools Application Discovery value: 6/10
Documentation 8/10
Activity 8/10
Community 7/10
Code quality 5/10

Inferred from signals mentioned in the README (tests, CI, type safety) — not a review of the actual code.

Overall score 7/10

AI's overall editorial judgment — not an average of the bars above, can weigh other factors too.

firefox-extension progressive-web-apps desktop-integration browser-automation web-standards
Actively maintained Well documented Niche/specialized use case Production ready
Deep Analysis · Based on README and public signals
1w ago

Firefox extension enabling PWA installation as standalone apps, filling a native-like experience gap in Mozilla's browser

PWAsForFirefox is a browser extension and CLI tool that allows users to install Progressive Web Apps as standalone applications within Firefox, a capability the browser lacks natively. It works by creating isolated Firefox runtimes with modified UI to mimic native app behavior. Used by developers and power users seeking PWA support on Firefox; adoption appears modest but engaged. The project solves a real gap in Firefox's PWA support strategy but relies on unsupported runtime modifications that risk breakage with browser updates.

Origin

Created June 2021 by Filips (filips123) to address Firefox's lack of native PWA installation capability compared to Chromium browsers. Evolved from a personal tool to a maintained extension distributed via Mozilla's official add-on store, demonstrating sustained effort to keep pace with Firefox versioning and web standards.

Growth

Repository shows steady but slow adoption since inception. Approximately 3,031 GitHub stars and presence in official package repositories (DEB, RPM via packagecloud.io) indicate modest recognition. Recent star gain (3 in 7 days as of July 2026) and continued active maintenance (last push June 23, 2026) suggest stable but non-exponential growth trajectory. Adoption likely constrained by Firefox's overall market share and the niche nature of PWA deployment.

In production

Mozilla add-on store listing with user count badge and ratings visible in README suggests some real-world usage, though specific user numbers not disclosed in excerpt. Sponsorship from packagecloud.io and SignPath Foundation indicates sufficient legitimacy to attract infrastructure support. Presence in Linux package repositories (Repology link shown) suggests adoption among Linux PWA enthusiasts. However, adoption not verified at enterprise scale or mainstream consumer level.

Code analysis
Architecture

Based on README, appears to use a two-part architecture: a native component (CLI tool and isolated Firefox runtime with runtime-modified UI chrome) and a browser extension for installation/management UX. The project explicitly states it modifies Firefox chrome UI using JavaScript and CSS at runtime rather than integrating into official Firefox code. This approach trades quick implementation for technical fragility.

Tests

not documented in README

Maintenance

Last push June 23, 2026 (9 days before evaluation date) indicates active maintenance. Release badge and semantic versioning present. The project maintains presence in multiple package distribution channels (npm, DEB, RPM). However, the README explicitly acknowledges unsupported runtime modifications and notes that changes 'can break with Firefox updates,' suggesting reactive rather than preventative maintenance posture.

Honest verdict

ADOPT IF: You are a Firefox user who needs to install PWAs as standalone applications and accept the tradeoff of runtime UI modification brittleness for that capability. You prioritize Firefox for privacy/customization reasons and don't require chromium-specific APIs. AVOID IF: You need guaranteed stability across Firefox updates, you require Chromium PWA APIs (Filesystem, Bluetooth, USB, NFC), or you expect this to replicate native PWA support (it is a workaround, not integration). MONITOR IF: Mozilla signals native PWA installation support is coming to Firefox, as this project would lose its primary value proposition; conversely, monitor if Firefox market share increases, which could drive adoption.

Independent dimensions

Mainstream potential

3/10

Technical importance

6/10

Adoption evidence

5/10

Risks
  • Runtime UI modification is explicitly unsupported by Mozilla and can break with Firefox updates, making maintenance a reactive burden.
  • Project depends on a single maintainer with limited capacity (acknowledged in README: 'I currently don't have enough knowledge and time' for official integration). Bus factor is high.
  • PWA adoption itself remains niche; this project's growth is capped by the intersection of Firefox users + PWA practitioners, a small subset.
  • Windows APPX/MSIX packaging explicitly not supported; Windows users redirected to Edge, limiting platform reach.
  • No documentation of test coverage or CI/CD pipeline; unclear how update safety is validated before release.
Prediction

Project likely remains a stable niche tool for Firefox-loyal PWA developers. Mainstream adoption unlikely without either (a) Mozilla integrating PWA installation into Firefox, making this obsolete, or (b) PWAs becoming significantly more prevalent as a deployment model. Current trajectory suggests continued incremental maintenance and slow organic growth within the Firefox ecosystem.

0 found this helpful

Newsletter

Get analyses like this every Monday

Free weekly digest of the most interesting open-source discoveries.

Languages

JavaScript
41.4%
Rust
34.6%
HTML
12.2%
Fluent
6.9%
CSS
2%
SCSS
1.4%
Shell
1%
Scheme
0.2%

Information

Language
JavaScript
License
MPL-2.0
Last updated
2w ago
Created
62mo ago
Analyzed with
anthropic/claude-haiku-4-5

Stars over time

Loading…

Contributors over time

Top 100 contributors only — repos with more will plateau at 100.

Loading…

Similar repos

pwa-builder

pwa-builder/PWABuilder

PWABuilder is a comprehensive toolset for creating and packaging Progressive...

3.7k TypeScript Web Dev
GoogleChrome

GoogleChrome/workbox

Workbox is a collection of JavaScript libraries maintained by Chrome's Aurora...

13k JavaScript Web Dev
mozilla

mozilla/web-ext

web-ext is a command-line tool for building, running, testing, and signing...

3.1k JavaScript Dev Tools
maxence-charriere

maxence-charriere/go-app

go-app is a Go package for building progressive web applications (PWAs) that...

8.9k Go Web Dev
BrowserWorks

BrowserWorks/waterfox

Waterfox is an open-source browser built on Firefox's Gecko engine, optimized...

6k JavaScript Security
vs. alternatives
PWABuilder (3,646 stars)

PWABuilder is a platform-agnostic PWA scaffolding and optimization tool by Microsoft; PWAsForFirefox is Firefox-specific runtime installation. PWABuilder helps build PWAs; PWAsForFirefox helps install existing PWAs in Firefox. Complementary rather than competitive.

Workbox (12,964 stars)

Workbox is a Google service-worker library for PWA functionality; PWAsForFirefox is a Firefox app-wrapper. Different layers of the PWA stack; not direct competitors.

web-ext (3,098 stars)

web-ext is Mozilla's official CLI for web extension development; PWAsForFirefox is a specialized extension for PWA installation. web-ext is broader tooling; PWAsForFirefox is use-case-specific.

go-app (8,933 stars)

go-app is a framework for building PWAs in Go; PWAsForFirefox is browser runtime management. Serve different stages of PWA lifecycle.

Edge PWA Support (native browser feature)

Microsoft Edge and Chrome both support native PWA installation; Firefox does not. PWAsForFirefox bridges this gap via workaround. Not a direct replacement but addresses a genuine competitive disadvantage for Firefox users.