What FrameTwin means by local-first capture
How the FrameTwin companion website explains local-first dual-format recording without inventing a backend, sync system, or cloud recording feature.
FrameTwin's public writing stays tied to shipped local-first capture and recovery behavior.
FrameTwin’s V1 product stance is local-first. The recording workflow should not depend on a network request, account, sync service, or cloud storage backend.
The website is not the recording system
This Cloudflare Worker serves public pages, FAQ, privacy information, support content, RSS, and lightweight /v1/* protocol routes.
It does not store recordings. It does not run purchase verification. It does not create accounts.
Why that matters
Creators need capture to keep working under bad network conditions. The app should be able to record, save, and recover locally because the important moment might not wait for a backend.
What can come later
A future backend could support account features, support intake, purchase verification, or optional sync. Those are Phase 2 choices, not V1 assumptions.