đź–– Live long and prosper, PWAs on Firefox. PWA Browser Installation Changes # On the Chromium-side of the world, 2021 will bring changes in the PWA installation process to help the user experience. First, the PWA criteria are changing, and it's adding offline content as a mandatory requirement.
Also, additional pseudo-browsers available in the App Store, such as Chrome, Firefox, Brave or Edge won’t be able to install a PWA or use Service Workers. Once it’s installed, it will look. The new version of Firefox brings functions to protect privacy, but marks a step backwards in the support of PWA applications which bear much hope. Mozilla has released a major new version of its Firefox browser. Version 85 incorporates its share of novelty, and in particular protections against “supercookies», But also a look back at. I found a PWA called Wavemaker, which is a writing app that I would say is a good alternative to Scrivener.Anyway, I got the PWA installed on my Android device running 9.0 Pie, and somehow, I got it to install as an app on Chrome on the same computer, but I can't get the website prompt me to do the same on Firefox.
-->Progressive Web Apps (PWAs) provide access to open web technologies for cross-platform interoperability and provide your users with a native, app-like experience customized for their devices. PWAs are websites that are progressively enhanced to function like native apps on supporting platforms. The qualities of a PWA combine the best of the web and native apps.
Discoverable
From web search results and supporting app stores
Installable
Pin and launch from the home screen, Start Menu, Taskbar, and so on
Re-engageable
Send push notifications, even when the app is not active
Network Independent
Works offline and in low-network conditions
Progressive
Experience scales up (or down) with device capabilities
Safe
Provides a secure HTTPS endpoint and other user safeguards
Responsive
Adapts to the user's screen size or orientation and input method
Firefox Pearl's Peril
Linkable
Share and launch from a standard hyperlink
Build (or convert) your existing website to a PWA to enhance your engagement with your users. Enhancements include push notifications, app-like integration, and offline support. Continue to build your audience on the open web for users to discover your PWA through search and link-sharing. Best of all, your app is updated in using your web server code.
PWAs on Microsoft Edge (Chromium)
When you build a Progressive Web App targeting web standard APIs, your app may be deployed across platforms and devices and take advantage of the device-specific capabilities as available. PWAs in Microsoft Edge (Chromium) add the following advantages to your website.
- Your app is built on a standards-based web platform.
- Enables your users to install your app directly from the browser.
- Enables your users to install your app without a Store-based deployment or registration.
Desktop PWAs are supported on any of the platforms Microsoft Edge (Chromium) is available. Microsoft Edge (Chromium) is available on Windows 7, Windows 10, and macOS. The following benefits are included.
Apps may be installed directly from within the browser using the Install icon in the navigation bar.
Apps may also be installed, run, and managed from the Settings > Apps menu
Web Notifications are integrated into the Windows notification system
Shared cookie store with the browser profile that installed the app
Access to other browser features using the Setting and more (
...) menu including certificate validation, site permissions, tracking protection, and browser extensionsFull access to Microsoft Edge DevTools for debugging your app
Note
For more information about PWA benefits, upcoming features, and short demos, navigate to Build 2020 PWA session.
Requirements
To run as a PWA, your server-hosted web app should include following minimum requirements.
Protects your users by providing a secure connection for server or app communication. Service Workers and other PWA technologies only work with web resources served over a secure connection (or from localhost for debugging purposes).
Uses Service Worker threads to act as network proxies between your server and client app. Service Worker threads provide offline support, resource caching, push notifications, background data sync, and page-load performance optimizations.
Provides a JSON-based metadata file that describes key information about your web app, so that Windows 10 and other host platforms provide your PWA users with an installable, native app-like experience. Key information includes icons, language, and URL entry point.
To be a great PWA, your app must also meet the following requirements.
Ensure your PWA works by testing in different browsers and environments.
Employs fluid layouts and flexible images. Responsive design includes the following elements that adapt your UX to your user's device.
- CSS grid
- CSS grid and flexbox
Uses device emulation tools from your browser to locally test, or create a remote debugging session on Windows or Android to test directly on a target device.
Routes each page of your site to a unique URL so existing users may help you engage an even broader audience through social media sharing.
Uses code quality tools like the Webhint linter to optimize the efficiency, robustness, safety, and accessibility of your app.
Verifies your PWA against the Google baseline PWA checklist.
Note
To turn your PWA into a Microsoft Store app, navigate to Progressive Web Apps in the Microsoft Store.
See also
I use a lot of web-based services and it’s not always convenient to have all of them as tabs in a web browser. Pinning tabs in Firefox is convenient, but those are lost when restarting Firefox, you’re using multiple browser windows and don’t close the one with the pinned tabs last. So I’d like to run some sites as “standalone” PWA in a dedicated window and added to the GNOME application list. There used to be a Epiphany feature for that but I can’t find it and it too is now running in Flatpak so I don’t see how that would work.
The combination of these 3 things don’t add up:
- Our web browsers are soon all running in Flatpak containers. I’m running the latest Firefox beta from Flathub testing and it’s looking pretty good.
- Websites are increasingly adding Progressive Web App support. Most major ones already do. Some don’t even offer a mobile/desktop app and have gone PWA-only.
- Not every website can and will be offered as a PWA wrapper on Flathub
Firefox Pwa Windows
So what’s the most convenient way to exose PWA’s as standalone web-apps in Silverblue? Does anyone know?