--- blog
Local-First: Why Your Data Should Stay On Your Device.
Every new app you install comes with the same pitch: sign up, sync your data to our servers, and trust us with everything. Your notes, your screenshots, your files, your entire digital life, floating around in someone else's cloud.
And sure, cloud sync is convenient. Until you're on a plane with no wifi. Or the service goes down. Or they change the pricing. Or they get acquired and shut down. Or, you know, you just don't want some company's employees having potential access to your screenshots of sensitive Slack DMs.
The Problem With Cloud-First Everything
Here's what your screenshot folder probably contains right now: code snippets with API keys you forgot to redact, private conversations, financial statements, medical records, that one password reset screen you screenshotted instead of writing down.
Most productivity apps treat this stuff like it's no big deal. "Don't worry, we encrypt it!" Cool. Who holds the keys? "We do, but trust us." Right.
The cloud-first model made sense when devices were weak and storage was expensive. But your Mac has hundreds of gigabytes free and a processor that can run language models locally. You don't need someone else's server to organize your screenshots.
What Local-First Actually Means
Local-first software isn't just "works offline." It's a design philosophy that puts your device in charge and treats the cloud as an optional sync layer, not the source of truth.
The core principles are simple:
- //Your data lives on your machine first
- //The app works fully without internet
- //You can see, export, and own your files
- //No account required to use your own stuff
- //Privacy isn't a premium feature
This isn't some radical new idea. It's how software worked before SaaS took over. The difference now is that modern local-first apps combine that ownership with the polish and intelligence you'd expect from cloud services.
Why Local-First Is Better UX, Not Just Better Privacy
Privacy matters, but let's be honest, most people won't switch apps just for ideological reasons. The real win with local-first software is that it's simply faster and more reliable.
Instant everything. No loading spinners while data fetches from a server. No "syncing..." status bars. You take a screenshot, the app sees it immediately, you add context, done. All of this happens in milliseconds because nothing leaves your machine.
Works when wifi doesn't. Plane mode, coffee shop with broken internet, VPN acting weird, doesn't matter. Offline-first apps don't have a degraded experience without connectivity because they're built to work that way by default.
Your files stay yours. If the company shuts down tomorrow, your data doesn't vanish. It's right there in a SQLite database you can open with any tool. No export process, no waiting for download links, no panicking about losing years of notes.
No subscription to access your own data. Some apps literally lock you out of your content if you stop paying. With local-first software, the data is already on your device. The worst case is you stop getting updates.
The Local-First Movement Isn't New, But It's Having a Moment
Developers have been talking about local-first principles for years. The Local-First Software essay from Ink & Switch laid out the vision back in 2019. Tools like SQLite, CRDTs, and event sourcing have made it practical to build apps that are both local and collaborative.
What's changed is that the tooling got good enough that small teams can build local-first apps that feel as polished as their cloud-first competitors. You don't need a massive backend team and database infrastructure. You need a solid local storage layer and smart sync when it matters.
The other thing that changed is people are tired of giving every app access to everything. The privacy conversation isn't abstract anymore. We've all had apps get breached, shut down, or pivot to terrible business models. Keeping your data local isn't paranoid, it's practical.
How ohsnp Takes the Local-First Approach
When we built ohsnp, local-first wasn't a marketing angle. It was the obvious architecture for a screenshot organization tool.
Screenshots are inherently sensitive. You're capturing whatever's on your screen at that exact moment. Could be work stuff, personal stuff, stuff you'd rather not have sitting on a random company's S3 bucket. So we made a simple choice: none of it leaves your Mac unless you explicitly tell it to.
Here's how it works:
Everything runs on your device. The app watches your screenshot folder using macOS filesystem events. When a new screenshot appears, a small popup appears in the corner. You can add voice or text context (or just dismiss it). If you choose to analyze it, the AI processing happens locally or through your own API keys. The result gets stored in a SQLite database in your Application Support folder.
No cloud account required. You install it, it works. No sign-up flow, no email verification, no "please sync your data to continue." Your screenshots are already on your machine. Why would we need to move them somewhere else?
Your data is readable. The database is standard SQLite. The screenshots stay exactly where macOS put them. If you want to export everything, open the .db file with any SQLite browser. No proprietary formats, no lock-in.
Privacy by architecture. We can't access your data because we never see it. There's no server to hack, no employee with admin access, no third party processing your screenshots. The app runs entirely on your Mac.
This doesn't mean ohsnp will never have sync. If we add it, it'll be end-to-end encrypted and optional. The local version will always be the full app, not a crippled offline mode.
You Should Own Your Tools
Cloud-first apps trained us to think we need permission to access our own files. That our data should live in someone else's database and we're just renting access.
Local-first software rejects that model. Your screenshots, your notes, your files should be yours. Stored on your device, readable without the app, exportable anytime, private by default.
That's not a radical position. It's just good software design.
ohsnp is a macOS menu bar app that turns screenshots into searchable, AI-organized notes. Everything stays local. No cloud required. Join the waitlist to get early access.
// related posts