HTTPArchive / almanac.httparchive.org

HTTP Archive's annual "State of the Web" report made by the web community
https://almanac.httparchive.org
Apache License 2.0
602 stars 164 forks source link

Mobile Web 2024 #3605

Open nrllh opened 4 months ago

nrllh commented 4 months ago

Mobile Web 2024

Mobile Web illustration

If you're interested in contributing to the Mobile Web chapter of the 2024 Web Almanac, please reply to this issue and indicate which role or roles best fit your interest and availability: author, reviewer, analyst, and/or editor. You might be interested in exploring the changes to this year's version here.

Content team

Lead Authors Reviewers Analysts Editors Coordinator
- - @dwsmart - @LoraRaykova - -
Expand for more information about each role πŸ‘€ - The **[content team lead](https://github.com/HTTPArchive/almanac.httparchive.org/wiki/Content-Team-Leads'-Guide)** is the chapter owner and responsible for setting the scope of the chapter and managing contributors' day-to-day progress. - **[Authors](https://github.com/HTTPArchive/almanac.httparchive.org/wiki/Authors'-Guide)** are subject matter experts and lead the content direction for each chapter. Chapters typically have one or two authors. Authors are responsible for planning the outline of the chapter, analyzing stats and trends, and writing the annual report. - **[Reviewers](https://github.com/HTTPArchive/almanac.httparchive.org/wiki/Reviewers'-Guide)** are also subject matter experts and assist authors with technical reviews during the planning, analyzing, and writing phases. - **[Analysts](https://github.com/HTTPArchive/almanac.httparchive.org/wiki/Analysts'-Guide)** are responsible for researching the stats and trends used throughout the Almanac. Analysts work closely with authors and reviewers during the planning phase to give direction on the types of stats that are possible from the dataset, and during the analyzing/writing phases to ensure that the stats are used correctly. - **[Editors](https://github.com/HTTPArchive/almanac.httparchive.org/wiki/Editors'-Guide)** are technical writers who have a penchant for both technical and non-technical content correctness. Editors have a mastery of the English language and work closely with authors to help wordsmith content and ensure that everything fits together as a cohesive unit. - The **[section coordinator](https://github.com/HTTPArchive/almanac.httparchive.org/wiki/Section-Leads'-Guide)** is the overall owner for all chapters within a section like "User Experience" or "Page Content" and helps to keep each chapter on schedule. _Note: The time commitment for each role varies by the chapter's scope and complexity as well as the number of contributors._ For an overview of how the roles work together at each phase of the project, see the [Chapter Lifecycle](https://github.com/HTTPArchive/almanac.httparchive.org/wiki/Chapter-Lifecycle) doc.

Milestone checklist

0. Form the content team

1. Plan content

2. Gather data

3. Validate results

4. Draft content

5. Publication

6. Virtual conference

Chapter resources

Refer to these 2024 Mobile Web resources throughout the content creation process: πŸ“„ Google Docs for outlining and drafting content πŸ” SQL files for committing the queries used during analysis πŸ“Š Google Sheets for saving the results of queries πŸ“ Markdown file for publishing content and managing public metadata πŸ’» Collab notebook for collaborative coding in Python - if needed πŸ’¬ #web-almanac-mobile-web on Slack for team coordination

nrllh commented 3 months ago

Hey @Suzzicks @foxdavidj @dwsmart @hemanth @CodeMartian @dknauss @siakaramalegos - awesome contributors from previous years πŸ™‚ Are you interested in joining us again this year?

dwsmart commented 3 months ago

Hey @nrllh, I would be happy to be a reviewer.

Some part of me kinda wonders though if thenl mobile web is really more just the web these days, and some of the specifics shouldn't be more in things like the page weight, performance, accessibility chapters?

nrllh commented 3 months ago

Thank you, @dwsmart! The metrics such as performance and accessibility are indeed interesting. However, I believe that we should not limit the scope of our analysis to these aspects alone, as there are still significant differences between desktop and mobile platforms. Nonetheless, the content team is free to choose the topics they wish to analyze and discuss. 😊