What "Local-First" Actually Means (And What It Doesn't)
Local-first has been stretched to mean native, offline, private, free, and open source, which are five different things. Here is the one test that actually separates local-first software from everything else, and the misreadings worth dropping - including what it costs you.
A phrase that stopped meaning anything
The label local-first is plastered across every landing page that does not sell a subscription web app. The phrase has been stretched so thin it barely covers its own marketing. People read the term and take it to mean native, offline, private, free, or open source. Those are five entirely separate properties. A piece of software can possess any combination of them. A web app can be entirely free to use. A native application can be a bloated wrapper that costs money and tracks your clicks. A tool can be open source while still demanding a continuous internet connection to function. These concepts get tangled up because people want a single word that means good software. That is a vibe, not a standard. We need a test that separates software you control from software that controls you.
The test: what breaks when the company disappears
Ask one question of the software you use. What are you left holding if the company goes dark tomorrow? That is the test. If the answer is an export you have to request from a server, or a proprietary database file that nothing else can parse, the tool was never local-first. Local-first means your data lives in files on your machine. It means the actual computing work happens on your own hardware, using your own processor and memory. The files are saved in a format you can open without the original vendor. If a company folds, goes bankrupt, or gets acquired by a private equity firm, your files stay exactly where you left them. You double-click the file, something else opens it, and you get back to work. If you hold the data and the means to read it, you pass the test.
It does not mean the app never touches the network
Opening a network socket is not a sin. Some software is entirely about the network and would be pointless without it. NitroNet monitors your network speed, runs pings, and inspects traffic locally. FlightTrack pulls live air traffic down and paints it across a 3D globe on your desktop. TickerBar puts live stock, ETF, and crypto prices right in your menu bar. They touch the network constantly because the network is the material they work with. Then there is ChatCafe. It handles peer-to-peer LAN chat with text, files, and games. The peers sit entirely on your own local network. No server holds the conversation. The distinction matters. Touching the network to do a job is fine. Depending on someone else's server to own your work is the failure condition.
It does not mean "native", and native does not mean it
People use these two words interchangeably. They are completely independent. A native application can be lightning fast, beautifully designed, and still lock your data in a proprietary cloud sync engine that you cannot bypass. An Electron app can eat a gigabyte of memory just to show a blinking cursor, yet write plain text files to your local disk that any basic text editor can open. Being fast and being yours are different properties entirely. Native development tells you how the interface was drawn on the screen. It says absolutely nothing about who owns the underlying data. If you want to see how that plays out in practice, look at how different note apps behave. A fast app that holds your files hostage is still a hostage situation.
The format is the exit
A file on your own disk is not enough on its own. If the bytes inside it are a proprietary format only one program can read, you are holding a locked box.
Look at NoteCafe. Every note is a plain text file on your computer, sitting in folders you control. Point another editor at that directory and it reads them. No database required. The same rule applies to DocCafe opening and editing standard .docx files offline.
A format other software already understands makes leaving possible. That forces an app to keep earning its place. The format is your exit door.
What it costs you
Local-first hands responsibilities back to you. Backups are yours now. A file sitting on one disk is exactly one physical disk failure away from being gone forever. If you spill water on your keyboard, and you have not copied that data somewhere else, the work disappears with the hardware. You might keep photos in a password-locked encrypted vault like PrivateMedia, but managing the physical backups for that vault is your job entirely. Syncing between your own machines is work you have to arrange yourself, whether that means setting up a local network share or plugging in an external drive. Collaboration is simply harder. You cannot just send a link to a shared web document and watch three people type at the same time. You are trading convenience for absolute control, and control takes effort. These are real, tangible costs. Anyone who tells you otherwise is selling something.
The next time you download a tool, find exactly where it saves your work. Disconnect your internet, close the application, and try to open that file with a completely different program. Ask yourself what happens to that data if the developer closes their doors next week. If your files stay yours, and something else can open them, the tool passes the test. Our whole menu is built for software that answers that question the same way.