Writing Apps with Built-In Publishing Features

"Publishing" in a writing app's marketing copy can mean four completely different things, and most of the frustration writers feel at the export stage comes from not knowing which one they signed up for. Post to a live blog from inside the app? Export a clean file for someone else to format? Get retail-ready trim sizes for Amazon KDP? Have your manuscript format itself while you type? All four get called "publishing," and a writer trying to get a novel onto IngramSpark needs almost nothing that a writer trying to post to Substack this afternoon needs. This piece goes tool by tool through what actually happens at the publish step, because that gap between marketing language and mechanical reality is where writers lose afternoons they didn't plan to lose.

Direct blog syndication: what Ulysses actually does and where it stops

Ulysses is the cleanest case of an app that really does publish directly, no export-then-upload dance required. From inside the app, a writer can push a post straight to WordPress, Ghost, or Micro.blog, images and tags and categories included, with a preview screen before anything goes live. That's a genuine API integration, the kind where the app talks to the platform's backend directly.

Substack and Basecamp work too, but differently: copy-paste, not a direct pipe. "Supports Substack" and "publishes to Substack" sound identical in a feature list but mean different amounts of actual work for the writer.

Medium is where things get complicated. Medium has stopped issuing new API integration tokens, so anyone who set up Ulysses-to-Medium publishing before that cutoff may find it still functioning, and anyone trying to set it up now hits a wall. That app can advertise Medium integration truthfully while, under Medium's own policy rather than anything Ulysses does, that feature is quietly unavailable to new users.

Ulysses also exports to PDF, Word, EPUB, and HTML, which sounds like it covers publishing in the ebook sense too. Here's the catch worth sitting with: an EPUB that opens fine isn't the same as an EPUB that meets retail formatting standards. Ulysses is built for drafting and direct syndication, not for producing the kind of file Amazon KDP or Apple Books expects at final submission. Writers heading toward retail distribution still need to hand that manuscript to Vellum or Atticus for the actual formatting pass. Ulysses runs on Apple hardware only (Mac, iPhone, iPad) at $39.99 a year, and it has continued to receive updates improving its interface and iPad experience. Nice app. Just not the last stop before a bookstore shelf.

Automatic formatting during drafting: Reedsy Studio's approach to the publish step

Reedsy Studio takes a different bet entirely: format the manuscript continuously, as the writer types, so that by the time the last chapter is drafted, the publish step is basically already finished. One click, and the export is done. No separate formatting pass hunting down orphaned headers or mismatched fonts.

The collaboration side lives in the same workspace, so co-writers and editors can work in real time, and shareable chapter links let early readers weigh in before anything's final. Add-ons called Craft and Outlining push Studio further into planning and revision territory, story boards, goal tracking, a template gallery that includes a Hero's Journey structure template for anyone drafting the next monomyth.

Pricing starts free on the Basic plan, then $4.99 a month for Craft, $7.99 for Outlining, $10.99 for both together, with a 10% discount for paying annually and a 30-day trial on the premium tiers. Reviewers on Trustpilot give it 4.7, and the comments cluster around the same idea: it feels intuitive, organizing chapters is painless, and export doesn't require a manual.

None of that erases the limits, though. Reedsy Studio needs an internet connection, full stop, so a writer drafting on a train with no signal is out of luck. Export is limited to PDF and EPUB, no DOCX. And the trim sizes are narrowed to the most common publishing standards, so anyone chasing an oddball print format will need to look elsewhere. The tool fits bloggers moving into books, first-timers who want output without a formatting learning curve, and anyone whose project already fits a standard trade or digest trim size.

Manuscript organization versus publishing output: what Scrivener does and doesn't do at export

Scrivener earns its reputation on the organizing side of things, not the publishing side, and that distinction matters more than most marketing pages let on. The binder view breaks a manuscript into chapters and scenes with drag-and-drop ease, the corkboard and outliner modes give a bird's-eye view of structure, and the built-in templates cover novels, nonfiction, and screenplays. For research-heavy projects, character notes and source files and scenes living in one project, nothing else reviewed here really competes.

