Writality is free. I do not like the idea that a writing tool should sit between someone and their work with its hand out. If the tool is useful, it should earn its place by being useful, not by turning the act of writing into a subscription decision.
FAQ
Questions I imagine
people would ask.
These are the questions I imagined people ask about Writality. If I had any users, that is.
Still, these are probably the obvious ones, so I wrote the answers down anyway.
BEFORE YOU ASK
Writality is opinionated. It is for me more than it is for a anyone else. I built it to scratch my own itch, and I expect that if it scratches the itch of anyone else, it will be because they are similar to me in how they write and what they want from their writing software.
WHAT THIS PAGE IS
Not at the moment. I am not wholly against AI, but I am also not interested in using it in a way that takes the pen out of the writer's hand. If it ever shows up in Writality, it would be for things that support the work rather than replace it. Something more like spotting a plot hole, noticing a contradiction, or helping you catch structural issues. Even then, I am not sure what shape that should take yet, because I do not love the idea of casually handing your work over to the AI overlords just to bolt on a feature.
It helps by keeping the surrounding complexity attached to the draft instead of scattered around it. As the project grows, you can link characters, locations, and events directly into the manuscript, move through those connections, and see how things relate without having to stop and reconstruct your own system every time you forget where something lives. The idea is not to interrupt the writing. The idea is to make the project easier to stay inside.
Most tools either feel too generic or too managerial. Writality is me trying to make something that stays close to the actual work of writing. It is offline-first, so your work stays on your device. It understands relationships, structure, and chronology without forcing you into some stiff prefab workflow. I wanted something that feels calm, specific, and properly built for fiction instead of pretending a novel is just another document.
The short answer is that it is built for the whole shape of a writing project, not just the page where the current paragraph happens to be.
- •A rich text editor for the manuscript itself
- •Version control with automatic snapshots
- •A unified Concepts system for characters, locations, and other story elements
- •Visual relationship graphs
- •Chronology tools with time graphs and time logic
- •An image gallery for visual references and assets
- •Tagging and global search across the project
- •Writing analytics and progress tracking
- •Spellcheck in multiple languages
- •Offline-first storage, with your data staying on your device
So the useful version is: the writing, the surrounding material, and the project logic are meant to live together, instead of being split across five different tools and your tolerance for folder systems.
The next obvious thing is maps. Not as some bolted-on gimmick, and not by jamming in someone else's mapping tool just to say it exists.
I want something in-house that makes sense inside the app and fits neatly with the rest of it. I do not know exactly which approach I want yet, which is partly why I have not rushed it.
I also sometimes get ideas when I am out and about, and I usually jot them down in Obsidian. That keeps reminding me it would be nice to have some kind of mobile companion that integrates properly instead of living as a separate habit.
Toward a fuller creative workspace, but not a noisier one. I do not want to keep adding features just to make the list longer.
The writing, relationship, and chronology systems already do real work, so the direction now is to make the whole thing feel more complete without making it feel busier. Most of that direction comes from using it myself and noticing where the work still catches.
The manuscript side also needs some love. The mildly inconvenient truth is that I have never finished a first draft, so I am usually most motivated to work on features when I actually hit the need for them in my own writing. That is typically how development happens: I run into the edge, get annoyed, and then go build the missing piece.
Because I want it to exist, which is a less polished answer than people usually give, but it is the honest one. Writality is a passion project. I am not building it just for the sake of building a product, and I am not building it as some neat little monetisation puzzle. I use it myself when I write, and that is usually where the next improvement comes from. I run into some friction, or notice some missing piece, and then I start thinking about how it should work properly. That is typically how it goes.
Yes, but not in the usual real-time-multiplayer-document sense.
I am not especially interested in turning a novel into a shared office document where three people poke at the same paragraph at once. That is a real kind of collaboration, but it is not the one I care about here.
What I want is something closer to how creative writing actually gets shaped: writing groups, chapter sharing, thoughtful feedback, review rounds, and a small circle of trusted readers helping the draft become itself over time.
So yes, collaboration matters. Just not as 'Google Docs, but for novels.' That sounds miserable.