Why does the Meta Threads API make me feel so disappointed?

To be honest, I'm quite lazy when it comes to writing articles. When you see that I'm writing this article about the Threads API, you'll understand the intense frustration I have towards it. For those who don't know, the Threads API is an official third-party code interface released by Threads for developers to call certain development capabilities. When Threads released their API on June 18th, I was very excited and immediately began researching and developing an independent product. However, it only took a month (today is exactly July 18th) for me to become completely disappointed with the Threads API. Let me explain what exactly happened.

I independently developed a product called ThreadsDashboard, which is a Threads data analysis product based on the official API of the Meta Threads app. You can see key data indicators and trend graphs about your Threads account, such as the number of followers, post exposure, reposts, likes, etc.

The implementation of this product was quite fast. Using a series of technology stacks like Nextjs, the route to creating such a product is quite clear. Throughout the development process, the most difficult and complex part was the Threads API itself. Here are a few incomprehensible points:

Leave a Comment