Install as App

[screentriggers]

I am new here (like new born baby new). I have created an app and I would like it to install to any device, as if it was an app from Google Play. I have applied various different coding language to have it install as a real, native app, without the browser bar and with it's own icon and name on the home screen of the device, rather than a Chrome shortcut. No matter what I try, I just can't get it to work. Am I missing something key? Do I need to publish this app first or pay for a particular plan in order to make this happen? Please help!

[LuisGustavoCassioli]

Hi @screentriggers,

If you want your web app to install like a real native app (with its own icon and name, not just a Chrome shortcut), you need to configure it as a Progressive Web App (PWA).

Make sure you have:

• A valid manifest.json file
• Proper icons defined in the manifest
• display: standalone in the manifest
• A registered service worker
• HTTPS enabled

Without these, browsers will only create a shortcut instead of installing it as a standalone app.

You do NOT need to publish it to Google Play unless you specifically want it distributed through the Play Store. A properly configured PWA can be installed directly from the browser.

Hope this helps!

[screentriggers]

Thank you SO much for your quick response!

I have a valid manifest.json, proper icons in manifest, a registered service worker (sw.js) and https is enabled. My manifest.json notes display: standalone. I don't know why it won't work. This is my manifest.json code. Would you mind taking a look?

{
"name": "Screen Triggers",
"short_name": "Screen Triggers",
"start_url": "/app/",
"scope": "/app/",
"display": "standalone",
"display_override": ["standalone"],
"orientation": "portrait-primary",
"background_color": "#0b3d91",
"theme_color": "#0b3d91",
"description": "Screen Triggers Library",
"icons": [
{
"src": "/app/icon-192.png",
"sizes": "192x192",
"type": "image/png",
"purpose": "any maskable"
},
{
"src": "/app/icon-512.png",
"sizes": "512x512",
"type": "image/png",
"purpose": "any maskable"
}
]
}

[LuisGustavoCassioli]

Hi @screentriggers,

Your manifest looks mostly correct. However, if installation is not being triggered, the issue is usually not the manifest itself, but one of the following:

1. Service Worker Scope
   Make sure your sw.js is registered within the same scope as /app/.
   If the service worker is registered at /, but your scope/start_url is /app/, it can cause installability issues.

2. Service Worker Control
   Open DevTools → Application → Service Workers and verify:

The service worker is active

It is controlling the page

There are no errors in the console

If the service worker does not control the page, Chrome will not allow installation.

3. Install Criteria
   Chrome requires:

The site to be served over HTTPS

A valid manifest

A service worker controlling the page

The user to interact with the site (sometimes install prompt won’t appear until engagement)

4. Try Lighthouse Audit
   Run a Lighthouse PWA audit in Chrome DevTools to see exactly what requirement is failing.

Also double-check that:

/app/icon-192.png and /app/icon-512.png are accessible directly via URL

The manifest file is correctly linked in your HTML:

If all of the above is correct, the issue is very likely related to service worker control or scope.

[LuisGustavoCassioli]

For a PWA to be installable in Chrome, all of the following must be true:

• The site is served over HTTPS
• The manifest is valid and accessible
• The icons load correctly (no 404 errors)
• A service worker is registered
• The service worker is actively controlling the page

---

From your repo structure, here are the most important things to verify:

1️⃣ Service Worker Scope

If your app runs under /app/, your service worker should either:

• Be located at /app/sw.js
  or
• Be registered with an explicit scope

Example:

if ('serviceWorker' in navigator) {
  navigator.serviceWorker.register('/app/sw.js', {
    scope: '/app/'
  })
  .then(reg => {
    console.log('SW registered with scope:', reg.scope);
  })
  .catch(err => console.error('SW registration failed:', err));
}

If the service worker does not control /app/, Chrome will not trigger installation.

---

2️⃣ Confirm the SW Controls the Page

Open Chrome DevTools → Application → Service Workers and check:

• The service worker is active
• It says “This page is controlled by a service worker”
• There are no errors in the console

If there is no controller, the PWA will not be installable.

---

3️⃣ Verify Manifest and Icons

Make sure this exists in /app/index.html:

<link rel="manifest" href="/app/manifest.json">

Then open these directly in the browser:

• /app/manifest.json
• /app/icon-192.png
• /app/icon-512.png

They must load without 404 errors.

---

4️⃣ Run Lighthouse Audit

Open DevTools → Lighthouse → Select “PWA” → Run audit.

It will tell you exactly which installability criterion is failing.

---

Your manifest itself looks correct, so this is almost certainly a service worker control or scope issue.

Hope it works.