Sameer Ali is the sort of developer who, when confronted with a repetitive activity, builds an app to repair it. He is additionally a creator, publishing coding content material on Instagram, TikTok, and YouTube beneath the title coding.kitty — and his build-an-app strategy was precisely how he eliminated nearly all of the admin from his social presence.
Beforehand, each completed video meant 15–20 minutes of busywork: downloading, re-uploading to every platform, rewriting captions, setting metadata, scheduling, and manually updating his venture board. His customized desktop app — the aptly named coding.kitty engine — utterly modified that. It handles the whole manufacturing pipeline from ideation and scripting by means of to subtitling, scheduling, and analytics.
However when it got here to really getting the movies onto Instagram, TikTok, and YouTube, even Sameer determined to not construct that half himself. He turned to Buffer’s API as a substitute.
Why a full-stack engineer selected not to construct it himself
Sameer may have used Instagram, TikTok, and YouTube’s native APIs. However that might have meant three separate OAuth flows, three totally different add mechanisms, three units of fee limits, and a customized scheduler service to maintain all of it working on time. He described it as constructing a complete product on high of the product he was already constructing.
As a substitute, Buffer handles all of it.
One GraphQL API, one auth movement, and Sameer can move YouTube titles, privateness settings, classes, Instagram Reel vs. submit sort, first feedback, and TikTok titles by means of a single mutation. He had the total integration working in a number of days.
“I desire a assure that my posts might be posted on the specified time,” Sameer says. “Buffer handles the scheduling half reliably, and I can see every part in a calendar view.”
He additionally preferred that the GraphQL schema coated every part he wanted in a single place: create, delete, fetch posts, fetch channels — with out him having to sew collectively separate endpoints.
From 1 YouTube video to a number of posts in 2 minutes
As a long-time creator and marketer, I am cannot recover from how environment friendly Sameer’s app + Buffer API workflow is.
It kicks off when a video will get marked “able to schedule” in Jira. The coding.kitty engine picks it up robotically, downloads the subtitled video from the Jira attachment, and robotically resizes it to suit Instagram Reels’ vertical format. The video uploads to Sameer’s cloud storage and turns into accessible through a public URL.
From there, Sameer picks the goal platforms, generates a platform-specific caption (his built-in AI is aware of the character limits and conventions for every platform, so he isn’t rewriting the very same message 3 times), and scrubs by means of the video to pick out a thumbnail body.
Then coding.kitty hits Buffer’s CreatePost GraphQL mutation that features the video URL, caption, thumbnail, and all platform-specific metadata. Buffer fetches the video from R2, queues it for publishing, and the Jira ticket auto-transitions to the following column.
Two minutes, achieved.
A calendar and sensible submit scheduling
If that weren’t sufficient, Sameer constructed a pair extra helpful options into his app. For starters, his personal calendar view.
coding.kitty additionally pulls scheduled posts again from Buffer to show its personal calendar view. Sameer can spot gaps in his schedule, keep away from posting conflicts, and reschedule content material by dragging posts round — all with out leaving his app.
And maybe my favourite bonus characteristic: An AI agent that makes all the selections round publishing.
As a result of coding.kitty has entry to latest posts, and the total queue of movies able to go, Sameer can hand off the publishing choice totally to the agent. It checks what’s been posted just lately, picks the proper content material, platform, and timing, and schedules it by means of the Buffer API.
Fairly cool, proper?
Strive it your self
Sameer constructed a desktop app. You may construct a CLI device, a Slack bot, or an n8n workflow. No matter you construct, you possibly can give attention to that — the publishing piece is already solved.
Buffer’s API is now accessible. You can begin constructing at present.
