PWA Browser Scorecards

The fact that iOS safari supports SO many lifecycle features except BeforeInstallPrompt is just so frustrating.

You can feel the dev team trying to get as close as they can without shooting their golden goose App Store.

So many apps could be PWA…and we could expect so much more from the median PWA.

I'm still so pissed at how Apple continues to hamstring PWAs to push their own platform. Can't wait for the day their app store era is over and something actually user-focused is prevalent

I can easily imagine a world where you could install an open source PWA from an archive file into its own security sandbox without any further hoops to jump through, and it continues to just work indefinitely because the web has very good backwards compatibility guarantees. Instead, we have to get licensed and notarized by the monopolies and they keep you on a constant treadmill of drudgery just to stay up to date. Or you install somebody else's monopoly-approved "legitimate business" app which steals or leaks your data. Sad!

"Security and privacy" is kind of a funny one to rate. As I understand it, one of the main reasons why Safari doesn't support as many advanced APIs as other browsers is that they want to avoid technologies that pose a fingerprinting risk. From that point of view, Chrome is pretty bad.

Seems like a useful resource to help devs understand PWA support across platforms. Thank you!

I help run PWABuilder.com, which packages PWAs for app stores. I think it would be helpful to our users to see your pwascore.com site. Maybe we can link to your site from ours.

I’ve always thought it funny how PWAs were pushed by Apple of all people in the beginning. Nowadays they might as well not exists for iOS/macOS

This site is harmful.

Yes, we need to do this, but it has to be an actual test suite.

People need to be able to contribute tests to expose broken “supported” functionality.

This just perpetuates lies.

Kudos to the author, I have absolutely nothing against your efforts, but the approach is just flawed in my opinion.

It says "popular mobile and desktop browsers" but doesn't include the most popular desktop browser, Chrome? I know it has Chrome for Android, but desktop Chrome supports some extra stuff (Shared Workers, File System Access API) which makes it basically the best browser for PWAs. Feels like that level of popularity and quality should be represented somewhere.

Biggest problem for me as a PWA dev is how eager mobile browsers are to delete your local data, which is not part of this scorecard. I guess that's tricky to quantify, but basically they all suck but Safari sucks more.

Are there any popular PWA-only apps without a mobile app counterpart?

File-sharing services (e.g., sharedrop?) seems to be some of them but I'm not sure if its popular in terms of usage.

Looks pretty cool. Some comments on usability, It would be handy to see a visual indicator of which capabilities where missing from each browser - maybe you could colour each section heading Green or Red? It would also be handy if you could toggle all open/closed.

Why is Firefox marked as "unknown" for many easily findable settings/capabilities? (Ex: https requirement)

This feels like a chrome ad

Tabbed Application Mode is really supported across all three?

I know Chrome / Edge kept having issues with it being behind experimental flag and even the flag breaking and going away between builds.

Never heard of Safari supporting tabbed mode for PWA's

This is probably the biggest issue for me with PWA's windows.open actually opening a new full OS window sucks rather than a built in native tab strip.

https://developer.mozilla.org/en-US/docs/Web/Progressive_web...

Oh cool, I was wondering about this.

Is there not much PWA stuff for desktop or... does it not matter since you can just pin tabs?