VidSyndicate
Social Media Publishing, Video Distribution, Cross-Platform
-
1
The API makes VidSyndicate feel less like a social publishing tool and more like infrastructure other products can build on. The OAuth step seems like an important transition point for that broader use case.
-
1
I agree. I think the direction could serve both.
One use case is the everyday user who wants a simple dashboard to publish their videos across multiple platforms. That could be a content creator, realtor, lawn care company, local business, or literally almost any business that uses social media.
The second use case is developers and companies that want to add social publishing to their own product or workflow. Instead of building, maintaining, and managing separate integrations with every social platform, they could use the VidSyndicate API as the publishing layer behind their application.
That second use case is where I think OAuth becomes especially important. VidSyndicate can still be a standalone product, but it can also become infrastructure that other products build on.
-
1
The infrastructure angle is definitely the more interesting one. If you’re pursuing both, I’d be curious which side you expect to become the stronger business over time. If you’re open to continuing the conversation, what’s the best email to reach you at?
-
-
-
1
10+ Meta reviews and roughly the same with TikTok is quite a journey. Curious which platform has been the biggest headache so far.
-
1
For me, it’s not really the platforms themselves—it’s learning how to make the screencast clearly demonstrate each permission being used. When I first started, I thought some things were “implied,” but to an auditor, they aren’t. I had to learn how to present each feature so they can literally check every box during the review.
I still get rejections from time to time, but I’ve never been told a flat-out “no.” Usually it’s just figuring out exactly what they want demonstrated, fixing it, and resubmitting.
-
1
That makes sense. The review process sounds like its own product problem sometimes. I’d be curious what you’ve learned about getting those approvals through efficiently.
-
1
My experience has been that keeping each review focused on just one or two permissions makes the process a lot easier. Trying to get five or ten permissions approved at once creates a lot more opportunities for something to get questioned or rejected.
If you have the runway to roll features out gradually and account for review time, I think that’s the better approach. We also have AWS SaaS founder credits, so we’re not under pressure to rush the product out just to start covering infrastructure costs. That gives us the ability to build and release things the right way.
It also helps that I’m a DevOps engineer and handle the development and infrastructure myself. I’m not paying an outside team every time I need to make a change for a reviewer, so I can iterate, resubmit, and learn from each review without those cycles becoming expensive.
-
1
That makes a lot of sense, especially the point about review cycles becoming cheaper when you control the infrastructure yourself. I’d be interested in continuing the conversation — what’s the best email to reach you at?
-
1
Happy to continue the conversation. You can sign up at VidSyndicate.com and reach me directly through support there. That’s probably the easiest way to connect.
-
1
Thanks! I’ve just sent it over.
Looking forward to hearing your thoughts whenever you have a chance.
-
-
-
-
-
-
Comment