NAOMS has a web version that runs in a browser tab, with no install. Until now, a freshly made account there could not reliably save a note. On 22 October that changed: first-run setup finishes in the background, you see what it is doing, and when it is done, saving works.

What the setup is

Your data lives on a chain, a signed, append-only record kept on your own device. A chain only accepts the kinds of record it has been told about. Before it can hold a note, it needs to learn that notes are allowed.

On the desktop app this happens at startup. The web version now does the same thing after you create or unlock your account, using the same rules as the desktop. It also registers what those records are, so a saved note can be found again.

Who it is for

Anyone trying NAOMS from a browser, for example from a link a friend sent, who wants to use it right away without installing anything.

A walk-through

Dana opens NAOMS in her browser and sets up an account.

1. Right after she does, a small line appears: "Finishing setup, saving works in a few seconds."
2. If she tries to save during those seconds, the save is refused with that same sentence instead of failing silently.
3. The line disappears when setup is done. She writes a note and saves it. It lands on her own personal chain, and a search finds it again.
4. If she closes the tab halfway through, nothing is lost or doubled. Setup resumes from where it stopped the next time, and a record already written is not written a second time.

In the team's own timing, setup finished about 17 seconds after the account was sealed. That is a measurement from the builder's machine, and your connection and device may differ.

When setup does not go smoothly

The screen says so by name rather than spinning forever:

• If setup fails, you see "Setup did not finish" with a short code, and the advice to lock and unlock to try again.
• If it takes more than ten minutes, you see "Setup is taking longer than expected", and you can keep waiting or try again.
• If you are adding a second device, the screen says it is waiting for your first device to share its setup, and the message clears by itself when that arrives.

What's next

• The web version is still catching up with the desktop. This work makes notes and tasks savable. It does not claim every app works in the browser.
• The records written during setup itself are indexed in the simpler way the desktop used before this change. Later saves, and any reload, use the full set. Doing it the other way round made setup take about three times longer, so we chose speed.
• A saved note is guaranteed on your chain in the tests we ran, but the full join-from-another-device walk-through still needs a relay server our test machines do not have yet.

Written by AI agents from real project logs; owned and edited by Mujo.