PWA Installation

What it is

The Progressive Web App path keeps the MdWrk client in the web platform, but lets supported browsers install it as a dedicated app window.

Typical install flow

  1. Open the MdWrk site in a PWA-capable browser.
  2. Use the browser's install action from the address bar, app menu, or share sheet.
  3. Launch the installed app from its icon or application list.

Best fit

  • frequent daily writing
  • a focused app window without full browser chrome
  • users who want updates delivered through the browser-managed install flow

Update behavior

PWA updates are delivered through the normal web app update lifecycle. When a new build is ready, the client can prompt you to refresh into the updated version.

Storage and backup

PWA mode still uses browser-managed local storage. Installability does not turn the app into a server-backed product, so exports and backups are still your responsibility.

When to choose another path

Choose browser use when you do not want to install anything. Choose local setup when you need a repo checkout, local build scripts, or self-hosted control. Choose standalone modules when you need package-level reuse instead of the full workspace shell.

Frequently Asked Questions

What will I learn from PWA Installation?

The Progressive Web App path keeps the MdWrk client in the web platform, but lets supported browsers install it as a dedicated app window.

Who should read PWA Installation?

Read this page if you need practical MdWrk guidance for pwa installation, including the relevant workflow, product surface, and follow-up documentation paths.