Documentation versions (currently viewingVaadin 23)

You are viewing documentation for Vaadin 23. View latest documentation

Turning a Vaadin Flow Application into an Installable PWA

Learn how to define a custom offline page and enable installation on supported devices.

In this chapter, you turn the completed Customer Relationship Management (CRM) application into a Progressive Web Application (PWA), so that users can install it.

What’s a PWA?

The term “PWA” is used to describe modern web applications that offer a user experience similar to a native application. PWA technologies make applications faster, more reliable, and more engaging. PWAs can be installed on most mobile devices and on desktop when using supported browsers. They can even be listed in the Microsoft Store and Google Play Store. You can learn more about the underlying technologies and features in the PWA configuration documentation.

Two main components enable PWA technologies:

  • ServiceWorker: a JavaScript worker file that controls network traffic and enables custom cache control.

  • Web application manifest: a JSON file that identifies the web application as an installable application.

Generating PWA Resources

Vaadin provides the @PWA annotation, which automatically generates the required PWA resources.

Add the @PWA annotation on as follows:

@PWA( // (1)
    name = "Vaadin CRM", // (2)
    shortName = "CRM" // (3)
public class Application extends SpringBootServletInitializer implements AppShellConfigurator {

    public static void main(String[] args) {, args);

  1. The @PWA annotation tells Vaadin to create a ServiceWorker and a manifest file.

  2. name is the full name of the application for the manifest file.

  3. shortName should be short enough to fit under an icon when installed, and shouldn’t exceed 12 characters.

Customize the Application Icon

You can override the default icon by replacing src/main/resources/META-INF/resources/icons/icon.png with your own 512px × 512px PNG icon.

You can use your own icon, or save the image below, by right-clicking and selecting Save Image.

example icon

Customize the Offline Page

Vaadin creates a generic offline fallback page that displays when the application is launched offline. You can make your application appear more polished by replacing this default page with a custom page that follows your own design guidelines.

Use the code below to create offline.html in the META-INF/resources folder:

<!DOCTYPE html>
<html lang="en">
    <meta charset="UTF-8"/>
    <meta name="viewport" content="width=device-width, initial-scale=1.0"/>
    <meta http-equiv="X-UA-Compatible" content="ie=edge"/>
    <title>Offline | Vaadin CRM</title>
        body {
            display: flex;
            flex-direction: column;
            align-items: center;
            font-family: sans-serif;
            color: #555;

        .content {
            width: 80%;

        .offline-image {
            width: 100%;
            margin: 4em 0px;

<div class="content">
    <img src="./images/offline.png" alt="VaadinCRM is offline" class="offline-image"/>
    <h1>Oh deer, you're offline</h1>
    <p>Your internet connection is offline. Get back online to continue using Vaadin CRM.</p>
    window.addEventListener('online', () => window.location.reload()); // (1)
  1. The JavaScript snippet reloads the page if the browser detects that it’s back online.

Add the following image (or use one of your own) to the META-INF/resources/images folder and name it offline.png.

example offline image

Make the files available offline by adding them to the @PWA annotation in Application as follows:

    name = "VaadinCRM",
    shortName = "CRM",
    offlineResources = { "./images/offline.png"} // (1)
  1. offlineResources is a list of files that Vaadin makes available offline through the ServiceWorker.

Restart the application. You can now install the application on supported browsers.

Testing the Offline Page

Shut down the server in IntelliJ and refresh the browser (or launch the installed application). You should now see the custom offline page.

custom offline page

In the next chapter, you add both unit tests and in-browser tests to the application.

migration assistance

Download free e-book.
The complete guide is also available in an easy-to-follow PDF format.

Open in a
new tab
export class RenderBanner extends HTMLElement {
  connectedCallback() {

  renderBanner() {
    let bannerWrapper = document.getElementById('tocBanner');

    if (bannerWrapper) {

    let tocEl = document.getElementById('toc');

    // Add an empty ToC div in case page doesn't have one.
    if (!tocEl) {
      const pageTitle = document.querySelector(
        'main > article > header[class^=PageHeader-module--pageHeader]'
      tocEl = document.createElement('div');

      pageTitle?.insertAdjacentElement('afterend', tocEl);

    // Prepare banner container
    bannerWrapper = document.createElement('div'); = 'tocBanner';

    // Banner elements
    const text = document.querySelector('.toc-banner-source-text')?.innerHTML;
    const link = document.querySelector('.toc-banner-source-link')?.textContent;

    const bannerHtml = `<div class='toc-banner'>
          <a href='${link}'>
            <div class="toc-banner--img"></div>
            <div class='toc-banner--content'>${text}</div>

    bannerWrapper.innerHTML = bannerHtml;

    // Add banner image
    const imgSource = document.querySelector('.toc-banner-source .image');
    const imgTarget = bannerWrapper.querySelector('.toc-banner--img');

    if (imgSource && imgTarget) {