Blog
How we build P-Pass: design trade-offs and engineering notes on backing up phone photos to a computer at home.
- Auto-Updates Without an App Store: Tauri and Android APKs
- Android Battery Drain from Idle QUIC (iroh) Endpoints: 300mAh to 30mAh
- Your phone is full, and the photos are the hard part
- RPC timeouts, 202-style polling, and a tokio broadcast race in phone-to-desktop backup
- NAT traversal field test: sending photos from a 5G phone to a computer at home
- Why our QUIC connection cache still did five handshakes for five photos
- Why we rebuilt our photo backup core around a per-photo ledger
- What macOS FSEvents actually reports when you move and delete files in Finder
- Android content triggers without gaps, using JobScheduler instead of WorkManager
- Why a failed iroh-blobs FsStore::load hangs instead of returning an error: a tokio runtime self-deadlock
- How we designed the P-Pass app icon, from first sketch to a size-specific icon set
- Why we're building photo backup for families
- How P-Pass knows a photo is already backed up
- Connect first, get faster later, which is why P-Pass runs on iroh