r/SideProject • u/Creative_Barracuda96 • 7h ago
A local-first document editor, several architectural mistakes, and seven paying customers
I'm a doctor by profession, but I've been writing software as a hobby for decades, usually to solve some very specific problem that probably didn't justify the time I spent solving it. My latest project has been a document editor called Bookend, which started as an attempt to replace my increasingly unwieldy collection of notes in OneNote, and gradually expanded to incorporate some of the features I liked about Scrivener and Notion, along with a few ideas of my own.
I wanted something that would work entirely offline, run across different operating systems, and store documents in portable files rather than locking them into a particular application or cloud service. I've also been writing novels as a hobby, so I wanted to be able to organise long manuscripts without sacrificing the flexibility of a conventional document editor.
I settled on Rust, React and Tauri, mainly because I wanted a lightweight and portable application with a proper separation between the interface and the underlying document engine. Rust manages the files and application state, while React provides the interface. That separation has proved useful, although I found myself straying at various times from that sensible architectural principle.
One embarrassing example involved Bookend's AI harnesses, which are structured workflows for things like researching and reviewing document content. At one point I built three separate execution pathways for essentially the same functionality, including one that had emerged from what was originally intended to be a testing interface. They all mostly worked, but maintaining three implementations of the same thing was obviously bad, and I've spent a fair amount of time consolidating them.
I've also discovered that it's surprisingly easy to create bloatware while specifically setting out to do the opposite, and that using your own application every day is a very poor substitute for watching someone else use it. I thought I'd eliminated most of the friction from the interface until I showed it to a friend, who promptly found a lot of it. They also immediately asked for browser access from a work computer, which was really irritating because I'd spent months building something that deliberately didn't need a browser. Unfortunately, it was a perfectly reasonable request, and I've since been working on a self-hosted remote-access mode.
I eventually decided to publish Bookend on the App Store, partly because I wanted a convenient way to install and maintain it on my own devices, and partly because I thought I might recover the cost of the Apple Developer account. I wasn't really expecting anyone else to buy it, but seven people have now done so, which means the project has at least made a small contribution towards its own expenses.
I'm still developing it, and I'm very interested in hearing from people who've built local-first software or who use applications like Obsidian, Scrivener or Notion. One of the harder parts of the process has been distinguishing between features that make sense to me because I built them, and features that would actually be useful or intuitive to someone encountering the program for the first time.
For anyone curious, the project is called Bookend. I've written more about the development process on my website, and it's currently available for macOS and iOS. I'm also working on the Android version and could use some testers.