Tabbed application mode for PWAs
Work on more than one document at a time with tabs in your Progressive Web App
In the world of computing, the desktop metaphor is an interface metaphor that is a set of unifying concepts used by graphical user interfaces (GUI) to help users interact more easily with the computer. In keeping with the desktop metaphor, GUI tabs are modeled after traditional card tabs inserted in books, paper files, or card indexes. A tabbed document interface (TDI) or tab is a graphical control element that allows multiple documents or panels to be contained within a single window, using tabs as a navigational widget for switching between sets of documents.
Progressive Web Apps can run in various display modes determined by the display property in the web app manifest. Examples are fullscreen, standalone, minimal-ui, and browser. These display modes follow a well-defined fallback chain ("fullscreen" → "standalone" → "minimal-ui" → "browser"). If a browser does not support a given mode, it falls back to the next display mode in the chain. Via the "display_override" property, developers can specify their own fallback chain if they need to.
What is tabbed application mode #
Something that has been missing from the platform so far is a way to let PWA developers offer their users a tabbed document interface, for example, to enable editing different files in the same PWA window. Tabbed application mode closes this gap.
Suggested use cases for tabbed application mode #
Examples of sites that may use tabbed application mode include:
- Productivity apps that let the user edit more than one document (or file) at the same time.
- Communication apps that let the user have conversations in different rooms per tab.
- Reading apps that open article links in new in-app tabs.
Differences to developer-built tabs #
Having documents in separate browser tabs comes with resource isolation for free, which is not possible using the web today. Developer-built tabs would not scale acceptably to hundreds of tabs like browser tabs do. Developer-built tabs could also not be dragged out of the window to split into a separate application window, or be dragged back in to combine them back into a single window. Browser affordances such as navigation history, "Copy this page URL", "Cast this tab" or "Open this page in a web browser" would be applied to the developer-built tabbed interface page, but not the currently selected document page.
Differences to "display": "browser" #
The current "display": "browser" already has a specific meaning:
Opens the web application using the platform-specific convention for opening hyperlinks in the user agent (e.g., in a browser tab or a new window).
While browsers can do whatever they want regarding UI, it would clearly be a pretty big subversion of developer expectations if "display": "browser" suddenly meant "run in a separate application-specific window with no browser affordances, but a tabbed document interface".
Setting "display": "browser" is effectively the way you opt out of being put into an application window.
Current status #
Using tabbed application mode #
To use tabbed application mode, developers need to opt their apps in by setting a specific "display_override" mode value in the web app manifest.
{
…
"display": "standalone",
"display_override": ["tabbed"],
…
}Trying tabbed application mode #
You can try tabbed application mode on ChromeOS devices running Chrome 83 and up today:
- Set the
#enable-desktop-pwas-tab-stripflag. - Install any web app that runs in
standalonemode, for example, Excalidraw. - Pin the app icon to the shelf, right click the icon, and select "New tabbed window" from the context menu.
- Open the app and interact with the tab strip.
The video below shows the current iteration of the feature in action. There is no need to make any changes to the web app manifest for this to work.
Feedback #
The Chrome team wants to hear about your experiences with tabbed application mode.
Tell us about the API design #
Is there something about tabbed application mode that does not work like you expected? Comment on the web app manifest Issue that we have created.
Report a problem with the implementation #
Did you find a bug with Chrome's implementation? File a bug at new.crbug.com. Be sure to include as much detail as you can, simple instructions for reproducing, and enter UI>Browser>WebAppInstalls in the Components box. Glitch works great for sharing quick and easy reproduction cases.
Show support for the API #
Are you planning to use tabbed application mode? Your public support helps the Chrome team prioritize features and shows other browser vendors how critical it is to support them.
Send a tweet to @ChromiumDev using the hashtag #TabbedApplicationMode and let us know where and how you are using it.
Useful links #
- Web app manifest spec issue
- Chromium bug
- Blink Component:
UI>Browser>WebAppInstalls
Acknowledgements #
Tabbed application mode was explored by Matt Giuca. The experimental implementation in Chrome was the work of Alan Cutter. This article was reviewed by Joe Medley. Hero image by Till Niermann on Wikimedia Commons.
