Shipped: moved post/schedule/draft actions into the thread editor — completion rates were dying at the last step

Quick milestone post. We shipped a UX fix this week that I should have caught earlier.

The thread editor had a completion problem. Users would write a full thread - sometimes 5-6 tweets - then bounce before actually scheduling or posting it. The actions to do something with the thread lived on a different screen. One extra navigation step, but it was enough.

Moved post now, schedule, and save draft directly into the editor. Actions appear once you have content in the first tweet. If you've already picked a schedule time, the button label reflects that. If not, it prompts you to set one or post immediately.

The implementation was the interesting part. The editor was already tracking per-tweet character counts, ordering, and platform context (we support X, LinkedIn, Threads, etc. from one composer). Wiring in the full post lifecycle without the component feeling overloaded took a few iterations - ended up leaning on conditional rendering tied to content state rather than a separate "ready to publish" mode.

For other founders: if you're seeing drop-off at the end of a creation flow, check whether the final action is one step too many away from where the user's attention already is.