Twitter client Kiwi lets you style, hide, organize tweets
PEOPLE WHO READ THIS ALSO READ: — You would be right in many ways if you said that Twitter clients figuratively cost ten cents for every twelve apps you can round up. They typically compete in terms of redesigning …
Context & Ripple Effects
By December 2009 Twitter's API had already produced more than 50,000 applications, and reviewers treated clients as near-commodities — Macworld opens by noting they compete mostly on redesign, a wave this desk tracked earlier in the year with an Excel-lookalike Twitter client pitched at office procrastinators. Kiwi's answer to that saturation is filtering rather than skinning: styling, hiding, and organizing tweets.
The timing cuts two ways. Commentators had spent November 2009 arguing Twitter suffered from information overload, which is exactly the pain Kiwi sells against. But days before the launch, Twitter unveiled its Contributors feature to court big business and began winding down the open API access that made tools like Kiwi possible at all — a client built entirely on someone else's interface, launching as that host tightens its grip.
First-order effects
- Kiwi enters a client market where differentiation by visual redesign has stopped working, betting that tweet-level styling, muting, and organization win users drowning in volume.
- Every competing Mac and desktop Twitter client now faces a bar raised from 'looks nice' to 'helps me filter,' forcing feature work toward hide/mute and organizational tooling.
Second-order effects
- As Twitter ends the open-API era, third-party clients like Kiwi become structurally dependent on whatever access Twitter still grants — product roadmaps shift from features to surviving the platform's policy decisions.
- Twitter's own push upmarket, marked by the Contributors feature for big business, pulls official attention toward enterprise accounts and away from hobbyist clients, leaving independent developers to differentiate or die on filtering alone.
Third-order effects
- The pattern points toward platform owners reclaiming the client layer: an API that seeded tens of thousands of apps becomes a controlled surface, and client developers' value migrates from building interfaces to renting permission to build them.
- If filtering and organization prove to be what overloaded users pay for, curation — not raw access — becomes the durable product layer atop real-time streams, regardless of who owns the pipe.
The trend: Consumer platforms that opened their APIs wide enough to spawn commodity client ecosystems are starting to close them, shifting the battleground from interface design to filtering and curated access.