Inside River Writer: keep the draft portable before adding a platform
A 24 October Product Hunt launch and current MIT repository show how plain-text source, local formatting and built-in Git can stay separate from cloud workflow promises.
River Writer appeared #14 on Product Hunt's 24 October 2026 daily launch with 78 points when checked 25 October. That dated discovery signal is not market share, a final lifetime total or evidence of reliability.
Documented components, not a complete production inventory.
- Tauri app + JavaScript interface
- Documented native workbench and application layer
- Rust workspace + typesetting crates
- Documented local engine, formatting and test boundary
- Fountain / Markdown project files
- Documented portable source files owned by the writer
- Built-in Git history
- Documented commits, restoration and branch experiments; not a backup guarantee
A recent launch with a narrow, inspectable promise
Product Hunt lists River Writer at #14 with 78 points for 24 October 2026. The maker describes a quiet Mac app for screenplays, stage plays and novels. FreeStack reviewed the launch page and current maintainer repository. We have not built the app, opened a screenplay, verified PDF fidelity, tested crash recovery or confirmed the maker's workflow claims through hands-on use.
What the public source confirms
The repository documents .fountain files for scripts, .md files for novels, a live formatted preview, PDF export, outline and scratchpad files, Git commits and branches, autosave and crash recovery. It also states there are no accounts, cloud sync, subscriptions, telemetry, AI features or network connections. Current distribution is source-only for macOS 13 or later and requires Xcode command-line tools, Rust, Node and pnpm to build.
The documented implementation boundary
The repository names a Tauri application, a Rust workspace with crates, a JavaScript app layer and IPC between the interface and native engine. Its documentation separates file layout, editor behaviour, Git integration, typesetting, security, testing and release decisions. Those are published components of this repository; they do not prove every runtime property or disclose a future hosted architecture.
Plain text provides an exit route
FreeStack's editorial lesson is to decide which file remains useful when the application is unavailable. Fountain and Markdown keep the draft readable in another editor, while Git records meaningful checkpoints. A PDF is a review output, not the editable source. Portability does not solve backup, collaboration, permissions or interchange by itself, but it keeps those requirements visible before they are bundled into a subscription decision.
Try the smaller learning workflow
FreeStack suggestion, not River Writer's production stack: use the linked guide to create one fictional two-page scene, three named checkpoints, a reviewed Vale report and a checked PDF. Save River Writer, Git, Vale and Pandoc as a private starter stack. This teaches the portable-source boundary without claiming a completed film workflow or rebuilding the app.
Where payment becomes justified
The repository currently offers no signed download, Windows or Linux build, cloud sync, telemetry or AI. FreeStack upgrade triggers are therefore concrete: pay when you need a supported installer, real-time co-authoring, managed backup, mobile access, studio permissions, comments or production interchange that survives a representative-file test. Do not pay merely to hide a file format you could continue owning.
Sources & further reading
Follow the source for current details. Product Hunt is used for discovery and launch history; technical claims use provider documentation or the project repository.