storynote

Browser and Device Support for Storynote

Storynote is a web app, so a current browser and a stable connection are most of what you need. This guide covers the setup that works best and the quick fixes for the rare issues that come up.

Recommended setup

Storynote works best in a recent version of a modern browser such as Chrome, Edge, Firefox, or Safari. Keeping your browser updated matters: the editor, real time collaboration, and the interactive views all rely on current web features, and updates also bring security and performance fixes.

A reliable internet connection is the other essential. Storynote saves and syncs your work over the network, so a steady connection keeps autosave and collaboration running smoothly.

Desktop versus mobile

Storynote is built for focused writing and visual planning, which is most comfortable on a desktop or laptop with a real keyboard and a larger screen. The interactive views in particular, like the map and the canvas, benefit from the extra space and precision.

You can check your work on a tablet or phone, but for serious drafting and worldbuilding, a larger screen is the better experience.

Fixing common issues

If something is not behaving, work through these in order:

  • Update your browser. An out of date browser is the most common cause of trouble. Update and reload.
  • Reload the page. A refresh clears most transient glitches, including a view that did not load or content that looks out of sync.
  • Check your connection. If saving or syncing seems stuck, confirm you are online, then reload. See autosave explained for how saving behaves around connection drops.
  • Try another supported browser. If an issue persists in one browser, testing another quickly tells you whether the problem is specific to your setup.
  • Disable interfering extensions. Aggressive ad blockers or script blockers can break interactive features. Temporarily disabling them helps you find the culprit.

If trouble continues after all of this, note what you were doing and which browser and device you were on, and reach out for support so the team can help.