Skip to content

F8.1: Make Pixel Forge installable and offline-ready #329

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Flow-Fly merged 3 commits into from
Jul 10, 2026
Merged

F8.1: Make Pixel Forge installable and offline-ready #329

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
c661606
feat(pwa): add installable offline shell (#326)
Flow-Fly Jul 10, 2026
c4c311c
feat(pwa): add quiet install action (#327)
Flow-Fly Jul 10, 2026
9c16278
feat(pwa): require confirmation before updates (#328)
Flow-Fly Jul 10, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
39 changes: 39 additions & 0 deletions docs/verification/pwa.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,39 @@
# PWA verification

Use a Chromium browser for the install and service-worker checks. The development server does not register the production service worker, so build and preview the app first.

```sh
npm run build
npm run preview -- --host 127.0.0.1
```

## Install

1. Open the preview URL and wait for the application to finish loading.
2. Open **File** and choose **Install Pixel Forge**.
3. Accept the browser-owned install prompt.
4. Confirm Pixel Forge opens in its own standalone window.
5. Reopen **File** and confirm the install action is gone.

The menu action is intentionally absent when the browser does not expose an install prompt.

## Offline editing

1. Load the preview once while online and wait for the service worker to become active in DevTools **Application → Service Workers**.
2. In DevTools **Network**, select **Offline**, then reload.
3. Confirm the editor shell loads without the network.
4. Draw a visible change and wait for auto-save.
5. Reload again while still offline.
6. Confirm the saved project and drawing return from IndexedDB.

## User-confirmed update

1. Keep the installed or previewed app open as version A.
2. Make a visible local copy change, then run `npm run build` again to create version B while the preview server stays open.
3. In DevTools **Application → Service Workers**, choose **Update** for the active registration.
4. Confirm the non-modal **Update ready** notice appears and the editor does not reload on its own.
5. Choose **Later** and confirm the current session continues unchanged.
6. Ask the service worker to update again, then choose **Restart**.
7. Confirm the current project is saved before the waiting worker activates and version B loads.

To exercise the save-failure path, temporarily make IndexedDB unavailable before choosing **Restart**. Pixel Forge should remain open and explain that the current session stayed open.
5 changes: 3 additions & 2 deletions index.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,9 +2,10 @@
<html lang="en">
<head>
<meta charset="UTF-8" />
<link rel="icon" type="image/png" href="/favicon.png" />
<link rel="icon" type="image/png" href="./favicon.png" />
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
<title>Pixel-Forge</title>
<meta name="theme-color" content="#0d1015" />
<title>Pixel Forge</title>
<link rel="stylesheet" href="./src/index.css" />
<script type="module" src="/src/main.ts"></script>
</head>
Expand Down
Loading
Loading