The concept.
NeoDrop explores what file storage looks like when your own hardware is the cloud: a NAS-backed storage and synchronisation experience where privacy and ownership aren't subscription features, they're the architecture. The product concept questions whether a Dropbox replacement needs an intermediated cloud at all.
Desktop-first, menu-bar-level small.
Documented development in October 2026 covers product identity and the desktop experience, with a focus on macOS menu-bar design considerations: a tool that lives a click away, stays out of the way while idle, and earns its place by being fast with the common action.
What's real, prototyped and planned.
This is concept development, not a released product. The work documented so far covers product identity, the menu-bar interaction direction and installer packaging exploration. Synchronisation behaviour at production quality remains planned rather than shipped — and that distinction matters: it's honest product design, not a brochure about a product that doesn't exist yet.
Why NAS-first, anyway.
The premise: households and small studios already own a NAS, or are one cloud-sync subscription away from buying the storage they already have. Pointing synchronisation at a NAS the user controls keeps data local, keeps costs flat, and keeps the escape hatch — your files are on a drive you can walk to.
That reframes the product question. Not “how do we keep subscription pricing sensible?” but “how good can synchronisation feel when the hardware is already there?” — speed, conflict handling and confidence become the competition, not price.
The hard parts, named early.
Exploration was honest about the difficulties: conflict resolution when two devices edit the same file offline, sync-state clarity when a device has been asleep for days, and the trust problem of showing exactly what has and has not arrived. These are the problems that make or break storage products, and they are interface problems as much as protocol problems.
Prototyping exists precisely to ask such questions early — the answers will define whether a concept graduates into something worth shipping.
The workflow portrait.
Every storage product ultimately serves a portrait of daily life: a file is captured on one device, refined on another, delivered from a third, and versioned four times before it reaches its audience. Today that portrait is held together by whichever cloud service the household or the studio gives up on and repurchases, with local files treated as an inconvenience.
NeoDrop's concept inverts that portrait: the local storage is the home, the cloud is a service on top rather than a landlord underneath. The design question stops being “which subscription tier?” and becomes “how does moving files around feel more like passing them to a person than publishing to a platform?”
Designing state you can trust.
The most difficult interface challenge in synchronisation is not moving files — it is telling the truth about a moving world: what has arrived, what is pending, what differs across devices, what happened while a laptop was asleep. Sync indicators usually lie by omission, and the first time a user is wrong, the trust they can invest evaporates.
The concept work therefore spends its effort on state language: honest, legible indication of what is where, with edges spoken aloud rather than smoothed over. Precision here is what makes the experience worth installing in the first place.
A small surface with deep systems.
Desktop-first, menu-bar-level small — that form factor has a rule: anything visible must be needed at a glance, and everything else must either be a step away or automatic. The constraint is demanding but clarifying; it forces decisions to be made rather than deferred to a settings folder.
Behind the small surface, the real engineering lives in rules: what moves, what stays, what conflicts and what wins, and what a user can recover when they decide after the fact that they were wrong. Consumer-grade polish is mostly invisible plumbing that makes those rules feel like freedom.
Where it sits among the alternatives.
Against mainstream cloud drives, the NAS-first concept trades convenience for ownership — and for the right audience, that trade is a bargain. Against traditional NAS clients, most of which look like firmware utilities from another decade, the bet is that sync can feel designed rather than configured.
That is the experiment in a sentence: the local-first thesis has never had a pleasant interface. If the experience is the part that has been missing, a studio that builds it has opened a lane that spending money cannot buy in an existing product.
What this demonstrates.
For teams weighing private infrastructure against per-seat SaaS subscriptions, this is the expertise: product design, desktop application development and custom software that runs on your terms. The same thinking applies to internal tools built around your data, not a vendor's.
