SMF·TYPEFULLY
Can a prompt replace Typefully?
Social media — thread writing + scheduling
Exhibit tracking slip
Verdict
A distraction-free thread composer with a posting queue is a real weekend build. The catch isn't the code — it's that X's own API pricing for posting access costs more than Typefully's subscription, which makes the honest DIY version cheaper to build but not necessarily cheaper to run.
Exhibit A — The prompt
Received on30.07.2026Build a distraction-free thread composer: split a long draft into individual posts, show a live character count per post, support drag-to-reorder, and autosave every draft to a database. Add a scheduling queue where a post either takes the next open slot from a small set of configured posting times or gets pinned to an exact time; show the queue grouped by day. A background job publishes due posts and records a sent/failed status per item. Post through the X API — be explicit in the README that X's free API tier is read-only, and posting requires a paid tier that costs more than most social-scheduling subscriptions; that's the actual moat here, not the code. Add a 'copy thread to clipboard' fallback plus a browser notification at the scheduled time, so the tool is still useful for someone unwilling to pay X for API access — they just post manually when notified.
Do not build analytics on published posts or AI rewrite suggestions — those need either a data pipeline that reads back post performance or an LLM integration, both real scope beyond a composer and queue.Opening prefills the prompt — press enter to run it.
Exhibit B — What you lose
- B.1 analytics on published posts
- B.2 AI rewrite suggestions
- B.3 multi-account and team features
- B.4 a posting path that doesn't depend on X's own paid API tier
Prior art
Exhibit C — Why people still pay: social API/polish
The composer itself is the easy part — people pay so posting just works without them having to deal with X's API pricing and policy changes directly.
Questions
Can I import my existing Typefully drafts and queue?
Not automatically — there's no structured export for drafts. Recreating a queue is usually quick since most people only have a handful of scheduled posts at any time.
Will it work on my phone?
As a responsive web page, yes, for browsing the queue and reading drafts. Composing a long thread is realistically a desktop task, and the browser notification fallback needs the tab open.
What does it cost to run?
Hosting and a database, typically a few dollars a month — but the real cost is X's paid API tier if you want automatic posting, which this build can't make cheaper, only optional.
What's the one thing that doesn't survive the rebuild?
Posting without paying X directly. Typefully absorbs that API cost into its subscription; a self-hosted composer either pays the same API fee itself or falls back to manual copy-paste posting.
Related tools
Receipt