Describing an app to an AI and shipping whatever comes out — 'vibe coding' — is fine for a weekend toy. For a social media scheduler that touches Meta, X, LinkedIn, TikTok and YouTube APIs, it's a fast road to token leaks, silent publish failures, and a queue that quietly drops posts at 3 a.m.
What tends to break
- OAuth refresh flows across five providers, each with different token lifetimes
- Rate limits and per-platform quotas that a generated prototype ignores
- Media pipelines: aspect ratios, codec requirements, and thumbnail generation per network
- Retry and idempotency logic — reposting the same tweet twice is worse than not posting it
When vibe coding is fine
Prototyping the UI, exploring a calendar layout, or drafting a caption generator against your own account are perfectly good uses. Trusting that output with a client roster is not.