Writing software · Active development

WriMo

A writing workspace that keeps the author in control of the words, the project, and the recovery path.

01 / The why

The problem worth solving

Writing tools can push complexity, lock authors into their own systems, or interrupt their flow. I wanted a calmer place to keep writing and return to work with confidence that drafts were saved and recoverable.

02 / In the product

A look inside

Product screenshots are being reviewed for public release. This page describes verified foundations and design direction without substituting mockups for working software.

03 / Functionality

What the experience does

The current browser foundation supports signing in with GitHub, creating projects and chapters, saving local drafts, and using private-repository backup/recovery.
The desktop development foundation supports local projects, chapters, rich-text editing and local save/reopen workflows.
Design exploration continues around collaboration, provenance, import/export, customization and stronger offline/recovery experiences. Those directions are not all shipped.

04 / Direction

Decisions I made — and why

Writer-first, not AI ghostwriting

The product centers human authorship and ownership; external AI integrations are optional directions, not the reason to write.

Trust requires more than a save icon

I separated local-save confidence from backup and recovery, and required clear conflict handling rather than silently overwriting work.

Technical internals should stay out of the way

Git and repository history can support recoverability without forcing writers to learn developer terminology.

One thing, many relationships

The principle that everything can be a note guides organization and future metadata, while keeping the initial writing experience simple.

05 / The process

Building alongside AI

I run the product and design decisions through structured sessions and record their consequences before committing implementation scope.

AI collaborators help investigate architecture, implement browser and desktop foundations, write tests, and examine edge cases. I review the behavior and separate demonstrated capabilities from roadmap ideas.

A core test of the process is independent recovery, not just a successful save message. Some desktop and connectivity scenarios still need direct verification.

06 / Where it stands

What came of it

The browser and desktop foundations are developing. The product remains a work in progress; current tests do not establish that the entire long-term design is already available.