Mobile capture
Send a thought into HeapFile
Captures in this demo stay in the browser on this device. Cloud sync requires a configured service, a HeapFile account, explicit sign-in, and entitlement checks.
HeapFile Mobile
This browser surface stores quick captures on this device and shows selected recall and desktop handoff. Native iOS and Android distribution follows store approval; account sign-in and cloud-backed features use entitlement checks through heapfile.com.
Mobile capture
Captures in this demo stay in the browser on this device. Cloud sync requires a configured service, a HeapFile account, explicit sign-in, and entitlement checks.
Queued locally
Cloud-backed mobile features use your HeapFile account. This demo stores captures locally; Premium cloud sync and smart handoff require deployed services and paid entitlement checks.
Selected brain items and source-backed reminders require configured services. Sensitive local-only desktop memory remains opt-in for cloud sync.
Capture notes and links in this browser. File and voice capture depend on a supported client; preparing captures for desktop requires a configured handoff path.
Desktop handoff requires a configured relay. Desktop remains the place for local MCP and browser-backed work automation.
Honest parity line
Phones are great for capture, recall, and approvals. Desktop is still required for local stdio MCP, local browser profiles, desktop app automation, and full organization connector workflows.
Browser capture
Local browser capture is available now. Account creation stays on heapfile.com. Native app distribution begins after Apple and Google approval, and cloud services remain account-entitled.