You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/content/en/2025/pwa.md
+34-34Lines changed: 34 additions & 34 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -49,7 +49,7 @@ Service workers remain essential to allow advanced capabilities like background
49
49
{{ figure_markup(
50
50
image="pwa-sw-control-ranking.png",
51
51
caption="Service worker controlled pages by rank.",
52
-
description="Bar chart showing the PWA websites controlled by service workers by their ranking.",
52
+
description="Bar chart showing the correlation between a website's popularity and its use of service worker technology. The data shows that adoption is significantly higher among top-tier websites, with the highest implementation occurring in the top 10,000 rank at 29.4% for desktop and 27.5% for mobile. As the sample size broadens to include less popular sites, adoption rates drop steadily, reaching a low of 20.0% when looking at all websites combined. Overall, desktop platforms consistently maintain a slight lead in service worker usage across every ranking category compared to their mobile counterparts.",
@@ -67,7 +67,7 @@ Following we have usage data for capabilities of service worker by events, metho
67
67
{{ figure_markup(
68
68
image="pwa-sw-events.png",
69
69
caption="Most used service worker events.",
70
-
description="Bar chart showing the popularity of service worker events, with activate being around 96% and install around 64%.",
70
+
description="Bar chart showing the most used service worker events. Lifecycle events dominate the data, with the `activate` event appearing on 96% of PWA sites and the `install` event used by 64%. Functional events see lower but notable adoption, with `fetch` at 12% for intercepting network requests and `push` and `notificationclick` both at 7%.",
@@ -83,7 +83,7 @@ Usage of other advanced events, like `fetch`, `notificationclick` and `push` fal
83
83
{{ figure_markup(
84
84
image="pwa-sw-methods.png",
85
85
caption="Most used service worker methods.",
86
-
description="Bar chart showing the popularity of service worker methods, with `skipWaiting` being used on approximately 66% of PWA pages.",
86
+
description="Bar chart showing the popularity of service worker methods, with `skipWaiting` being used on approximately 68% of desktop PWA pages and 63% of mobile PWA pages.",
@@ -97,7 +97,7 @@ Looking at the most used service worker method, `skipWaiting()` has a notable us
97
97
{{ figure_markup(
98
98
image="pwa-sw-objects.png",
99
99
caption="Most used service worker objects.",
100
-
description="Bar chart showing the popularity of service worker objects.",
100
+
description="Bar chart showing the adoption rates of various service worker objects on desktop and mobile platforms. The data shows that `clients.claim` is the most widely used object, appearing on approximately 67 percent of desktop PWA pages and 63 percent of mobile PWA pages. Other common objects include `caches.open` and `caches.delete`, which are notably more prevalent on mobile devices than on desktop.",
@@ -113,7 +113,7 @@ As hinted before, the main methods from these correspond to `claim`, `open`/`del
113
113
{{ figure_markup(
114
114
image="pwa-sw-reg-properties.png",
115
115
caption="Most registered service worker properties.",
116
-
description="Bar chart showing the most registered service worker properties, with pushManager.subscribe and pushManager.getSubscriptionon top with a 7% on mobile.",
116
+
description="Bar chart showing the adoption of various service worker registration features among desktop and mobile Progressive Web Apps. The data shows that `pushManager.subscribe` and `pushManager.getSubscription` are the most utilized properties, each appearing on approximately 7% of PWA websites across both platforms. In contrast, advanced synchronization and performance properties like `sync.register` and `navigationPreload.enable` see much lower implementation, with usage rates hovering between 1% and 2%. Overall, the visualization demonstrates that push notification capabilities are significantly more common in the PWA ecosystem than background sync or navigation preloading features.",
@@ -135,7 +135,7 @@ The web application manifest is now, more than ever, the most important part of
135
135
)
136
136
}}
137
137
138
-
For the current year, 94.4% of desktop sites and 94.9% of mobile sites are parseable. There is [no change from the last data set](../en/2022/pwa#fig-9), and same as last time around, the fact that the manifest file was able to be parsed does not imply completeness or minimum availability of features. Many values in the manifest, as important as they may seem, have reasonable fallbacks in place.
138
+
For the current year, 94.5% of desktop sites and 94.9% of mobile sites are parseable. There is [no change from the last data set](../en/2022/pwa#fig-9), and same as last time around, the fact that the manifest file was able to be parsed does not imply completeness or minimum availability of features. Many values in the manifest, as important as they may seem, have reasonable fallbacks in place.
139
139
140
140
From those parseable manifests, we will now look at individual present fields. This can give us an understanding of how developers are using the manifest file and if there have been changes since 2022.
141
141
@@ -144,7 +144,7 @@ From those parseable manifests, we will now look at individual present fields. T
144
144
{{ figure_markup(
145
145
image="pwa-manifest-properties.png",
146
146
caption="Most used manifest properties.",
147
-
description="Bar chart showing the most used Web App manifest properties. Name Icons and short_name on the top.",
147
+
description="Bar chart showing the most frequently used fields within web app manifest files for both desktop and mobile platforms. Core identity and visual properties dominate the findings, with `name` and `icons` appearing in over 90% of manifests, followed closely by `short_name`, `display`, and `theme_color` at roughly 80%. Mobile PWAs exhibit slightly higher adoption across every listed property compared to desktop, particularly for functional fields like `start_url` and `scope`. Overall, the data illustrates a high level of standardization for basic PWA identification, while more descriptive or restrictive properties like `description` and `orientation` remain significantly less common.",
@@ -186,7 +186,7 @@ Let's examine how individual members rate in the totality of manifest files scan
186
186
</tr>
187
187
<tr>
188
188
<td>`background_color`</td>
189
-
<td class="numeric">79%</td>
189
+
<td class="numeric">80%</td>
190
190
<td class="numeric">82%</td>
191
191
</tr>
192
192
<tr>
@@ -212,7 +212,7 @@ Let's examine how individual members rate in the totality of manifest files scan
212
212
<tr>
213
213
<td>`orientation`</td>
214
214
<td class="numeric">17%</td>
215
-
<td class="numeric">20%</td>
215
+
<td class="numeric">21%</td>
216
216
</tr>
217
217
</tbody>
218
218
</table>
@@ -224,7 +224,7 @@ For the manifests that specify the `categories` member, the top categories are:
224
224
{{ figure_markup(
225
225
image="pwa-manifest-categories.png",
226
226
caption="Most used manifest category values.",
227
-
description="Bar chart showing the top categories defined in the manifest field (shopping/business and education).",
227
+
description="Bar chart showing the percentage of Progressive Web App manifests that specify a particular application category for desktop and mobile platforms. The data shows that `shopping` and `business` are the overwhelmingly dominant categories, each represented in approximately 2.4% to 2.5% of manifests across both client types. In contrast, all other listed categories—including `education`, `entertainment`, `games`, and `productivity`—see significantly lower adoption, with each appearing in less than 0.3% of manifests.",
@@ -240,7 +240,7 @@ The display member is used to specify the preferred display mode for the web app
240
240
{{ figure_markup(
241
241
image="pwa-manifest-displays.png",
242
242
caption="Most used display values in the manifest (standalone).",
243
-
description="Bar chart showing the most used display values in the manifest file (standalone).",
243
+
description="Bar chart showing the distribution of display modes defined in web app manifests for desktop and mobile platforms. The `standalone` value is the overwhelmingly dominant choice, utilized by 78% of mobile PWA manifests and a similarly high percentage on desktop to provide an app-like experience. Other standardized display values, such as `minimal-ui`, `fullscreen`, and `browser`, see very low adoption, with each accounting for 3% or less of the total. Additionally, a notable portion of manifests, roughly 15%, do not have a display value set.",
@@ -254,7 +254,7 @@ Most web apps (78%) opt for a `standalone` value for the display member. From th
254
254
{{ figure_markup(
255
255
image="pwa-manifest-icons.png",
256
256
caption="Most used icons size values in the manifest.",
257
-
description="Bar chart showing the most used icon size values in the manifest file (192px and 512px).",
257
+
description="Bar chart showing the most common icon dimensions specified in web app manifests for desktop and mobile platforms. The data shows that 192x192 and 512x512 are the overwhelmingly dominant sizes, appearing in approximately 85% and 75% of manifests respectively. All other listed sizes, such as 144x144 and 96x96, see significantly lower adoption, with each utilized by less than 25% of Progressive Web Apps.",
@@ -268,7 +268,7 @@ Top sizes include 192x192 and 512x512.
268
268
{{ figure_markup(
269
269
image="pwa-manifest-orientation.png",
270
270
caption="Most used orientation values in the manifest.",
271
-
description="Bar chart showing the most used orientation values in the manifest file (none!).",
271
+
description="Bar chart showing the percentage of Progressive Web App manifests that specify a default screen orientation for desktop and mobile platforms. The data reveals that an overwhelming majority of manifests—roughly 80 percent—do not have an orientation property set. Among the minority that do define a preference, `portrait` is the most common selection at approximately 12 percent, with mobile applications showing a significantly higher tendency to lock this orientation compared to desktop versions. Other specific orientation values such as `any`, `natural`, and `portrait-primary` see very low adoption, each appearing in fewer than 5 percent of manifests, while `landscape` is the least utilized at just 0.1 percent.",
@@ -284,7 +284,7 @@ We've seen the latest data on what the most used service worker and manifest fea
284
284
{{ figure_markup(
285
285
image="pwa-manifest-sw-manifest-usage.png",
286
286
caption="PWA service worker and manifest file usage.",
287
-
description="Bar chart showing service worker (19.2%) and manifest file (~9%) usage.",
287
+
description="Bar chart showing the adoption of key Progressive Web App technologies on desktop and mobile websites. The data reveals that service workers are significantly more common than web app manifests, with 18.9% of sites implementing the former and roughly 9% implementing the latter across both platforms. When looking at overall adoption, 24.5% of websites use at least one of these PWA features, but only a small fraction—3.3% on desktop and 3.5% on mobile—have implemented both simultaneously.",
@@ -311,53 +311,53 @@ These are the top 10 used advanced capabilities in PWAs for 2025.
311
311
<tbody>
312
312
<tr>
313
313
<td>Compression Streams</td>
314
-
<td>18.38%</td>
315
-
<td>20.86%</td>
314
+
<td>18.4%</td>
315
+
<td>20.9%</td>
316
316
</tr>
317
317
<tr>
318
318
<td>Async Clipboard</td>
319
-
<td>17.85%</td>
320
-
<td>19.13%</td>
319
+
<td>17.9%</td>
320
+
<td>19.1%</td>
321
321
</tr>
322
322
<tr>
323
323
<td>Device Memory</td>
324
-
<td>10.71%</td>
325
-
<td>10.59%</td>
324
+
<td>10.7%</td>
325
+
<td>10.6%</td>
326
326
</tr>
327
327
<tr>
328
328
<td>Web Share</td>
329
-
<td>9.55%</td>
330
-
<td>9.77%</td>
329
+
<td>9.6%</td>
330
+
<td>9.8%</td>
331
331
</tr>
332
332
<tr>
333
333
<td>Media Session</td>
334
-
<td>6.75%</td>
335
-
<td>7.75%</td>
334
+
<td>6.8%</td>
335
+
<td>7.8%</td>
336
336
</tr>
337
337
<tr>
338
338
<td>Add to Home Screen</td>
339
-
<td>6.82%</td>
340
-
<td>7.30%</td>
339
+
<td>6.8%</td>
340
+
<td>7.3%</td>
341
341
</tr>
342
342
<tr>
343
343
<td>Media Capabilities</td>
344
-
<td>6.33%</td>
345
-
<td>7.34%</td>
344
+
<td>6.3%</td>
345
+
<td>7.3%</td>
346
346
</tr>
347
347
<tr>
348
348
<td>Cache Storage</td>
349
-
<td>8.97%</td>
349
+
<td>9.00%</td>
350
350
<td>3.00%</td>
351
351
</tr>
352
352
<tr>
353
353
<td>Service Worker</td>
354
-
<td>3.69%</td>
355
-
<td>3.32%</td>
354
+
<td>3.7%</td>
355
+
<td>3.3%</td>
356
356
</tr>
357
357
<tr>
358
358
<td>Push</td>
359
-
<td>1.72%</td>
360
-
<td>1.61%</td>
359
+
<td>1.7%</td>
360
+
<td>1.6%</td>
361
361
</tr>
362
362
</tbody>
363
363
</table>
@@ -373,7 +373,7 @@ Notifications make sense for apps as they allow the user to re-engage with the a
373
373
{{ figure_markup(
374
374
image="pwa-manifest-notification-rates.png",
375
375
caption="PWA notification acceptance rates.",
376
-
description="Bar chart showing PWA notification acceptance rates. Most of themare ignored in both desktop and mobile.",
376
+
description="Stacked bar chart showing desktop users overwhelmingly ignoring notifications at a rate of 78 percent, while only 6 percent choose to accept them. Mobile users appear more engaged with the prompts, showing a significantly higher acceptance rate of 16 percent, though they are also far more likely to actively deny or dismiss the requests compared to their desktop counterparts.",
0 commit comments