Devlog 002: Finding Our Footing

Hello again, writers!

A month in, and what started as a pile of ideas is beginning to feel like a real writing studio.

June was about deciding what Draftmount should be. July was about making it work, and it turns out a writing app takes a lot more than a text editor inside a pretty website. Who knew?

The editor comes first

The writing experience got most of my attention this month: how the editor should behave, how text gets formatted and organized, and how the interface feels during long sessions.

Everyday writing should feel natural. Starting a paragraph, moving between chapters or changing a heading shouldn’t make you think about the software. Good tools are there when you need them and quiet when you don’t.

Finding the right structure

Not everyone writes the same way. Some writers plan every chapter before typing a sentence; others open a blank page and hope the characters cooperate. I want Draftmount to work for both.

That means thinking hard about how projects, chapters, scenes and notes fit together without turning the workspace into a maze of menus. I tried several layouts this month, kept the ones that felt obvious, and reworked the rest.

The less glamorous side of development

Saving, performance, document handling and recovery won’t make exciting screenshots, but nothing here matters more.

A big priority is making sure writers know where their work is stored and how to keep it safe. Cloud storage is part of the longer-term plan, but I don’t want to promise it before it’s reliable. A beautiful editor means very little if someone loses their manuscript.

Learning when to say no

July reinforced a lesson: not every good idea needs to become a feature. It’s tempting to keep adding things when you’re excited about what you’re making, but Draftmount needs a solid foundation before it needs a hundred tools. For now the focus stays on writing, organization and reliability.

The fancy things can come later. Probably.

Looking toward August

Next I’ll bring the separate pieces of the writing experience together and see how they work as one application. A few things will almost certainly need rebuilding along the way, and that’s part of the process.

Until the next draft,

The Draftmount Developer