Public beta · 0.2.0-beta.2

Help shape a dependable home for your story.

Free to try, without an account or payment. Start with disposable writing and a checked backup before using an important manuscript. No cloud recovery is available.

A practical test session

1. Create a project, rename its empty book, and add a chapter and two scenes. There should be no example writing to delete.
2. Write a few paragraphs. Try formatting, lists, a table, a comment, find/replace and undo. Wait for “Saved on this device,” reopen the site in the same browser, and check your work.
3. Read the full chapter or book. Use the tree, tabs, and Project/Details/Reference menus on a small screen.
4. Add a character, question, source and finding. Link research to a scene. Try an optional planning template, a promise and a revision issue.
5. Add dated timeline entries and switch between Planning, Visual and Vertical views. Treat custom calendars and advanced continuity as experimental.
6. Export to DOCX, Markdown, plain text and PDF via print. Check the files, including formatting and any citations. Exact Word layout is not promised.
7. Download a complete workspace archive through Help → Backups & recovery. Check the file, then restore it as separate projects. Verify prose, attachments and saved revisions; your original projects must remain intact.

Never clear your real workspace to test recovery. A preview address, another browser, or another device has its own independent storage. Moving to talespyre.com requires a downloaded backup and restore.

Browser compatibility during beta

Recent manual checks cover desktop Chrome saving, reopening, backup download, validation and restoration. Physical Safari/Firefox and mobile testing, native file-permission/failure cases, and screen-reader review are still incomplete. This is a limited public beta, not a claim of full browser or accessibility certification. Start with a checked safety backup before trusting important work to the beta.

Our target test matrix is current Chrome, Edge, Firefox and Safari, including Android Chrome and iPhone Safari. This is a testing target, not a claim that every physical device has passed.

• Browser-local saving requires available browser storage. Private browsing, quotas and cleanup can limit retention.
• Optional direct file autosave requires a compatible desktop browser and permission, typically Chrome or Edge. If unavailable, browser saving continues; use manual safety downloads.
• PDF uses your browser’s print dialog. Fonts and spellcheck depend on your device/browser. Installed fonts or your own licensed web-font project are required.
• Offline startup, cloud sync, collaboration, Google login and billing are not available.

Tell us what got in the way

Include the release number, steps, expected result and what happened. Browser details are optional. Reports are prepared locally for your review; nothing is automatically sent and no manuscript is attached.

If saving fails, keep the tab open, preserve your text and make a safety copy if possible. Do not clear site data or overwrite another copy to troubleshoot.