Hi Product Hunt! 👋 I’m Anton, a software engineer and an author. B-Maker started with a problem I kept running into myself: at some point, a book stops behaving like a document. It becomes a project. There are chapters, scenes, old versions, comments, characters, plotlines, research, ideas that may become chapters later, and material you want to keep without necessarily publishing. As a developer, this felt strangely familiar. Software engineering has had tools for managing complex projects for decades — but simply giving writers Git, issue trackers and diagrams would obviously be the wrong answer. So I started building B-Maker around a different idea: give writers project-level capabilities without project-management complexity. You can open B-Maker and simply start writing one chapter or article. If the project grows, you can gradually add structure, collections, versions, characters, plotlines, an Idea Map, a manuscript board, editorial checks, analytics and publishing tools. One design decision I care about especially is local-first ownership. A B-Maker project can be stored as one portable .bmaker file containing the manuscript, structure, versions and planning data. No mandatory proprietary cloud is required for your book to exist. B-Maker currently runs as a native Windows app and as a web app. I’d especially love feedback on three things: — Does the “start simple, grow into a system” approach make sense for your writing workflow? — Which part of managing a long manuscript causes you the most friction? — What would stop you from using B-Maker for a real project? Thanks for checking it out. I’m building this in public, so critical feedback is genuinely useful.

B-Maker

Plan, write, revise and publish in one project

Plan, write, revise and publish in one project