Summary
Two related problems with the invite web page (https://<relay>/invite/<code>) when opened on a phone — the most common way a mobile invitee first touches Buzz:
- Blank render on mobile browsers. The SPA serves 200 with all assets loading, but there is no mobile invite landing — recipients see an empty page. (Self-hosted relay,
ghcr.io/block/buzz:main 2026-07-28; observed on iOS Safari.)
- Download links point to GitHub releases instead of the app stores. The platform-detection helper classifies all mobile user agents as
unknown, so the download button falls back to https://github.com/block/buzz/releases — desktop binaries — even though the mobile app is published on both stores:
Non-technical invitees (family members, employees) tap an invite, see a blank page, find their way to a GitHub releases list, and stall.
Suggestion
- A minimal mobile invite landing: app-store badges by UA + "already have the app? open this invite in Buzz" deep-link/copy affordance.
- Store URLs in the download-platform helper for iOS/Android UAs.
Workaround we deployed (self-hosted)
A UA-based redirect endpoint in front of the relay (/get → App Store / Play Store / GitHub by user agent) plus rewriting the bundle's release-page links to it. Works, but it's a patch that must be reapplied on every image upgrade — store links upstream would fix it for everyone.
Summary
Two related problems with the invite web page (
https://<relay>/invite/<code>) when opened on a phone — the most common way a mobile invitee first touches Buzz:ghcr.io/block/buzz:main2026-07-28; observed on iOS Safari.)unknown, so the download button falls back tohttps://github.com/block/buzz/releases— desktop binaries — even though the mobile app is published on both stores:Non-technical invitees (family members, employees) tap an invite, see a blank page, find their way to a GitHub releases list, and stall.
Suggestion
Workaround we deployed (self-hosted)
A UA-based redirect endpoint in front of the relay (
/get→ App Store / Play Store / GitHub by user agent) plus rewriting the bundle's release-page links to it. Works, but it's a patch that must be reapplied on every image upgrade — store links upstream would fix it for everyone.