Re: [w3c/manifest] meta: see web almanac for any insights about manifest usage (#987)

We (Edge) just overhauled our own manifest crawler and I have a dashboard showing usage, errors, store readiness, and more. Happy to share the details I find. It would also be great to correlate the data with what y’all are seeing too. Currently, we’re tracking a little over 135k manifests. Some of the highlights:

- A little over 5% were invalid/un-parsable (mostly—over 97%—due to issues in the page’s HTML)
- More than a few sites are struggling with icon sizes, typically providing incomplete values, using the multiplication sign or asterisk instead of x or X, including commas between multiple size entries, or including the string "apple-touch-icon-" before the size value.
- Nearly 6% of manifests do not have a `name`.
- Only 30% define a start_url
- 63% are "display: standalone"
- Only 68% have a theme color
- 64% define a background color
- Most (89%) do not define orientation
- PNGs are the most popular icon format and most manifest define either 2 (43%) or 6 (~24%) icons
- Only 6% define a language and 3.75% define a text direction

Per #399, I have been continuing to track query string usage and have not found many UUIDs embedded in the `start_url`… yet. The only ones I’ve identified are:

> https://www.geekmagazine.com.br/?tracking=5eb941b082681

> https://www.aadvantageeshopping.com/?source=mn|AA|ALL|mn|NA|bookmark|na||mobile|00000000

> https://shopping.mileageplus.com/?source=mn|UA|ALL|mn|NA|bookmark|na||mobile|00000000

> /?tracelog=51606102_9527_7259_7770&from=desktop
> /?ucid=HPS-1027
> /?source=NV_PWA_HL_HP&agentcode=00399206&utm_medium=WebPush&utm_source=NotifyVisitor
> /?mc=xQZpn7mAMXLZ

I need to investigate these to see if they are using a truly unique identifier though. Most have "utm_source=webapp" or similar. The closest I’ve seen to a tracking value so far is the occasional "utm_campaign=X" or the language or similar. One accidentally (?!) posted an API Key in the start url.

I’ve also got data on newer features too (share_target, protocol_handlers, etc.). I’m planning to write-up a "State of the Manifest" some time in the next quarter.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/manifest/issues/987#issuecomment-882876540