No account, by design
You will never sign up for an OmniFlux app. We argue why \"no account\" is a feature, not a missing one — and how it changes everything downstream.
The promise
You will never see a "Sign up" or "Log in" screen in an OmniFlux product. There is no account to create, no email to confirm, no recovery flow to manage, no "delete my data" button — because there is no data of yours that we hold to delete.
This is a deliberate engineering and product choice, not an oversight. Here is the reasoning.
Why most apps want an account
For most apps, an account is how cloud-side features work: your data is in their database, your settings are in their backend, syncing across devices means uploading to their servers. The account is the key to a server-side store.
Our products do not have a server-side store. The model runs on your device. Your inputs and outputs live on your device. There is nothing to "log in to."
What we give up
- Cross-device sync is harder. We solve it with end-to-end encrypted peer sync over your local network and (opt-in) over iCloud / Drive / Dropbox folders that you already control. Nothing transits our servers.
- Cross-device usage analytics are gone. We do not know how many of you use a feature, and we will earn that signal back the slow honest way — by reading reviews, talking to users, watching what people ask for.
- Login-walled features are gone. Our entire product surface works for a user who installed the app five minutes ago and has not connected anything to anyone.
What we gain
- A trust default. When you do not collect data, you cannot leak it, sell it, get subpoenaed for it, or have it stolen.
- Zero account-recovery support burden. No password resets, no "I lost my email" tickets, no SIM-swap fraud. Our support load looks more like a single-player game than a SaaS.
- Honest pricing. We charge for the app, once. We are not subsidising free tier users with paying ones, and we are not pulled toward dark patterns by a metric that says "free users churn unless we add notifications."
- Long product lifespan. Apps with no servers do not die when the company changes priorities. The local model and the local database keep working as long as the device does.
How sync works
When you opt in:
- Pair devices over your local network with a one-shot 6-digit code (think AirDrop pairing, not OAuth).
- Both devices generate keypairs locally; the public keys are exchanged in the pairing handshake.
- Sync messages are encrypted to the recipient device's public key. Our infrastructure (if any is used as a relay) sees only ciphertext.
- You can revoke a device at any time by removing it from the pair list on the original device.
If you prefer, you can plug your own folder in any cloud drive (iCloud, OneDrive, Drive, Dropbox, a self-hosted WebDAV) and we will write encrypted sync packets there. We never ask for credentials to those services; you point us at a local folder, the platform handles the upload.
"But how will you know what to build?"
By talking to users. By reading reviews. By offering an explicit, opt-in survey now and then. By the slow accumulation of feedback that you would have given an old shareware author in 1996 — which, it turns out, was enough to build very good software.
Want updates like this in your inbox?
No newsletter platform. No tracking. We send a single email per launch.
Subscribe