![Adriana Jara](https://web.dev/images/authors/ajara.jpg) Adriana Jara [X](https://twitter.com/tropicadri) [GitHub](https://github.com/tropicadri) [LinkedIn](https://www.linkedin.com/in/adrianajara) [Mastodon](https://hachyderm.io/@tropicadri)
Installed platform apps can be launched even when offline. In this situation they often include a page letting the user know internet access is not available. Some developers even create a full set of features that can be used while offline. With web apps, the capability to work offline is more recent; it became possible with the launch of the [Service Worker API](https://developer.chrome.com/docs/workbox/service-worker-overview). Also, when websites became installable, PWA added a [requirement](https://web.dev/articles/install-criteria) to register a service worker and implement its `fetch()` method in order for a web app to be installable. The idea was to incentivize developers to provide their users at least a notice that the app couldn't be used at the moment. Now developers won't need to do anything to get a default offline page. From Chrome 109 on Android, the browser will automatically generate a page that lets the user know when they are offline. If the app doesn't implement a custom offline experience, when the user is offline, the default offline page uses the app's icon and simple **You are offline** message. Like the example. ![The default offline page for an example web app, where the logo is a pink circle and two plus signs, and it includes the message 'you are offline'.](https://developer.chrome.com/static/blog/default-offline/image/the-default-offline-page-064a704283b77.png) The option to create your own custom offline page is still available. The following video demonstrates how to serve your custom page, using Workbox, with a single line of code. [Video](https://www.youtube.com/watch?v=M7gQg9JojGE) This feature is available on Android (Chrome 109) and desktop environments (Chrome 110). [Share your feedback](https://forms.gle/PnrpAtgGgvQ2jVof6).