The Evolving Ecosystem
Just over four months ago, at Chirp, our Twitter developer conference, I talked about how “Twitter is too hard” and what we're doing to address that. — One major area of difficulty I highlighted was getting Twitter on your phone.
Context & Ripple Effects
Twitter had already put a first-party mobile foothold in place with Twitter for iPhone, while June coverage argued the company needed to improve its execution quickly. The platform’s own framing identifies phone access as a usability bottleneck even as Tweets encompass links, photos, video, hashtags and check-ins.
The iPad release and mandatory OAuth adoption show Twitter addressing two connected constraints: making the service easier to use across devices and making third-party access less dependent on stored passwords.
First-order effects
- Twitter gains an iPad-specific surface for presenting richer Tweet content, extending its first-party mobile experience beyond the iPhone.
- Third-party Twitter applications must use OAuth, shifting account access away from locally stored user passwords.
Second-order effects
- Client developers have to absorb the OAuth transition while differentiating their interfaces and content experiences from Twitter’s expanding first-party apps.
- Publishers using Twitter’s Tweet Button and bookmarklet gain more ways to turn off-site pages into shared Tweets, reinforcing Twitter as a distribution layer for web content.
Third-order effects
- If first-party device apps and shared authentication standards continue to expand together, Twitter’s ecosystem is likely to concentrate around platform-controlled access and presentation rules rather than password-based client relationships.
The trend: Twitter is evolving from a standalone messaging service into a mobile-and-web distribution platform whose developer ecosystem depends on standardized, platform-controlled access.