Collaboration
Chrome Kiosk Web App Deployment
Published: 26/08/2025
Updated:
Deploying a Chrome kiosk app starts with the customer journey: the screens people use to check in, make a payment, collect a ticket or complete a self-service transaction. A web application can provide that interface directly in the browser. A progressive web app (PWA) can also add installation and offline behaviour where the application needs them.
A dependable deployment brings that interface together with browser policies, device startup, supported hardware and ongoing fleet operations. The choices differ between Chrome running on Windows or Linux and a managed ChromeOS kiosk. Establish the target platform before choosing an extension or packaging the application.
For on-premises fleets, Satellite remote device management supports Chrome extension installation, upgrades and installation confirmation. It gives the operations team a place to manage the release and follow what the devices report afterwards.
Start with a web app and add extensions where needed
Build and test the kiosk interface as a web application first. Make navigation clear on the actual touchscreen, give users a way to recover from an interrupted session, and decide which tasks can continue when the connection is unavailable. A PWA can cache selected content, but offline payments, identity checks and transaction submission still need explicit application design. Installing a PWA does not make every workflow work offline.
A Chrome extension can accompany the web app when it needs a browser capability that the web platform cannot provide. That decision should follow a specific requirement rather than become a prerequisite for displaying the kiosk interface. Google's Chrome App migration guidance recommends web applications for most cases and describes companion extensions for requirements that need extension APIs.
For a new extension, use Manifest V3 and request only the permissions its functions require. Background work runs in an extension service worker, which can stop when idle and start again for an event. Store durable state and handle reconnection instead of depending on a permanently running background script. Google's service-worker migration guidance explains the lifecycle and manifest changes.
Configure startup for the device platform
On Windows or Linux, configure the kiosk's operating-system session to start the intended browser and application after boot. Set browser policies for the approved content and any required extensions, then verify that those policies apply to the actual kiosk account. Browser presentation, operating-system access and application recovery each need their own configuration. Hiding the address bar or showing a fullscreen page alone does not establish that the device is securely restricted.
Test the complete startup path on the operating-system and Chrome versions you intend to deploy. Check what happens after a power interruption, a browser crash, a network outage and a software update. Include keyboard shortcuts, links that open another window, customer-session cleanup and the authorised maintenance route. The useful acceptance criterion is that the device returns to the intended customer experience and allows support to work through the agreed maintenance process.
Managed ChromeOS devices use a different deployment path. Google's web kiosk guide describes adding a website, PWA or isolated web app in the Admin console, selecting auto-launch and configuring any additional origins the application needs. Companion extensions can be added to the web kiosk there. Confirm the permissions and origins for the trusted application, including any separate identity or service endpoints it uses.
Legacy Chrome Apps are a separate technology from extensions and PWAs. Google is retiring them; its current support timeline identifies ChromeOS 150 as the last regular release supporting Chrome Apps in kiosk mode, with LTS kiosk support through April 2027. An existing Chrome App deployment needs a migration plan. Choose a current web kiosk approach for a new deployment.
Choose the management route around the device platform:
| Device platform | Deployment and management route |
|---|---|
| Windows with managed Chrome | Browser policies for extension installation and updates; Satellite for supported on-premises releases and confirmation. |
| Linux with managed Chrome | Browser policies and the supported extension distribution path; Satellite for supported on-premises releases and confirmation. |
| Managed ChromeOS | Google Admin console for the web kiosk, auto-launch and companion extensions. |
Distribute extensions through a managed update path
If the application requires a companion extension, test it as trusted unpacked code during development, then choose a supported distribution method for the fleet. Chrome Web Store distribution and managed self-hosting have different requirements. Google's extension distribution guidance explains that Windows and macOS self-hosted installations require enterprise policies, while Linux also supports manual installation of packed extensions outside the Store.
For managed Windows and Linux browsers, policies such as ExtensionSettings can specify the extension, its installation mode and its update source. Follow the platform's Windows policy instructions or Linux policy instructions, and confirm the result in chrome://policy. Check the fleet's management eligibility before choosing self-hosting; possessing a signed package does not by itself make every device eligible to install it.
When self-hosting is appropriate, Chrome's packaging process creates the signed CRX package and its private key. Protect that key, retain the extension's identity, increase the version for each release and configure the update manifest. Subsequent packages must use the same signing key. Google's packaging and update reference covers this process. Chrome Web Store-hosted extensions use the Store's packaging and distribution path.
Keep web application releases, extension releases and browser updates in the deployment plan. Test a change on representative devices before rolling it across the estate, and verify the installed version and customer workflow afterwards. Minifying JavaScript and CSS can reduce download size, but measure startup time and resource use on the kiosk rather than assuming a smaller package will solve every performance issue.
Install, upgrade and confirm with Satellite
A fleet needs a repeatable way to introduce an extension, move to a new version and confirm installation on the intended devices. Satellite supports that workflow for on-premises Chrome extension deployments on supported managed devices. Operators can manage the release centrally and follow reported outcomes across the fleet.
Installation starts with the approved extension and the devices that should receive it. Bring the extension into the managed release process and follow the installation outcome for the selected devices. This gives support a clear starting point when a newly commissioned kiosk is missing part of its application.
Upgrades follow the same deliberate approach. Test the next version on representative kiosks, choose the intended devices and follow the rollout. Keep extension changes coordinated with the web application and SDK so that the customer workflow is tested as a whole.
Confirmation gives the team visibility after the release has been sent. Review reported installation results and follow up on exceptions; then check that the kiosk's customer journey works with the intended version. A release being published is an earlier checkpoint than a device confirming installation.
Satellite brings this release workflow together with device status and remote diagnostics. Its security capabilities include software integrity checking, configuration drift monitoring, TPM integration on compatible devices and integration with SIEM workflows. Chrome's installation policies and platform requirements remain part of the deployment design.
Already have a web or mobile app?
If your customers already use a web, Android or iOS app, you may not need a separate kiosk interface at all. Weave, a feature of Azimut SDK, runs that existing app natively on the kiosk and connects it to payment, cash, printer, ID and SIM hardware through the same JSON API. The deployment and release steps above still apply to the kiosk device.
Connect the customer interface to hardware and fleet operations
A browser-based kiosk often needs more than an onscreen form. Receipt printers, scanners, payment terminals and cash-handling devices introduce readiness checks, interrupted operations and physical faults that the customer interface needs to handle. Azimut SDK provides a hardware-agnostic JSON API for supported device families, so application teams can build the customer workflow without writing a separate hardware integration for each model.
For receipt and document printing, design the workflow around a confirmed print outcome and clear handling of paper or device faults. Choose the application's connection to the SDK runtime as part of the deployment design. When a hosted web page calls a local service, verify browser permissions, origin access and authentication on the target environment. Chrome's Local Network Access guidance describes permissions for connections to local and loopback services. Test the intended route before relying on it in an unattended kiosk.
Fleet operation continues after the interface is deployed. Satellite remote device management gives teams a central workspace for device status, resource history, supported diagnostics and application releases across Windows, Linux and Android. Available controls depend on the platform, hardware and permissions. Together, the application, SDK and management workspace help teams follow the customer workflow and investigate device problems while keeping their deployment responsibilities clear.
Related solutions
Where this work fits in the platform.
Try it yourself
Book a demo
See how Azimut SDK works in your self-service environment. We'll walk through your use case, hardware setup, and integration options.
Continue reading
A Smarter Way to Handle Currency Exchange with Azimut
Upgrade currency kiosks with multi-currency, AML, and real-time rate support.
Modernise Legacy Kiosks Without New Hardware
Legacy kiosks fall behind your app. Modernise them with Weave, Azimut SDK and middleware, keeping your hardwar…
Reading ID Chip Data for Kiosk Identity Workflows
Separate document capture, chip access, signature validation and the identity decision when integrating ID rea…