Where to Get Help with PWAsForFirefox Problems

Updated

If you run into trouble installing or using PWAsForFirefox, start with the project's help section, and in particular its FAQ page. The site points to the FAQ as the first place to check for setup and usage problems, with the user guide and repository README as supporting references for more detail.

Help resources the project points to

The PWAsForFirefox site lists several places to look when something goes wrong:

  • Help section — the site's stated first stop for problems setting up or using the project, and for other questions about it.
  • FAQ page — called out specifically within the help section for common setup and usage questions.
  • User guide and related pages — the site directs you here for detailed usage instructions.
  • Repository README — described as the place for more details about the project.
  • About section — also offered for more background on the project.

Which resource to use for which problem

If your problem is about… Go to…
Setting up the project for the first time Installation page, then the user guide
Using PWAs day to day User guide and related pages
A recurring or common question FAQ page
Understanding what the project is or how it works About section and repository README
Anything else Help section

Before you dig in: the intended setup path

The site's usage guidance is to install the browser extension and then follow the in-browser installation instructions, with the installation page covering installation and setup in more detail. If you hit a problem, it helps to confirm you followed that path — extension first, then the in-browser steps — before assuming something is broken.

What the tool is, briefly

PWAsForFirefox is a tool to install, manage, and use Progressive Web Apps in Mozilla Firefox. Firefox supports many PWA APIs but does not support installing them as a standalone system app with an app-like experience — functionality often called a Site Specific Browser (SSB). The project creates a custom modified Firefox runtime so websites can be installed as standalone apps, and provides a console tool plus a browser extension to install, manage, and use them.

Knowing this matters for troubleshooting: installed PWAs run in an isolated Firefox installation and profile(s), have their own start/app menu entry and taskbar icon, live in their own window, and have no tabs or address bar. Problems that look like "missing" browser chrome are by design, not a fault.

Practical notes

  • The project supports installing all websites as PWAs, and supports all Firefox addons/extensions and built-in Firefox features — so if an extension behaves unexpectedly inside a PWA, that context is worth mentioning when you consult the FAQ or help section.
  • Installation and patching of the installation and profile(s) is automatic but user-triggered, which is useful to know if you are diagnosing a version or update issue.

The site does not describe support channels beyond these documentation resources, so the FAQ and help section remain the concrete starting points.