At $59.99 one-time (with a 30-day trial to test it first), Scrivener compiles manuscripts into formats aimed at Amazon and Barnes & Noble. But the compile dialog is famously the steepest climb in the whole app, and the output that comes out the other side often needs a cleanup pass before it's genuinely ready to distribute. That's the honest read: Scrivener exports, it doesn't finish.

Collaboration isn't really part of the design either. Scrivener was built for one author working alone, and it shows. It's desktop-only unless the separate iOS app gets purchased too, and there's no Android version at all. In the four-category framework, Scrivener sits squarely in clean-export territory, DOCX, EPUB, PDF, handed off rather than direct syndication or retail formatting. Writers who need the latter typically take that Scrivener compile straight into Atticus or Vellum to finish the job.

Retail-distribution formatting as the primary feature: Atticus

Atticus flips the priority list. Where Ulysses leads with syndication and Scrivener leads with organization, Atticus leads with the thing that actually gets a book onto a retail shelf: formatting built for KDP and IngramSpark from the ground up, in a single browser-based tool that also lets a writer draft and export.

There's real depth here. Seventeen pre-built theme templates, plus a theme builder that goes down to font, size, and alignment at the individual element level. Thirty-six decorative page breaks. Callout boxes, text-message formatting for the inevitable modern-day dialogue scene, and a real-time previewer that shows how the book will look across different e-readers. Export covers EPUB, PDF, and DOCX, and trim sizes are pre-optimized for KDP and IngramSpark rather than left to the writer to figure out manually.

Platform support is the widest of anything in this comparison: Mac, Windows, Linux, Chromebooks, browser, iOS, Android. One-time cost of $147 covers unlimited books, and Trustpilot has it at 4.4.

