The networks I chose not to support (yet)
People ask why a scheduler with seventeen networks does not have their favourite one. Usually there is a specific reason, and it is rarely "I didn't get to it".
These come from research I did in September, reading each platform's official documentation. Platforms change; this is a snapshot.
No way in
- Substack has no API for publishing posts.
- WhatsApp Channels has no official API at all.
- Medium and Hashnode were closed or paywalled for this use.
Nothing to build against - any workaround would break the platform's terms and break the product the day they notice.
Closed doors
- Reddit is restricting new API access, and commercial use needs an agreement.
- Snapchat needs an allowlist and a business organisation.
- beehiiv's posting API is an enterprise-only beta.
Possible, at a price
X charges per post through its API, more for posts with a link - paid by the app, not the user. It only makes sense on paid plans with usage metering.
These are "later", not "never".
What gets built
The networks that made it had a few things in common: an official way to publish, no company paperwork to get started, and costs that do not grow with every post.
Discord, Telegram, Slack, Bluesky, Mastodon and DEV all qualified quickly - and became some of the first networks to ship.
The filter
- Is there an official publishing API?
- Can I get access as I am today, without a company or an enterprise contract?
- Does it cost per post, and who pays?
- Will people in Clienzo's audience actually use it?
Four yeses, it goes on the list. Anything else gets a dated note explaining why not - so the next time someone asks, the answer is already written.
Originally published on jonasnguyen.com, where I write about building Clienzo and the next startups.
Comments
No comments yet. Start the discussion.