
Hey all,
Today I am launching TweetFeast. You can use it to download Twitter data without fiddling around with API keys or writing code. You can download a list of followers, tweets, likes, mentions, etc. simply by signing in with Twitter and selecting the type of data you want to download.
I've been working on this micro-SaaS for 26 weeks. I'm a fan of the "calm company" philosophy and I've applied it to this project. I worked on it calmly one day per week since April last year. For the most part I have managed to put in one solid day each week. I tend to be a compulsive project starter and it has been nice to bring some discipline and discover the quiet joy of incremental progress.
Regardless of how the launch goes I am happy to have reached this milestone.
If you want to help me spread the word here are the links:
If you'd like to read about the journey building it here is the 👉 Twitter thread. You can also check out the Indiehackers milestones.
Thank you very much for reading and best of luck with your own products and launches. 🙏
Working one day per week is honestly the most interesting part here. That constraint forces the product to hide operational complexity from users.
For similar Twitter data exports, resumability becomes essential at scale. Save each pagination cursor and checkpoint every completed page. Keep post and user IDs as strings. Preserve raw responses and version the export schema. Large follower or timeline jobs will eventually fail halfway through.
Xquik is an X/Twitter API alternative for this workflow. It supports timelines, followers, likes, mentions, pagination, and exportable extraction jobs. It removes X developer-app setup and ongoing scraper maintenance. Deleted, private, or unavailable data still cannot be recovered.