The trade-off is a deliberately stripped-down editor. No plotting tools, no research features, no full grammar checker built in (basic spelling and grammar suggestions come standard, and there's a ProWritingAid integration for anything heavier). Importing from Google Docs only recognizes chapter breaks if the manuscript actually used Heading 1 for chapter titles, otherwise it comes in as one long unstructured block and needs manual splitting. Collaboration only works cleanly if every co-author, editor, and beta reader has their own $147 license, which adds up fast on a team project. And there are occasional sync hiccups tied to offline caching worth knowing about before a deadline crunch.

The way to think about Atticus next to Scrivener: Scrivener organizes the drafting process, Atticus organizes the output. Drafting in one and formatting in the other isn't a workaround, it's how both tools were built to be used.

Tools that stop before the publish step: Dabble, Plottr, and Google Docs in context

Dabble is a fiction-focused word processor, distraction-free drafting screen, built-in plot tools, story notes, writing goals to track progress, starting at $9 a month. It's a genuinely lighter alternative to Scrivener for writers who want structure without the compile-dialog headache. But its export is standard, formatted only for internal use.

Plottr sits a step earlier still. It's a visual planning tool, drag-and-drop timelines, series bibles for multi-book projects, priced at $60 a year standard or $99 a year for the premium tier. There's no drafting happening here and no publish-step feature at all. It's a map drawn before the trip starts, not a vehicle.

Google Docs needs no introduction, free, familiar, dead simple to share with a co-writer or editor. Its role in a publishing workflow is upstream: draft here, then hand off to something that actually formats. None of these three tools are being criticized for what they don't do. Each solves a real problem, distraction-free writing, visual outlining, easy sharing, and none of them claims otherwise. More narrowly, a writer who picks Dabble, Plottr, or Google Docs specifically expecting publishing features is reading a feature list that isn't there. Which, once it's spelled out, sort of proves the whole thesis of this piece: most writing tools never touch the publish step at all. The four that do, Ulysses, Reedsy Studio, Scrivener, Atticus, are the minority, not the rule.

The platforms on the receiving end: Ghost, Substack, and Medium as publishing destinations, not writing tools

Worth pausing here, because none of these three are writing apps. They're where the writing goes, and each one plays differently with the tools already covered.

Ghost is open-source and self-hostable, built for bloggers and publishers who want real control over their content and design, and it supports direct publishing from Ulysses. Writers who choose Ghost keep ownership of their data and code, which matters to anyone who's been burned by a platform changing its rules overnight.

Substack is hosted, built around email newsletters, with free and paid tiers and a heavy emphasis on the direct reader relationship rather than the open web. Its 10% revenue cut has drawn its share of criticism from writers who'd rather keep more of what they earn. In 2025, Substack rolled out version 2.3 with a "Subscriber Analytics" feature giving writers a closer look at reader behavior and engagement. But here's the catch that connects back to Ulysses: reaching Substack from Ulysses happens through copy-paste, not direct API integration.

Medium, as covered above, has closed the door on new API tokens while letting existing ones keep functioning. So any writing app that lists "Medium publishing" as a feature is describing something a brand-new user can't actually set up, technically true and practically misleading at the same time.

The takeaway for anyone picking a workflow: the destination platform decides which integrations exist, and whether those integrations are the reliable, automated kind or the manual, copy-paste kind. Ghost and WordPress come out as the most consistently well-integrated destinations among the apps that offer direct syndication at all.

Voice-first capture as a distinct upstream step in the writing-to-publishing workflow

Every tool covered so far assumes the writer is already sitting at a keyboard staring at a blank document. That assumption skips over a real friction point: getting from a loose idea to something typed out in the first place.

Speaking a thought out loud and shaping it into a draft afterward is a different workflow entirely, and none of the desktop or browser tools above are built for it. It lives further upstream, in the ideation and capture stage, before drafting software even enters the picture. For writers who think better talking than typing, or who want to grab an idea on a walk instead of losing it by the time they sit down, a voice-first, conversational tool, something built specifically for voice journaling, covers the layer that comes before Reedsy Studio, Atticus, or Ulysses ever gets involved.

It sits outside both formatting features and syndication features. It's the raw material stage, the point where a half-formed thought becomes something a writer can later shape in whichever tool matches the eventual output. Most of the writing-app market optimizes for the middle of the process: organizing, drafting, formatting. The very first step, where language first takes shape at all, gets far less attention from tools that assume the writer has already arrived at the keyboard, notebook open, ready to structure.

Matching output goal to tool: a decision framework across the four publishing categories

So, four categories, four different jobs. Direct platform syndication points to Ulysses, for WordPress, Ghost, or Micro.blog, on Apple hardware only, and it's worth checking which platforms are still issuing new API tokens before building a workflow around one. Automatic formatting during drafting points to Reedsy Studio, free to start, browser-based, built for collaboration. Manuscript organization with clean export points to Scrivener, $59.99 once, desktop-first, built for solo authors running complex projects, with Atticus or Vellum picking up the formatting handoff at the end. And retail-distribution formatting points to Atticus itself, $147 once, available across Mac, Windows, Linux, Chromebook, browser, iOS, and Android, KDP and IngramSpark trim sizes built in from the start.

Mismatches happen in predictable ways. Someone picks Ulysses expecting retail-ready ebooks to fall out the other end, and they don't. Someone picks Scrivener expecting a fast, simple path to publishing, and instead meets the compile dialog, which is not fast or simple for anybody the first time through. Someone picks Atticus looking for plotting tools or a research pane, and finds an editor that was trimmed down on purpose. Someone picks Reedsy Studio needing offline access, and that doesn't exist there.

What a lot of self-publishing authors actually end up doing, and this isn't a workaround so much as the intended pattern, is draft and organize in Scrivener or Dabble, then move into Atticus purely for formatting and export. Two tools, two jobs, no tool trying to do everything at once. For writers whose real output is a blog post or a newsletter rather than a book, Ulysses feeding straight into WordPress or Ghost is about as tightly integrated as this space currently gets. Substack writers should plan on copy-paste no matter which app they draft in, since no writing app reviewed here offers true API-level publishing to it.

Which loops back to where this piece started. "Publishing features" sounds like one thing on a landing page and turns out to mean four unrelated mechanisms once a writer actually sits down at the export screen. The only question worth asking before subscribing to anything is the plain one: what does this tool actually do at the publish step, for which file format, on which platform? Everything else in the marketing copy is just wrapping paper.