Devlog 003: It’s Starting to Look Like Something

Hello again, writers!

I’ve spent the last few weeks staring at the same interface, moving things around, breaking perfectly good code, and occasionally wondering why building a writing application seemed like a reasonable use of my time.

But we’re getting somewhere. Draftmount is finally starting to look and feel like the studio I’ve been picturing since June.

The workspace is coming together

Most of August went into how everything connects: the editor, the manuscript structure, and the tools a writer reaches for in the middle of a project.

One lesson stuck. A layout can look gorgeous in a mockup and become irritating the moment you actually use it. The sidebar has to make navigating a manuscript easier without eating half the screen, and the editor needs enough breathing room for long sessions. Getting that balance right meant rethinking a few layouts, and yes, moving the same buttons more times than I’d like to admit.

Making the editor feel right

It’s easy to underestimate how much goes into something as ordinary as typing. Cursor behavior, text selection, formatting consistency, even the way the page scrolls all shape the experience. I experimented with formatting controls, document navigation, and how the writing area copes as a manuscript grows.

Some writers like the whole manuscript laid out in front of them; others work chapter by chapter. Draftmount should suit both. There are still rough edges, but the pieces are starting to fit.

The browser storage problem

Because Draftmount runs in a browser, I have to be especially careful about how manuscripts are saved and recovered. Local browser storage is handy during early development, but clearing browser data, switching devices or hitting a browser bug can all put that work at risk.

So I’ve been looking at ways to make saving more dependable, planning for cloud storage, and treating export and backup as part of the same problem. Writers put a lot of time into their stories, and protecting that work deserves serious attention.

A few ideas went to the graveyard

I have a habit of thinking, “Wouldn’t it be nice if the app could also do this?” It’s a dangerous little sentence, and every time I say it, the development list grows.

This month I went through those ideas and decided which belong in the first release. Some will have to wait, and a few may never make it in. I’m getting comfortable with that. I’d rather spend the time polishing the features people use every day.

Three months in

In June, Draftmount was mostly an idea and a growing collection of notes. Now I can see how the parts could work together as an actual product. There’s plenty of development ahead and I expect a few surprises, but I enjoy watching the details come together, even when that means spending three hours fixing something I broke in five minutes.

Coming up in September

September is about refining the core workflows and paying closer attention to how the app behaves in everyday use. I’ll also look at exports, project management, and the small quality-of-life improvements that make a writing environment pleasant to come back to.

Hopefully there will be fewer arguments with the sidebar. I’m making no promises.

Thanks for following along. I can’t wait to let you get your hands on it.

Until the next draft,

The Draftmount Developer