How can Firefox create the best support for web apps on the desktop?

[david-rubino]

(See my quick update posted February 4, 2025: https://connect.mozilla.org/t5/discussions/how-can-firefox-create-the-best-support-for-web-apps-on-t..., and then another update posted March 17, 2025: https://connect.mozilla.org/t5/discussions/how-can-firefox-create-the-best-support-for-web-apps-on-t...)

---

Hi everyone, my name is David Rubino and I’m a product manager for Firefox. As the Firefox leadership team mentioned in the Reddit AMA last week, we’re taking a fresh look at Progressive Web Apps (PWAs), which have long been a top request from our Mozilla Connect community. Today I want to share a concept that aims to address some of this feedback. 

As you may know, we built a prototype for desktop PWAs a few years ago, and unfortunately user testing on our solution showed confusion and lack of perceived value. We didn’t release it because we didn’t have an approach that could meet the needs of power users without causing confusion among the broader user base. Recently, other browsers have implemented or enhanced their approach to PWAs, for example by making it easy to install any website as a web app (even if no PWA manifest is provided), and by running web apps in the same session as normal browser tabs. I was a user of these features, and so when I joined the Firefox Product Management team last year, I decided to take a fresh look at how Firefox might approach the problem. 

In this post you will see that I don’t use the term “PWA” and instead stick with the more generic “web app”. While there are some working definitions for what a PWA is and is not, most of the feedback from the Firefox community are requests for specific capabilities. So when considering what Firefox should do, I’m focusing on how we can offer features that help you get a more app-like experience for any website you choose, when you choose. 

There are many specific requests in the thread, but viewed through this lens a few emerge:

1. Web apps should appear with their own icons alongside traditional apps, both in places where you launch apps and where running apps are shown. 
2. Web apps should remain open until you close them. You should not be able to “navigate away” from them like a web page.
3. Like many mobile apps, desktop web apps should be able to handle links to their website in lieu of having them opened in a normal browser window. 

It’s possible to take the web app concept further than is needed, into the realm of making web apps be as app-like as possible. This can make it seem like you’re not using a web browser or a website at all. Some examples of this might be having PWAs be installed and uninstalled using the OS, removing all or nearly-all of the browser “frame”, and limiting access to common browser features like bookmarks and search. While some of these may turn out to be beneficial, it’s not a goal to make it feel like you’re not in Firefox.

In fact, contrary to the notion that web apps should be “installed” like regular apps, a core idea of this concept is that running a web app should be thought of as moving a tab to your taskbar or dock... a one-step operation that can be undone just as easily. 

So what might this experience look like? Let’s look at the following topics:

1. Moving into and out of a web app “mode”
2. Offering a different browser UI for a web app
3. Browsing within and between sites
4. Integrating with the operating system

Moving into and out of a web app “mode”

As stated above, you should be able to take any tab and move it into web app mode in one step. When you take this action, the tab would be moved into a new web app window, maintaining the state of the web page entirely. You could even be watching a video, and it won’t miss a frame. There would be no setup. Each website will have some preferences associated with it, but the intent will be to have sensible defaults that work for most people, informed by a manifest if the site offers one. Moving a tab back out of this mode will be just as simple. 

Offering a different browser UI for a web app

Web apps are still websites in a web browser, so the goal will be to fully maintain access to features that help you with the website itself, while de emphasizing features that are about managing multiple websites. Some examples:

• No tabs or bookmarks bar by default, but these could be enabled in web app preferences
• The main toolbar would be fully enabled, including the address bar and extensions 
• A new toolbar section would show the icon of the website prominently, clearly indicating you’re in web app mode for a given site. This section would offer access to settings and controls for the web app.
• In lieu of a new tab button, there would be buttons to open a new tab in a normal Firefox window, or a new instance of the current web app. 
• The address bar would not be read-only, offering easy access to Firefox Suggest and the ability to search. Web pages opened from here would land in a new tab in a regular Firefox window. 

Browsing within and between sites

One of the key differences between a normal mode webpage and a web app is that you shouldn’t be able to “navigate away” from a web app. To exit a web app you have to explicitly close it. To accomplish this, each web app would be a “single site browser”. Navigations within the current website will remain in the app, and navigations outside the current website will open in a normal Firefox window. There will be exceptions to help with login flows and redirections so that a web app feels as much as possible like an app that only opens a browser when opening a truly external page. 

We would also introduce “link capture”, which would allow a web app to register itself to handle URLs within its scope. For example, if you click on a link to reddit.com in a normal Firefox window, the link would open in the Reddit web app. This behavior is analogous to how mobile browsers redirect links to registered mobile apps. 

Integrating with the operating system

On Windows, it is straightforward to show web apps separately on the taskbar using differentiated icons, to allow them to be pinned, to show them in the Start menu, in the ALT+TAB and window snap experience, and so on. This allows quick access to web apps using the same surfaces used to run or switch between regular apps. By “leveling up” to the taskbar websites you leave running and revisit often, you can save time over hunting for them in Firefox. 

This behavior may be more challenging to implement on macOS and is likely to have some limitations comparatively. You should expect that if we build a prototype, it will begin as a Windows-only feature. Once proven we would bring it to our other desktop platforms leveraging the features supported by them. 

Please let us know what you think!

I am hopeful Firefox can bring a web app experience to the desktop that will feel natural to all users, while supporting the needs of our power users. In particular, I think we can improve upon the current experience offered by other web browsers by offering one-step setup, retaining access to core browser features, and allowing links to be “captured” automatically. 

We are looking to make progress in this area soon, so I would love to get a discussion going about what is right and wrong and missing from this set of ideas. While I did read every post in the Ideas thread, I am aware I did not address every topic mentioned, so please especially bring up what I skipped that is important to you. 

Thanks in advance!

-David Rubino
Product Manager
Mozilla Firefox

[ShowMeBillyJo]

This articulates everything wrong with Mozilla's current design direction. In agile terms, it feels like Mozilla are skipping straight to designing the race car they think we want, when the existing PWA paradigm is the skateboard moped we're all asking for.

Grandma doesn't use Firefox anymore. We, the folks who do, don't need or want a differentiator. Mozilla doesn't need to fix what isn't broken. We just need something that works.

[bijm]

Well said, and I would like to echo this sentiment.

[SanguinePar]

"I already have a traditional browsing experience, but it falls short in some select usecases where a user experience more akin to a native application would be much more helpful"

This is absolutely spot on - I want a PWA so I can FEEL like I'm using an app, even though it's secretly just a browser with a false moustache on.

[bobster]

Agreed and I'm excited that this is still being worked on.. Hoping it comes out soon!

[vinnom]

Some awesome ideas for a first approach. One thing I would like to highlight though is that a Firefox web app icon on linux distros would be easy to implement (basically a .desktop file with a few parameters), so please consider it to be OOB too, not a Windows-only feature.

[Zarathin]

Based on this discussion I'm really liking the direction that PWA support in Firefox seems to be going, I look forward to trying it!

One stumbling block I wanted to bring up is a limitation in Floorp's implementation of PWA's which significantly hampers my particular use case and probably many others - hence why I want to bring it up here to help avoid Firefox doing the same thing.

When creating a PWA in Floorp, the distinguishing information it stores to create start menu/desktop shortcuts reference only the primary domain of the URL, ignoring any subdomains. For example, if I wanted to have two PWAs of Wikipedia installed, with one pointed to English Wikipedia (en.wikipedia.org) and the other pointed to Spanish Wikipedia (es.wikipedia.org), whichever PWA I create first will have its shortcuts overwritten by the PWA I create second, since it's only looking at the "wikipedia.org" portion of the URL.

I would love to be able to have separate PWAs installed for different subdomains of the same primary domain, either automatically or with an easily accessible override.

[nachtfalter]

I also would like to have the abillity to install more than one PWA from one domain, at e.g. based on the manifests scope. Currently with Chrome it's not possible to have more than one per domain, so I have to install the second one with Edge... So please don't build this limiation in.

I can't wait to see PWAs in Firefox! And thanks to the Firefox-Team for this amazing browser.