Local-first starts with knowing where your data lives
Separate desktop-local storage, cloud copies, mobile capture and AI execution so that cross-device use has clear expectations.
Separate desktop-local storage, cloud copies, mobile capture and AI execution so that cross-device use has clear expectations.
Before putting material into a content tool, ask where it is stored. Then ask what happens on another device and what an AI task sends to which service. These need separate answers.
DraPub's current desktop app uses Electron; mobile uses Expo and React Native. Earlier descriptions of a unified Tauri client are outdated. This revision explains the current data boundaries. Check Downloads for actual release availability.
Desktop-local business material stays on the device, with offline startup. Signing in does not automatically upload its contents to a cloud workspace.
That choice also requires backups. Signing in on another computer should not be expected to retrieve files stored only on the old one. Sign-out and local data deletion are different operations.
Cloud workspaces use cloud data as the authority and keep a synchronized desktop copy. When connectivity is interrupted, inspect synchronization state. Being able to see a local copy does not prove the latest changes reached another device.
Mobile connects to cloud workspaces. The native app can stage captured material, including files received through system sharing. This inbox supports capture and submission; it does not hold a full desktop local workspace.
After saving something offline, check that it reached the destination when connectivity returns. Check for unsubmitted local captures before changing phones.
Native mobile sessions use secure system storage. Mobile web uses the current tab's session storage. Neither should be confused with the desktop SQLite session.
Local storage does not imply offline inference. A desktop AI tool may use an online model, and DraPub Cloud uses the references supplied to its task. Web and mobile can use available cloud execution or registered remote nodes without starting desktop runtimes inside the browser or phone.
Check data location, execution option and reference scope separately. See Workspaces and Device data boundaries.
Q: Does local-first mean every AI request works offline?
**A: ** Data storage and AI execution are separate choices. A local tool may call an online model. Review the references supplied to a task before using cloud services.
Q: Can signing in on another computer restore a local workspace?
**A: ** Signing in alone does not migrate the original computer’s local data. Confirm its location and back it up before switching devices. For online workspaces, check that recent content has synchronized.
Q: How does the mobile offline inbox differ from a desktop local workspace?
**A: ** The mobile inbox temporarily holds captured items, which need confirmed submission to an online workspace. A desktop local workspace stores business data on that computer. Their storage scopes differ.