Install the existing home-server app as a PWA #6

Current status — 2026-10-12

Status: Partially implemented. The existing home-server PWA has a manifest, production service-worker registration, shell cache, and safe-area styling.

Completed code: public/manifest.webmanifest, public/sw.js, and production registration. The service worker excludes API and upload requests; this does not prove installation or safe unavailable-server behavior.

Remaining development and acceptance:

• Provide/check understandable supported-browser installation guidance and a documented suitable HTTPS setup for phone installation.
• Test actual Android-browser installation and standalone launch/navigation, icons, safe areas, and both themes.
• Verify unavailable PC/server/network messaging and failed writes; cached UI must not imply a successful save.
• Add real browser coverage for these cases through Add real UI interaction tests for core receipt workflows #27.

Evidence boundary: Current web checks/build pass and PR #30 includes limited review-layout smoke checks, but those checks do not install or exercise the PWA. The durable APK is a different native runtime and does not satisfy this issue. Keep open.

Goal

As a user, I want to install Itemly on my Android phone and open it from the home screen like an app. The existing home server is still required for data operations.

Acceptance criteria

• Provide a valid web app manifest with name, short name, theme, and icons.
• Allow installation from a supported browser.
• Support standalone launch and navigation without browser chrome.
• Account for display cutouts and safe areas.
• Show understandable installation guidance where supported.
• Clearly explain when the server or local network is unavailable.
• A cached app shell may appear offline, but writes must fail safely without implying success.

Important limitation

Full PWA installation and modern browser capabilities generally require HTTPS on the phone. Document a suitable local or self-hosted HTTPS approach without bypassing certificate warnings.

Out of scope

• Google Play publication
• Automatic cloud synchronization
• Background receipt-image uploads
• Phone-only operation without the home server; see Design phone-only Android storage architecture #12 and Store receipts and images persistently on Android #13

Verification

Check the manifest and service worker, Android installation and standalone launch, and unavailable-server behavior.