Stage 01
Complete
Identity and Philosophy
Cabin now has a name, domain, GitHub organisation, logo, typographic voice and restrained colour system. Its first product principles establish how the application should grow without overwhelming you.
A route through the mountains
Twelve places.
One careful path.
Stage 02
Current
Personas and Research
Study first-time novelists, worldbuilders, screenwriters, researchers and students in their real writing environments. Their habits, frustrations and existing tools will determine which problems Cabin should solve first.
Stage 03
Beyond the mist
MVP Selection
Reduce the broad feature inventory to a focused first release that protects the core writing experience. Every deferred capability receives an intentional later place instead of quietly expanding the initial scope.
Stage 04
Future
UX and File Model
Define how layouts, panels, resizing, docking and alternate views behave before implementation begins. At the same time, design a durable project folder structure that remains legible outside Cabin.
Stage 05
Future
Design System
Build the shared spacing, typography, icons, menus, sidebars, modals and theme tokens behind every screen. The system must preserve Cabin’s calm character from the smallest dialog to the densest workspace.
Stage 06
Future
Prototype
Create a pure interface prototype for testing resizing, docking, workspace layouts and motion without persistence getting in the way. The prototype should expose awkward interactions while they are still inexpensive to change.
Stage 07
Future
Core Editor
Implement projects, documents, the editor, autosave, themes and tabs with reliability as the baseline. Writing, saving and reopening work must feel uneventful before Cabin earns more advanced capabilities.
Stage 08
Future
Project System
Add folders, chapters, scenes, drag-and-drop ordering, metadata and workspace presets around the stable editor. Search and dependable exports will make larger manuscripts navigable without hiding their underlying files.
Stage 09
Future
Closed Alpha
Invite a small, varied group of writers and observe how they use Cabin without over-explaining it. Their sessions will reveal confusing assumptions, fragile workflows and the rough edges that internal testing misses.
Stage 10
Future
Beta
Open Cabin to a broader group of writers working on real, long-running projects. Improve reliability, measure recurring friction and confirm that the calm workflow survives greater scale and variety.
Stage 11
Future
Deployment
Prepare signed public builds, clear documentation, predictable update flows and thoroughly tested exports. Writers should understand where their work lives and trust Cabin throughout an ongoing project.
Stage 12
Future
Community Growth
Grow a thoughtful community around writing practice, plugins, themes and transparent product notes. Expansion should deepen the craft around Cabin without turning the core application into a marketplace or social feed.