Best practices for PWAs

This article lists best practices to make your PWA a great application for your users. When users install applications, they have certain expectations of what these applications can do, such as work offline, integrate deeply into the operating system, or perform non-trivial computing tasks.

Read the best practices on this page to learn to make your PWA look and feel like what users expect.

This page assumes that you already have a PWA. To learn more about building a simple PWA first, see Get started with Progressive Web Apps.

Provide a custom installation

Your app can already be installed using the App available button in the browser address bar if you follow the steps in Get started with Progressive Web Apps.

A custom installation experience, in the app user interface, can be more obvious to your users and lead to more installations.

To create a custom installation experience, use the beforeinstallprompt event and provide your own installation button in your app.

To see a code example of the beforeinstallprompt event, check the PWAmp demo app source code. To test the custom installation, open PWAmp, then click More tools (...) > About > Install app in the app.

Submit to app stores

Many users will look for your app on their device's app store. Downloading from an official app store provides a trustworthy and familiar experience for your users.

You can publish your PWA to the Microsoft Store for Windows, the App store for iOS, or the Play Store for Android, by using PWA Builder.

To learn how to use PWA Builder and publish to the Microsoft Store, see Publish a Progressive Web App to the Microsoft Store.

Create a great app icon

Many users find apps on their devices by their icons. To help users find your app more easily, choose a recognizable icon, make sure it stands out, and make sure that it adapts to the devices your app is installed on.

On Windows, your app icon appears in many places such as the taskbar, the Start menu, or the Alt+Tab task switcher. Provide multiple image sizes to ensure your app icon is easily recognizable in these places.

To learn which image size are needed on Windows, see Icon image sizes in Define icons and a theme color.

Use a standalone app window

Native applications have their own dedicated windows. PWAs can define how they appear in the host operating system.

To display your PWA in a standalone window with no browser navigation user interface, use the display member in your web app manifest file, and set it to standalone.

If your app has several HTML pages, make sure users can go between the pages using buttons or links within your app. Use the minimal-ui value of the display manifest member to let users go between pages using previous and next buttons rendered by the browser in your app title bar.

To create a more immersive, native-like experience, desktop PWAs can also choose to hide the default operating system title bar and display their own content instead. Displaying content where the title bar normally is can help PWAs feel more like native apps. Many desktop applications, such as Visual Studio Code, Microsoft Teams, and Microsoft Edge already do this.

To learn how to replace the title bar, see Display content in the title bar.

Integrate in the operating system

Users expect installed applications to integrate with the host operating system in some way.

Your app can provide a more familiar, engaging, and seamless experience by using operating system integration features such as shortcuts, sharing between apps, badging, file handling, or link handling.

Shortcuts

Shortcuts make it possible to define direct links to your app functionality by right-clicking the app icon.

See Define app shortcuts.

App sharing

PWAs can share content to other apps, and receive content from other apps, via the operating system's share dialog.

See Share content with other apps.

Icon badges

PWAs can display status badges on their app icons to alert users of the presence of new content in the app.

See Display a badge on the app icon in Re-engage users with badges, notifications, and push messages.

File handling

You can register your PWA to be a file handler for certain file types.

Use the PWA file handler feature to automatically launch your app when certain file are opened by the user in the operating system.

See Handle files in Progressive Web Apps.

Link and protocol handling

Register your app is a link or protocol handler to automatically launch your app when certain links are used in other applications.

See Handle links to your Progressive Web Apps and Handle protocols in Progressive Web Apps.

Widgets

Create your own app widgets to display in the operating system widget dashboard such as the Windows 11 Widgets Board.

See Build PWA-driven widgets.

Support offline scenarios

When connected to a slow or unreliable network, or even with no internet access, installed applications can usually still be opened and used. Users of installed applications expect them to continue working under these conditions. They also expect the network-dependent parts of an application to gracefully handle the lack of connection with a custom message and local caching capabilities.

To improve retention, use the service worker's Fetch and Cache APIs, and local data storage access and provide a good offline experience to your users.

You can provide a good offline experience in several steps:

1. Cache all the static resources your app needs to start, display content, and let users perform the most common tasks.
2. Redirect to a custom offline page for the pages that can't be cached.
3. Gracefully handle the tasks of your app that can't be used with no internet access.
4. Implement advanced scenarios such as letting users download data for offline viewing.

To learn more, see Use Service Workers to manage network requests.

Store data locally

To provide a rich and fast experience to your users, use the different persistent data storage options that are available to PWAs, such as:

• Cache storage, to store static resources for your app.
• Local and Session storage, to store small amounts of user data.
• IndexedDB, to store larger, structured, user data.
• File System Access API, to store files on disk.

To learn more, see Store data on the device.

Use advanced capabilities

Installed apps typically perform advanced computing scenarios that websites usually don't support.

To provide an app-like experience, use advanced web capabilities such as:

• Hardware access with the Web Bluetooth, Web USB, or Web NFC APIs.
• Clipboard access with the Clipboard API.
• Device contacts integration with the Contact Picker API.
• Rich media interactions with Canvas, WebGL, or WebAudio APIs.
• Safe and trusted authentication and payment with WebAuthn and Payment Request APIs.
• Non-trivial computing tasks with WebAssembly.
• Reading and writing to files with the File System Access API.

Ensure your app's most important tasks can be done across all browsers and devices. See Test on multiple browsers and devices.

Make your app look and feel like a real app

Users install apps on their devices to achieve specific tasks, and they have certain expectations about how these tasks are presented in the user interface and how they integrate in the host operating system.

To let your users achieve your app's most important tasks easily and in a familiar way, make design choices such as:

• Don't use a big header area like websites do for navigation to other pages. Use a menu metaphor instead.
• Don't use a big footer area like websites do for more links and information.
• Use the system-ui font to make your content feel more native and load faster.
• Use less links, and prefer bigger hit targets.
• Support the operating system's light and dark themes by using the prefers-color-scheme CSS media feature.
• Provide a background-color and theme-color in your web app manifest to customize the application window.
• Focus on the most important tasks, de-clutter de content, and streamline the user interface.
• Re-organize the user interface based on the device's form factor, by using CSS grid, Flexbox, Media queries, and Responsive images.
• Improve perceived performance by registering user interactions immediately.
• Consider using skeleton screens if rendering the next screen takes time.

Test on multiple browsers and devices

With Progressive Web Apps, you deliver an app for all devices, from one codebase. To make sure your app works everywhere, test it on multiple browsers, operating systems, and devices.

Make sure the most important scenarios of your app work everywhere, and progressively enhance the experience on supporting devices.

To test your app in multiple environments, consider the following techniques:

• Cross-browser testing.
• Emulate and test other browsers from Microsoft Edge, by using DevTools.
• Create a remote debugging session on Windows or Android.
• Test and automation in Microsoft Edge to automate your testing.
• Test on virtual machines.

Support deep linking

To improve discovery and sharing of your app through the web and social media, route each page of your app to a unique URL and support deep linking.