Where pwa.gripe cherry-picks and has an axe to grind, pwascore.com is intended to be a more thorough and dispassionate evaluation. I will add desktop browsers soon.
Click "Expand All" for a complete and detailed list. Click "How Scores Work" to understand the scoring heuristics.
Well the notifications on your web site doesn't provide the full idea of how limited it is in Safari. We have to ask users to install the shortcut before allowing notifications with Safari. Guess how many users actually go through with installing the shortcut? Nearly none.
If we had to ask users to go into their settings and switch the "enable notifications" flag we wouldn't call that supporting anything. The whole process of installing a shortcut to even get to the point where we can ask for notifications is even more convoluted on iOS.
The most significant effect is that experimental and non-standard PWA capabilities aren't reflected in the primary score. You can see raw/unweighted scores by hovering over the primary score. Chrome wins handily if you count experimental/non-standard features.
For standards-based features I used a 4-tier model, described about halfway through the README (which I should also add to About):
This weighting turns out to be reasonably conservative. For example, if you hover over the score for Firefox (the largest benefactor), you'll see that it bumps Firefox's score by 5.
I'm very open to feedback. This is a sincere attempt to quantify vendors' PWA support.
Where pwa.gripe cherry-picks and has an axe to grind, pwascore.com is intended to be a more thorough and dispassionate evaluation. I will add desktop browsers soon.
Click "Expand All" for a complete and detailed list. Click "How Scores Work" to understand the scoring heuristics.