Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Finalize assignments: Chapter 11. PWA #13

Closed
rviscomi opened this issue May 21, 2019 · 12 comments

Comments

@rviscomi
Copy link
Member

commented May 21, 2019

Section Chapter Authors Reviewers
II. User Experience 11. PWA @tomayac @jeffposnick @hyperpress @ahmadawais

Due date: To help us stay on schedule, please complete the action items in this issue by June 3.

To do:

  • Assign subject matter experts (coauthors)
  • Finalize peer reviewers
  • Finalize metrics

Current list of metrics:

  • % of pages with SW installs
  • Manifest
  • Stats on different service worker events
  • Stats on different web app manifest properties
  • Workbox adoption/usage
  • beforeinstallprompt usage

👉AI (coauthors): Peer reviewers are trusted experts who can support you when brainstorming metrics, interpreting results, and writing the report. Ideally this chapter will have multiple reviewers who can promote a diversity of perspectives. You currently have 1 peer reviewer.

👉 AI (coauthors): Finalize which metrics you might like to include in an annual "state of PWAs" report powered by HTTP Archive. Community contributors have initially sketched out a few ideas to get the ball rolling, but it's up to you, the subject matter experts, to know exactly which metrics we should be looking at. You can use the brainstorming doc to explore ideas.

The metrics should paint a holistic, data-driven picture of the PWA landscape. The HTTP Archive does have its limitations and blind spots, so if there are metrics out of scope it's still good to identify them now during the brainstorming phase. We can make a note of them in the final report so readers understand why they're not discussed and the HTTP Archive team can make an effort to improve our telemetry for next year's Almanac.

Next steps: Over the next couple of months analysts will write the queries and generate the results, then hand everything off to you to write up your interpretation of the data.

Additional resources:

@rviscomi rviscomi transferred this issue from HTTPArchive/httparchive.org May 21, 2019
@rviscomi rviscomi added this to the Chapter planning complete milestone May 21, 2019
@rviscomi rviscomi added this to TODO in Web Almanac via automation May 21, 2019
@rviscomi rviscomi changed the title [Web Almanac] Finalize assignments: Chapter 11. PWA Finalize assignments: Chapter 11. PWA May 21, 2019
@rviscomi rviscomi moved this from TODO to In Progress in Web Almanac May 21, 2019
@mikegeyser

This comment has been minimized.

Copy link
Contributor

commented May 22, 2019

Hi!

A quick question. Is it possible from the data set to get an idea of number (or %) of installs? (Sorry, I genuinely don't know.)

If we can, then wouldn't it be interesting to see what form factors (mobile/desktop/etc) PWAs were being installed in? Especially with the recent drive for PWA adoption on desktop.

(Ok, so technically two questions.)

@jeffposnick

This comment has been minimized.

Copy link

commented May 23, 2019

I'll defer to @tomayac in case he has any opinions otherwise, but both that list of metrics and the suggested peer reviewer (thanks @hyperpress!) seem good to me.

@hyperpress

This comment has been minimized.

Copy link
Contributor

commented May 23, 2019

Thanks all. Good to go here.

@rviscomi

This comment has been minimized.

Copy link
Member Author

commented May 23, 2019

@mikegeyser what you're asking about would need to come from a field dataset like the Chrome UX Report, which doesn't include installs/PWA stats. To my knowledge I'm not aware of another dataset that includes those metrics. HTTP Archive data could tell us how many sites are PWA-capable, but not necessarily the user experience of installing them.

@tomayac

This comment has been minimized.

Copy link
Member

commented May 24, 2019

Sounds all good to me.

@Eccenux

This comment has been minimized.

Copy link

commented May 24, 2019

Note that Chrome/Blink requires an app to have a PNG image in the manifest of at least 144px in size. Only then it can be installed. So to be installable the manifest must contain at least the text 144x144 and image/png. Official criteria talk about 192 and 512px but they either don't check this or accept SVG too.

Anyway I think it would be interesting to know what types of icons and what sizes are found in manifests.

@rviscomi

This comment has been minimized.

Copy link
Member Author

commented May 24, 2019

Thanks @Eccenux that's useful info to know. Agreed that icon sizes would be interesting to include. I'll defer to the authors to add it.

@tomayac @jeffposnick I know you've both done some HA analysis in the past. Would you be interested in writing the queries for this chapter? Also, can you think of 1 or 2 other people who might be good peer reviewers for this subject?

@hyperpress I've sent you an invite to join the @HTTPArchive/reviewers team. You can visit https://github.com/HTTPArchive to accept.

@rviscomi

This comment has been minimized.

Copy link
Member Author

commented Jun 4, 2019

@tomayac @jeffposnick @hyperpress we're hoping to finalize the metrics for each chapter today. If everyone is happy with the list of metrics in #13 (comment) could you tick the checkbox and close this issue? I'd also recommend finding at least one more peer reviewer if possible.

@hyperpress also, please accept your invitation to join the reviewers team.

@hyperpress

This comment has been minimized.

Copy link
Contributor

commented Jun 4, 2019

@rviscomi

This comment has been minimized.

Copy link
Member Author

commented Jun 4, 2019

@hyperpress sure, just resent the invitation. You can also accept it at https://github.com/HTTPArchive. Thanks!

@hyperpress

This comment has been minimized.

Copy link
Contributor

commented Jun 4, 2019

@hyperpress

This comment has been minimized.

Copy link
Contributor

commented Jun 4, 2019

I've reached out to peers over in @Polymer Lit General Channel to see if we can add another reviewer. But I believe metrics look good for moving ahead, and for closing the issue for now. We can adjust if need be.

@hyperpress hyperpress closed this Jun 4, 2019
Web Almanac automation moved this from In Progress to Done Jun 4, 2019
@rviscomi rviscomi referenced this issue Jul 23, 2019
6 of 6 tasks complete
@rviscomi rviscomi referenced this issue Sep 17, 2019
2 of 3 tasks complete
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Web Almanac
  
Done
6 participants
You can’t perform that action at this time.