Local-first software
Local-first software
One-line summary: Architecture where the device replica of user data is authoritative and servers (if any) are relays or secondary copies — one cited home for a user-owned interest graph.
The insight
Cloud recs apps make the server the store of record. Local-first inverts that so the user can read and write the graph offline; sync (often via CRDTs) is background. Grokipedia’s PKB page lists a related hosting menu: local files, embedded/graph databases, or client–server (including hybrid local-cloud). Solid is a different ownership invert — pod-primary, apps interchangeable — not the same as device-primary. From 2026-08-21-autoresearch-best-architecture-for-a-rec-system-web-app.
The chain
Device or user-pod replica is primary for a user-owned graph; servers are relays. That ownership invert is one cited serving-layer home for the interest graph, not a ranked stack vs Solid or a hosted PKB.
Canonical: user-owned-graph-to-quota-aware-youtube-serving.
Evidence
- From 2026-08-21-autoresearch-best-architecture-for-a-rec-system-web-app: “we treat the copy of the data on your local device … as the primary copy. Servers still exist, but they hold secondary copies.”
- From 2026-08-21-autoresearch-best-architecture-for-a-rec-system-web-app: “When data is stored on ‘someone else’s computer’, that third party assumes a degree of control over that data.”
- From 2026-08-21-autoresearch-best-architecture-for-a-rec-system-web-app: CRDTs “can sync their state via any communication channel (e.g. via a server, over a peer-to-peer connection, by Bluetooth … or even on a USB stick).”
- From 2026-08-21-autoresearch-best-architecture-for-a-rec-system-web-app: PKB deployments are “local file-based systems, embedded or relational databases, and client-server architectures”; hybrid options “store primary data locally with periodic syncing.”
- From 2026-08-21-autoresearch-best-architecture-for-a-rec-system-web-app: Solid SAI — applications “request typed access rather than ingesting a captive database.”
Contradictions / tensions
- Local-first (device primary), Solid (pod primary), and hosted PKB (server primary) are cited as different answers, not a ranked stack. None is tested as the store behind a YouTube-first recs UI.
- On-device ranking (on-device-recommender) is a compute placement, not the same claim as local-first data ownership.