Isolated Web Apps
A packaged, signed web app with extra system APIs.
In one line
Can run as a signed, packaged app with extra system features, on managed Chrome only
A packaged, signed web app with extra system APIs.
Needs a signed bundle and, today, enterprise managed Chrome. Unlocks Direct Sockets and Controlled Frame.
What it can and can't do
What the user does: Your organization installs the signed app on your computer
It can
- Run from a signed bundle instead of a normal web address
- Use raw network connections and controlled frames, which normal sites cannot
- Work as a kiosk or business app
It cannot
- Be installed by a normal visitor, since it needs a managed Chrome today
- Work in Edge, Firefox, Safari or on phones
- Run without a signed bundle
- Reach your files or system outside what the app is given
How it differs between platforms: Only Chrome on managed computers, and still limited. Other browsers and phones do not support it.
Browser support
| Browser | Status | First version | Note |
|---|---|---|---|
| Chrome | Behind a flag | 120 | Dev mode or enterprise |
| Edge | Not supported | Not available | None |
| Firefox | Not supported | Not available | None |
| Safari | Not supported | Not available | None |
| Safari on iPhone | Not supported | Not available | None |
| Chrome on Android | Not supported | Not available | None |
| Samsung Internet | Not supported | Not available | None |
How a site asks for it
| API | isolated-app:// scheme, Signed Web Bundle .swbn, manifest at /.well-known/manifest.webmanifest with version |
| How access is granted | enterprise |
| What the user sees | Enterprise install |
| Needs a secure context (HTTPS) | Yes |
| Needs a user gesture | No |
| How long it lasts | Per origin |
| How to take it back | Site settings |
| Inside an iframe | Same as top level; cross-origin iframes need a permissions policy where listed |
Typical flow
- Call the API
- Browser applies its access rules
- Page receives the result
Data you get
What comes back: A packaged, signed web app with extra system APIs.
Shape: object
How often: on demand
| Field | Type | Unit | Range | Precision |
|---|---|---|---|---|
signature | string | None | Ed25519 or ECDSA P-256 | Not listed |
updates | string | hours | checked every 4 to 6 hours | Not listed |
Technical limits
- Enterprise or developer mode only
- Strict COOP and COEP and CSP
The story
What it is
A packaged, signed web app with extra power, mainly for managed Chromebooks and companies.
For you
Most people never see these. They are installed by a school or company on its managed devices. They may use special features like raw network access, with admin approval.
For makers
Makers get native like power with web tools. Packaging and signing let the browser trust the app more, so it can access more of the device. It is mostly for enterprise and education.
Where you see it
| Type | Example | Apps |
|---|---|---|
| enterprise | A company ships a remote desktop client as an isolated app, which talks to office servers over raw network connections. | None named |
| education | A school installs a testing app that locks down the device while students take an exam. | None named |
| games | A cloud gaming client could ship as a signed bundle with low level network access for low delay streams. | None named |
| security | A bank sets up a branch kiosk app on managed devices, with strict rules about what code can run. | None named |
| developer | A tool ships a web terminal as a signed app, which can open network ports from the browser. | None named |
| health | A clinic uses a signed app to connect to medical devices on its network. | None named |
| creative | A studio tool uses a packaged app for fast offline file access on managed laptops. | None named |
Risks
- Very powerful
- Needs admin trust
What the platform says
- ChromeOS: Isolated Web Apps. Packaged web apps with a signed bundle and strong security rules, for powerful features such as direct sockets.
Good uses and abuse
Legitimate uses
- Enterprise kiosks
Known abuse
- None
Scores
| Score | Value | Meaning |
|---|---|---|
| Sensitivity | 3 of 5 | How revealing the data is |
| Utility | 3 of 5 | How useful it is to honest apps |
| Friction | 3 of 5 | How much the user has to do |
| Fingerprint bits | Not rated | Rough identifying entropy, when known |
History
- 2023, Chrome 120: IWA developer testing
Sources
How well checked: Based on official documentation.