Web App Manifest

You might say

Check the Web App Manifest name, icons, start_url, and display, then reinstall and verify the launch result.

A JSON file that describes a Web app's name, icons, and launch behaviorA page links to this JSON file with a manifest link, and a browser can use its name, icons, start_url, and display to create an install entry and launch window. Having a Manifest does not by itself provide complete offline PWA behavior.

Know first

JSON HTML Deployment

Manifestmanifest.json

How manifest.json becomes an install entry

index.html

1<link rel="manifest" href="/manifest.webmanifest">

VInstall VibeHubBrowser install entry

The manifest describes installation and launch; it does not guarantee offline use.

What the Manifest controls after installation

It describes identity and launch behavior: name affects the installed name, icons provide system artwork, start_url sets the launch address, and display influences whether it opens like an app or a normal tab. The page must link the intended file.

The installed result is the evidence: After editing the file, reinstall and check the name, icon, launch path, and window mode. A page opening in a browser proves only that it is reachable, not that install metadata is correct.

Quick checkChoose the best answer

An installed site always opens at the wrong path. What should you check first?

Check the Manifest start_url and verify the launch address after reinstallingChange the Favicon because the browser infers the launch path from itOnly add a Service Worker and assume the launch address will become correct

You can say this to an AI Agent

Inspect the Web App Manifest referenced by manifest link and check name, icons, start_url, and display. After fixing it, remove and reinstall the app, then verify the Home Screen name, icon, launch URL, and window mode. Do not equate installability with offline support.

Learn next

1App Icon→2Deployment→