River Writer: A Quiet, Anti-Cloud Writing Tool for the Mac

In an era dominated by AI writing assistants and cloud-based collaborative documents, a Mac app called River Writer has chosen the exact opposite direction: no account, no cloud sync, no telemetry, no AI, and not even a single network connection. It does just one thing—let you write screenplays, stage plays, or novels in peace.

Built by independent developer Arjun Acharya, the tool earned 73 upvotes on Product Hunt, landing at #14 for the day and picking up the "Productivity" and "Open Source" tags. The vote count isn't exactly dazzling, but the product philosophy it represents deserves serious scrutiny.

Plain Text as the Bones, Live Preview as the Flesh

River Writer's core workflow revolves around plain text. Users write in .fountain (a screenwriting-specific format) or .md (Markdown), and the app renders a formatted, print-ready page in real time on the right. The preview supports four layouts: Screenplay (standard script), Multi-cam (multi-camera sitcom format), Stage Play, and Manuscript (novel manuscript).

This two-pane "write plain text, see the typeset page" design isn't new, but what makes River Writer restrained is that it doesn't hide formatting behind an export button. The preview is always visible, meaning writers can directly sense the rhythm of the final page as they create—and for screenwriters, where one page roughly corresponds to one minute of screen time, that instant feedback has real value.

Choosing the .fountain format is a smart move. Fountain is an open-source screenwriting markup language that expresses scene headings, character names, dialogue, and transitions using simple indentation and keywords. It's fundamentally plain text, so it doesn't depend on any specific software and won't lock you into a vendor's ecosystem.

Fountain syntax was proposed around 2012 by screenwriter John August and developer Nima Yousefi, with the spec published openly at fountain.io. It's been adopted by screenwriting tools like Highland and Slugline as well as some film and TV production workflows. Its design philosophy is similar to Markdown: a handful of conventions—scene headings starting with INT./EXT., character names on their own line in all caps with dialogue immediately following, transitions starting with > or written in all caps ending with TO:—express script structure, and everything else is treated as body text. Since the file itself is UTF-8 plain text, it can be opened by any editor and compared line-by-line by Git, which dovetails neatly with River Writer's version control design.

Built-in Git: Handing Version Control to Writers

River Writer's most differentiated feature is embedding Git version control directly into the writing workflow. Users can commit drafts, restore historical files, and even try an alternate ending on a separate branch.

To non-programmers, this may sound unfamiliar, but it solves a very real problem: writing is inherently a process of trial and error, yet most writing software only offers "undo" and limited version history. Bringing in Git means you can keep a complete timeline while exploring multiple creative directions in parallel—say, advancing the main draft on the main branch while writing a darker ending on another branch, switching back and forth to compare at any time.

Outlines, scratchpads, and todos are also stored as plain files in the project directory. This design makes the entire project fully transparent to the user: everything is a readable, portable text file, not hidden away in a database or proprietary format.

Interestingly, built-in Git still poses a learning curve for the target audience. The product currently has only 3 reviews, and it's unclear whether it offers a sufficiently friendly Git interface to lower that barrier. This is where River Writer needs to prove itself.

Git is a distributed version control system created by Linus Torvalds in 2005 for Linux kernel development. Its core model is the "commit": each commit records a complete project snapshot and points to a parent commit, forming a traceable chain of history; a branch is essentially just a movable pointer to a commit, making branch creation and switching extremely cheap. "Writing a darker ending on another branch" means letting two creative lines share the same early history and then evolve independently, merging or discarding as needed. Git runs entirely locally with no server required, which is naturally consistent with River Writer's offline stance; but command-line concepts (staging area, commit messages, merge conflicts) do pose a barrier for writers.

"No AI, No Network" Is a Product Stance

River Writer explicitly declares: no account, no cloud, no telemetry, no AI, and no network connections of any kind. In today's tool market, this is both a technical choice and a statement of values.

Its appeal lies with several types of users: privacy-sensitive authors, creators tired of subscriptions and cloud lock-in, and those who don't want their work used to train models. The combination of plain text and local storage also means the project can survive into any future tool—as long as the text remains, the work won't be lost.

The trade-offs are equally obvious. No cloud sync means switching devices requires manual migration; no collaboration features means co-writing a script requires finding another solution; no AI assistance means facing the blank page on your own. River Writer clearly believes these "missing" features aren't a problem for its target users—they may even be the selling point.

"Telemetry" refers to software automatically collecting usage data in the background—launch counts, feature clicks, crash logs, even characteristics of edited content—and uploading it to vendor servers. It's commonly used to improve products and troubleshoot issues, but users are often unaware of it. In contrast, offline-first and local-first software advocates storing data on the user's device by default, with the network serving only as an optional sync channel. This philosophy has been systematically articulated in recent years by research teams such as Ink & Switch, emphasizing users' long-term ownership of data and the portability of software. River Writer's "no network connections of any kind" is the most thorough form in this lineage, and its verifiability is one reason it chose to be open source.

Open Source and Sustainability

River Writer is open-sourced under the MIT license, so the code can be freely used and modified. This lowers the trust cost for users—you don't need to take the developer's word for it; you can look at the code and confirm it really doesn't connect to the network.

But free open-source apps also face sustainability questions. How does the developer sustain long-term updates? There's no clear information at present. For a Product Hunt launch with only 73 votes, it may be too early to discuss business models, but this is a reality users can't help but consider when choosing a long-term writing tool.

Who It's For, and Who It Isn't

If you write screenplays or stage plays, value the portability of plain text, are willing to learn a bit of Git, and dislike cloud and AI intruding on your creative process, River Writer is worth a try. If you need multi-person collaboration, seamless cross-device sync, or AI-assisted generation, it clearly isn't designed for those scenarios.

In a writing tool market that keeps getting "smarter," River Writer's "quietness" is itself a scarce commodity.

One-line Summary

River Writer is a plain-text, open-source Mac writing app with no account, no cloud, no AI, and built-in Git.

Paragraph Summary

River Writer is a free, open-source Mac writing app from independent developer Arjun Acharya, built for screenplays, stage plays, and novels. Users write in .fountain or Markdown plain text, with four layout options rendered live on the right as print-ready pages, letting authors sense the rhythm of the finished draft as they write. Its most differentiated feature is embedding Git version control into the writing workflow, supporting draft commits, history restoration, and parallel exploration of alternate endings on branches; outlines, scratchpads, and todos are also stored as plain files in the project directory, making the entire project fully transparent. The product explicitly declares no account, no cloud sync, no telemetry, no AI, and no network connections, selling on privacy and portability—at the cost of missing collaboration and cross-device sync, plus a Git learning curve for non-programmers. The MIT license lowers trust costs, but long-term sustainability remains unclear.