Chrome 128 brings new capabilities that change PWA install surfaces
Practical checklist for developers shipping PWAs targeting Chrome 128+ on desktop and Android.
Why this matters for OpenPWA listings
Chrome 128 updates several web platform capabilities that PWAs rely on for native-like behavior after installation. These changes affect file associations, protocol handlers, and window controls.
What changed in Chrome 128
- Enhanced File System Access API integration with OS file pickers
- Improved protocol handler registration for custom URL schemes
- Refined display-override options for desktop window controls
OpenPWA checklist for Chrome 128 readiness
- Test file association declarations in manifest on Chrome 128 beta
- Verify protocol handler registration survives install and update flows
- Check that window-controls-overlay works with new display mode combinations
- Audit permission prompts for file and protocol features
- Update screenshots in app listings to reflect new native surfaces
Source-backed facts
According to Chrome for Developers release notes and MDN documentation on File System API and Protocol Handler Registration, these capabilities are now more stable across desktop and Android.
Next step for publishers
Run targeted tests on Chrome 128 beta channels before updating production PWAs. Update your OpenPWA marketplace listing metadata to highlight native integration depth.