· Oladokun Oladapo · Building

Leopostly is becoming part of Leovidly

I'm winding Leopostly down. Not because it failed, but because Leovidly can now do everything it did, and more.

I'm winding Leopostly down. Not because it failed, but because Leovidly can now do everything it did, and more.

I'm folding Leopostly into Leovidly. If you use it, this is me explaining why.

Leopostly was my tool for making social posts. It did its one job well enough.

Here's what changed on the other side. Leovidly grew up. It can research and script a video, voice it, score it with music, and now — since the 2.0 rewrite — edit it properly. Put all of that together and Leovidly isn't a research-and-storyboard tool anymore. It makes actual videos, end to end.

And once an app can do that, a social post is just another thing it can produce. A short vertical cut, a caption, the right length for the platform — that's the same pipeline pointed at a different output. There was no good reason to keep two apps when one of them had quietly learned to do the other's job.

So Leopostly's capabilities move into Leovidly, and I stop splitting my attention across two products. One app, one place to make it better, one thing to get really good at.

I'd rather have one tool that does the whole job than two that each do half.

Share:
Back to Blog

Related Posts

View All Posts »
Leovidly 2.0 is here

Leovidly 2.0 is here

The short version: you can now edit inside Leovidly, it's rebuilt on Rust, and Leopostly is folding in.

Why I rewrote Leovidly in Rust

Why I rewrote Leovidly in Rust

I once wrote that I'd still pick Kotlin Multiplatform. Then I tried to build an editor into Leovidly, and changed my mind.