I feel like it's a bit hypocritical to provide an API but not be a consumer of that same API. So I'm fixing that!
Last week I pivoted my business to a pure API model. This week I'm building some things on top of the API to both put the API through its paces, but also to act as use-cases / demos for potential customers browsing my marketing site.
Introducing Tweetagram! Auto generate a visual Instagram post (or story) from a tweet url:
So far I'm really enjoying my new product focus as an API. It keeps the core product scope manageable, but at the same time gives you license to build some neat apps on top of it. I think those two things are good qualities to have for an indie hacker product.
I don't know if the API product strategy will work out business-wise, it's too early to say. But I can say right now that it is a lot of fun! :)