@@ -237,6 +237,33 @@ from the home screen every page in the domain will automatically get the theme c
237
237
<figcaption >Sitewide theme color</figcaption >
238
238
</figure >
239
239
240
+ ## Test your manifest {: #test }
241
+
242
+ If you want to manually verify that your web app manifest is set up correctly,
243
+ use the ** Manifest** tab on the ** Application** panel of Chrome DevTools.
244
+
245
+ ![ The Manifest tab of Chrome DevTools] ( images/devtools-manifest.png )
246
+
247
+ This tab provides a human-readable version of many of your manifest's
248
+ properties. See [ Web app
249
+ manifest] ( /web/tools/chrome-devtools/progressive-web-apps#manifest ) over
250
+ at the Chrome DevTools docs for more information on this tab. You can
251
+ also simulate Add to Homescreen events from here. See [ Testing the app install
252
+ banner] ( /web/fundamentals/engage-and-retain/app-install-banners/#testing-the-app-install-banner )
253
+ for more on this topic.
254
+
255
+ If you want an automated approach towards validating your web app manifest,
256
+ check out [ Lighthouse] ( /web/tools/lighthouse ) . Lighthouse is a web app auditing
257
+ tool that you run as a Chrome Extension or as an NPM module. You provide
258
+ Lighthouse with a URL, it runs a suite of audits against that page, and then
259
+ displays the results in a report. Lighthouse audits related to web app manifests
260
+ include checking that:
261
+
262
+ * The app can be added to the homescreen.
263
+ * After being added, the app launches with a custom splash screen.
264
+ * The color of the browser's address bar is customized.
265
+ * The app is on HTTPS (a prerequisite for Add to Homescreen).
266
+
240
267
## More information
241
268
242
269
This article has given you a quick introduction to web app manifests, but
0 commit comments