Is It the Beginning of the End for PWAs?

After Firefox, will others follow suit?

Mahdhi Rezvi

Mar 17 · 4 min read

Photo by Szabo Viktor on Unsplash

Progressive web apps are changing the way we understand applications by providing an app-like experience in the web form. It was a way of describing applications that take advantage of new features supported by modern browsers, including service workers and web app manifests, and also lets users upgrade web apps to progressive web applications regardless of their native operating system.

But PWAs have been linked with several privacy concerns over the years. This had led to Apple blocking several PWA features on Safari. You can read more about them over here.

Nevertheless, other browsers such as Chrome and Firefox had continued to support the development of PWAs immensely.

Recently, Mozilla had released Firefox 85 which was aimed at protecting against supercookies. This version also appears to have dropped support for an essential feature for desktop PWAs. Let’s have a look at what it is.

What Was Dropped?

Firefox is dropping an experimental feature that supports installing Progressive Web Apps to the desktop. This feature is known as Site Specific Browser — SSB.

For those who were observing the situation, Mozilla had already indicated that they might drop support for SSB in future releases. The reason for this removal can be found in the bug tracker comment.

The SSB feature has only ever been available through a hidden pref and has multiple known bugs. Additionally user research found little to no perceived user benefit to the feature and so there is no intent to continue development on it at this time. As the feature is costing us time in terms of bug triage and keeping it around is sending the wrong signal that this is a supported feature we are going to remove the feature from Firefox.

What is SSB?

SSB is an experimental feature that allows any website to run in desktop mode, with its own window. The Site Specific Browser feature, which was available in Firefox 73 and above, allowed you to launch any website in a window with a minimal UI.

Is This A Deal Breaker?

It all depends on your perspective and intended usage of PWAs. If you think that PWAs are a way of getting applications that are platform-independent and perform like native applications, then you might be disappointed with this decision. If you think PWAs are simply a shortcut on your desktop, you probably wouldn’t bother about this change.

There are a number of people who are unhappy about this decision, but the numbers are quite low compared to the total number of users. This is mainly because this was an experimental feature and was not known to many.

As Ian says,

Users aren’t going to get upset because they have no idea what is being denied them and anyway why should they care that you have had to put extra effort in to create a native app?

Since technology is evolving at a rapid pace, companies spend a lot of resources on R&D. Experimental features are essential as they decide the future of the application. When something significant is dropped, it sends the wrong signal to the users.

But when the time comes and when PWAs become a highlighted browser feature, Firefox might lose a considerable amount of users to alternative browsers due to this move.

Why The Fuss?

You might start wondering whether this article title is clickbait. No, it is not.

A common trend in the tech world is when,

  1. A company makes a radical move
  2. Competitors mock them
  3. After a few years, the competitors who mocked the move, adopt the same move

You can relate this to several notable incidents such as the removal of the headphone jack, the removal of the home button in mobile phones, and the most recent buzz — removal of the charger from the mobile phone box.

The reason for the removal of SSB was mentioned to be the bugs that were causing trouble and precious time. If that’s the case, alternate browsers such as Chrome and Edge might also feel that this move will be beneficial for them. In such a scenario, we might lose PWAs for desktops for a while as similar incidents have happened in the past. Although this is highly unlikely, there is always a chance for something like this to happen, especially in the world of tech.

What do you think about Mozilla’s move? Comment them below.

Thank you for reading.

Collaborate on independent components with Bit

Bit is an ultra-extensible tool that lets you author, version, share and collaborate on independent components.

Use it to build modular design systems, author and deliver micro frontends or simply share components between applications.

Bit’s latest beta release: https://harmony-docs.bit.dev/

Author: Shantun Parmar

Leave a Reply

Your email address will not be published.