What is Local-First Software?

Local-first software represents a fundamental shift in personal and professional computing. Coined by Martin Kleppmann, Adam Wiggins, Peter van Hardenberg, and Mark McGranaghan in their seminal 2019 research paper Local-first software: You own your data, in spite of the cloud, this paradigm bridges the responsiveness and ownership of classic desktop applications with the collaborative benefits of modern networks.

In a traditional cloud application (such as Google Docs, Notion, or Slack), the remote server is the primary authority. If the network connection drops, latency spikes, or the vendor shuts down, users lose access to their work. In local-first software, your device’s local filesystem or embedded database is the primary system of record. Network activity is strictly secondary, asynchronous, or entirely optional.

The seven foundational ideals

The local-first philosophy outlines seven core tenets designed to return agency to computer users:

1. No spinners: Read and write operations complete in sub-millisecond local RAM and disk cycles, bypassing round-trip network latency.
2. Your work is not trapped on one device: Data can be backed up or transferred across personal devices without vendor gateways.
3. The network is optional: Every core feature—searching, editing, reading, linking, and organizing—functions perfectly while disconnected.
4. Seamless collaboration: When sharing is required, conflict-free replicated data types (CRDTs) or peer-to-peer protocols resolve divergence gracefully.
5. Software longevity: Documents created today remain readable decades from now, even if the application developer dissolves.
6. User data ownership: Files reside in user-accessible storage locations using open, standardized data formats.
7. Security and privacy by default: Because information does not traverse centralized vendor servers, remote surveillance and data breaches are architecturally prevented.

Architectural comparison: Cloud SaaS vs Local-First

The trade-offs between traditional cloud-hosted software and local-first architecture are profound:

Architectural Dimension	Traditional Cloud SaaS	Local-First Architecture
Primary System of Record	Remote PostgreSQL/MongoDB	Local Mac NVMe / SSD disk
Offline Latency	Blocked or degraded functionality	Sub-millisecond instant execution
Data Format	Proprietary JSON / relational blobs	Standard UTF-8 plain text / Markdown
Vendor Dissolution Risk	Complete loss of customer data	Permanent local data retention
Privacy Vulnerability	Exposed to cloud subpoenas / leaks	Air-gapped on local hardware

Local-first computing in Oyma on macOS

Oyma adheres rigorously to local-first principles. When you install Oyma on macOS, it asks you to select a folder on your Mac—such as ~/Documents/Notes or an existing Obsidian vault.

From that moment forward:

• Notes are written directly as standard .md files on your disk.
• Meeting recordings are captured via ScreenCaptureKit and transcribed on-device via Whisper.
• Search indexing utilizes an embedded SQLite FTS5 index located inside the application cache.
• The application makes zero telemetry calls and requires no user account or login token.

You retain complete custody of your intellectual output forever.