Can You Share a Tiny Little Office Document With Your Family?

Short answer: no, not the way you'd expect. Tiny Little Office — the free, no-login browser suite that hit the front page of Hacker News this week — lets you send someone a link to your document, but opening that link gives them their own independent copy, not a live window into yours. Whatever they type never reaches you, and whatever you type next never reaches them. It isn't a bug. It's the direct cost of the trick that makes the whole thing work in the first place.

If you haven't seen it: Tiny Little Office is a free bundle of ten small tools — word processor, spreadsheet, outliner, presentation builder, calculator, drawing tool, diagram maker, animator, calendar, trip planner — with no account, no login, and (its creators say) nothing saved on any server. It's a revival of an earlier project called TinySheet, and by the project's own account it was "vibecoded in three days." It racked up 699 points and 201 comments on Hacker News this week, plus write-ups from TechRadar, The Register and Kottke, mostly along the lines of "look at this clever thing."

The trick, and why it has a price

The reason Tiny Little Office needs no account and no server is that your document isn't stored anywhere except the link itself. Every edit you make gets encoded straight into the URL. That's a genuinely neat piece of engineering — there's nothing to log into, nothing to lose when a startup shuts down, nothing for a company to hold hostage.

It's also why two people can't share one. A link is just text. If you text your partner a link to the grocery list you just built, their browser decodes that text into a document on their screen — a copy, built fresh from the same starting characters yours was. From that moment, your two documents are two separate things that happen to look the same. Add an item on your end, and it exists only in your link. Add one on theirs, and it exists only in theirs. There's no server in the middle to reconcile the two, because having no server in the middle is the entire point.

People noticed this the same day the project hit Hacker News. One commenter asked outright whether the team had "considered real time collaboration," then answered their own question a moment later — the data is stored in the URL, which makes live sync "not really that close." Another asked if they could contribute a pull request for live collaboration using WebRTC. Nobody in the thread described it as solvable with a quick patch; it's a direct result of the architecture, not an oversight.

What else breaks along with sharing

The same lack of a server creates two more honest trade-offs worth knowing before you build anything real in it:

• The link is the only copy. There's no account to log back into and no server copy to recover from if you lose the URL. A review of the project put it plainly: avoid it for "records that must remain available indefinitely without an independent export." The project's own co-founder has a track record here — on a previous linked-document project, by their own account, "those sites fell off the web, and the old links all broke."
• Whoever has the link has the document — full stop. Reviewers note the URL functions as the password: "possession of the URL may function as possession of the document." You can password-protect a link, mark it read-only, or set it to expire, but the baseline access model is simple text in a browser bar, which means it can leak through chat history, browser history, screenshots, or a referrer header without anyone touching a server. As one review put it, "not saving to a server is not a complete privacy guarantee." Nobody recommends putting a password or financial record into one of these links.

None of this makes Tiny Little Office a bad idea — it's an honestly clever answer to "how do I make a quick, private, disposable document with no account." That's a real, narrow job, and it does it well. The trouble starts the moment you ask it to do a second job: being the shared grocery list, the shared to-do list, the shared anything your household keeps coming back to and editing together over weeks.

The actual tension

What this week's launch makes visible, more clearly than most, is a real tension that most tools quietly paper over: owning your data and sharing it with the people you live with pull in different technical directions. A tool with zero server and zero account is maximally yours and maximally offline — there's nothing to log into, nothing that goes down, nothing anyone else controls. But the instant two people need to see the same live document, something has to sit between them to reconcile changes. "No backend at all" and "my partner and I are editing the same list" are, architecturally, in tension — pick a tool built entirely around the first, and the second doesn't come along for free.

That's the actual problem FOKL exists to solve: not "yours" instead of "shared," but both at once — your tool, your data, genuinely offline-capable, and still something you hand to your partner or your kid and both of you are looking at the same list, updating in real time, without either of you forking a copy by accident. It's a harder engineering problem than Tiny Little Office's, which is exactly why it isn't a three-day build.

FOKL is still pre-launch, so there's nothing to try yet. If "I made something, but I couldn't actually share it with the person I made it for" sounds like a familiar shape of problem, the waitlist at fokl.ai is where we're keeping the people we're building it for.