11# IWA project templates
22
3- This project will contain templates that could be used for creation of new Isolated Web Apps (IWAs) projects.
3+ This project will contain templates that could be used for creation of new Isolated Web Apps (IWAs)
4+ projects.
5+
46## Prerequisites
57
6- - Google Chrome 120 +
8+ - Google Chrome 140 +
79
810- openssl
911
@@ -23,7 +25,7 @@ Open Google Chrome, go to `chrome://flags` and enable
2325
2426 chrome://flags/#enable-isolated-web-app-dev-mode
2527
26- chrome://flags/#enable-isolated-web-apps
28+ chrome://flags/#enable-isolated-web-apps (MacOS/Windows/Linux only)
2729
2830Once enabled, and chrome is restarted, go to ` chrome://web-app-internals ` , the web app internals
2931page. This page shows you the web apps you have installed, including Isolated Web Apps and
@@ -82,7 +84,8 @@ Next, create a .env file containing:
8284 PRIVATE_KEY_PASSWORD='YOUR_KEY_PASSWORD'
8385 PORT=YOUR_PORT
8486
85- _ Note: If you're using vite, also declare a variable called NODE_ENV, you can set it to either production/development_
87+ _ Note: If you're using vite, also declare a variable called NODE_ENV, you can set it to either
88+ production/development_
8689
8790_ Note: If you don't specify PORT, the app will fall back to default value (4321)_
8891
@@ -105,9 +108,8 @@ slu74sbybztfypa43w7f7rd34cbhautjcrfegz5lbow7vmwjojbqaaic).
105108
106109_ Note: Your web bundle ID will look differently, this is just an example_
107110
108- Since IWA are using a different schema ` isolated-app:// ` instead of ` https:// ` , you can access it by
109- pasting ` isolated-app://your-web-bundle-id ` in Chrome, or by running it like any other app on your
110- computer.
111+ To run your newly installed Isolated Web App, use chrome://apps (Windows/Mac/Linux only) or by
112+ running it like any other application on your desktop.
111113
112114### Personalizing this template
113115
@@ -126,7 +128,6 @@ Related information:
126128Isolated Web Apps share the same
127129[ Manifest Properties] ( https://web.dev/articles/add-manifest#manifest-properties ) as Progressive Web
128130Apps, with some slight variations, see:
129- [ Isolated Web Apps explainer - Web App manifest section] ( https://chromeos.dev/en/web/isolated-web-apps )
130131
131132There are two fields that should be included, ` version ` and ` update_manifest_url `
132133
@@ -139,8 +140,8 @@ There are two fields that should be included, `version` and `update_manifest_url
139140
140141- How to add API Permissions?
141142
142- By default, Chrome blocks all permission requests from IWAs. You can opt-in to permission policies you need by specifying
143- a ` permissions_policy ` field in your manifest.
143+ By default, Chrome blocks all permission requests from IWAs. You can opt-in to permission policies
144+ you need by specifying a ` permissions_policy ` field in your manifest.
144145
145146_ Note: Adding a permission here does not automatically grant it, it just makes it avaliable to be
146147granted, when a request for that capacity is made._
@@ -155,7 +156,7 @@ granted, when a request for that capacity is made._
155156Related Information
156157
157158- [ Permissions Policy - MDN Docs] ( https://developer.mozilla.org/en-US/docs/Web/HTTP/Guides/Permissions_Policy#allowlists )
158- - [ Permissions Policy header - MDN Docs] ( https://developer.mozilla.org/en-US/docs/Web/HTTP/Guides/Permissions_Policy#allowlists )
159+ - [ Permissions Policy header - MDN Docs] ( https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Permissions-Policy )
159160- [ Web Application Manifest - MDN Docs] ( https://developer.mozilla.org/en-US/docs/Web/Progressive_web_apps/Manifest )
160161
161162### Related Information
0 commit comments