What I built this week: moving publish actions into the editor to fix a silent drop-off problem

Sometimes the bug isn't in the code it's in the flow.

We have a thread editor in XreplyAI (Rails API + Next.js). It handles per tweet character limits, thread ordering, and multi-platform context. Users write threads for X, LinkedIn, Threads, all from one place.

The problem: after writing, they had to navigate to a separate screen to actually schedule or publish. One extra step. Invisible in analytics until I looked at completion rates by flow stage. Threads were being written but not posted.

The fix was straightforward once I diagnosed it: surface post now, schedule, and save draft directly in the editor. Conditional on having content in the first tweet. Button label updates based on whether a schedule time is already set.

The engineering challenge was keeping the component focused. The editor was already managing a lot of state. The solution was treating the publish actions as a read-only consumer of
existing editor state rather than adding new state to the component — the actions just observe what's already there and offer the right affordance.

Small change. Should have shipped it earlier.

If you're building content tools: audit where users are in the moment they need to act, and make sure the action is right there with them.