logo

filips123/PWAsForFirefox

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

View on GitHub ↗Jump to charts ↓Open shareable report →

filips123/PWAsForFirefox has 3k+ stars and 70+ forks on GitHub, is written in JavaScript, and was last pushed on Oct 9, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 1 hour ago
Type:Plugin / ExtensionCategory(s):Browsers & ExtensionsDesktop & System UtilitiesWeb Development
Added to GitGenius on September 22nd, 2026
Created on June 11th, 2021
Open Issues & Pull Requests: 90 (+0)
GitHub issues: Enabled
Number of forks: 73
Total Stargazers: 3,133 (+0)
Total Subscribers: 18 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 24.5 hours
Mean response time: 10.7 days
90th percentile: 17.7 days
Tracked items: 240

Most active contributors

Sign in to see contributor activity.
Sign in

Related repositories by overlapping contributors

Maintainer activity

1 person did triage or write work on this repository in the last 12 months.

Counts unlabeled, assigned, unassigned, milestoned, demilestoned, locked, unlocked over the last 12 months. These are issue and pull request events that require triage or write permission. Commits and code review are not counted. labeled and renamed are excluded because GitHub issue forms record the issue author as the actor. Figures from October 18, 2026. This count is not comparable across projects: each project's automation decides which of these events a person emits. How this is counted.

How this project is maintained

About 7% of issues opened in the past year have never received a reply. 95% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. 68% of issues opened in the past year have been closed, leaving a working backlog. Three people close 80% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 65
New in 7 days: 3
Closed in 7 days: 2
Avg open age: 573 days
Stale 30+ days: 56
Stale 90+ days: 39

Recent activity

Opened in 7 days: 3
Closed in 7 days: 2
Comments in 7 days: 3
Events in 7 days: 12

Top labels

  • bug (168)
  • enhancement (64)
  • question (36)
  • help wanted (27)
  • could not reproduce (13)
  • documentation (3)

Most active issues this week

Sign in to see which issues are moving.
Sign in
Explore full issue details

Detailed Description

PWAs for Firefox is a tool to install, manage and use Progressive Web Apps in Mozilla Firefox.

Firefox natively supports many Progressive Web App APIs but lacks the ability to install PWAs as standalone system applications with an app-like experience. This project solves that limitation by creating a custom modified Firefox runtime that allows websites to be installed as standalone apps. It provides both a command-line tool and a browser extension to handle installation, management, and execution of PWAs. Installed PWAs run in isolated Firefox installations with their own profiles, appearing as separate applications in the system menu and taskbar without tabs or address bars.

The tool suits developers and users who want to run web applications as native-like desktop apps within the Firefox ecosystem. It works with any website that can be installed as a PWA and supports all Firefox extensions and built-in features within the PWA environment. The project explicitly does not plan integration into official Firefox code, as it currently modifies the browser UI at runtime using JavaScript and CSS, an officially unsupported approach that can break with Firefox updates. It also does not support using the same profile for both PWAs and normal browsing, as this could destabilize the main browser installation.

Development activity shows consistent engagement with the codebase through regular updates and maintenance. The project maintains active documentation and provides clear separation between native and extension components, each with its own technical documentation. Community contributions are welcomed, as evidenced by participation in community-driven development initiatives. The maintainer has clearly documented both planned features and intentional non-goals, indicating thoughtful project scope management.