# Local-first software

> Software that keeps the primary copy of your work on your device while treating network services as optional helpers.

## What it means

Neutral explainer of the concept, distinct from the product-specific /blog/local-first-explained (link it for how PlexiDesk does it). Source, verified: Kleppmann et al., ‘Local-first software’, Ink & Switch, Onward! 2019 (https://www.inkandswitch.com/essay/local-first/), and its seven ideals quoted exactly (“No spinners: your work at your fingertips”, “Your work is not trapped on one device”, “The network is optional”, “Seamless collaboration with your colleagues”, “The Long Now”, “Security and privacy by default”, “You retain ultimate ownership and control”). Explain offline-first versus local-first, and CRDTs in one paragraph . Related: single-source-of-truth, second-brain, bring-your-own-key.

## A practical example

You edit a document on a flight with no connection because the working copy and editor are already on your computer.

## Put it into practice

- Name the concrete situation before applying the label. Local-first software is useful only when it changes a choice, boundary or next action.
- Make the state visible: write the owner, time, source or stopping condition down instead of relying on memory.
- Review what happened. Keep the part that reduced ambiguity and change the part that added ceremony without helping the work.

## How it relates to Plexii



## Sources

- [Kleppmann et al.: Local-first software](https://www.inkandswitch.com/essay/local-first/)