Facebook Woos Mobile Developers, but Is It Too Late?
Not so long ago, the key to building a successful app business required piggybacking on an existing big network like Facebook. — But relying on Facebook for your paycheck also meant being subject to the whims of Facebook CEO Mark Zuckerberg.
Context & Ripple Effects
Facebook's developer courtship is a rerun with a new cast: the 2007 app feeding frenzy made the platform the place to build, then a wave of developer fear and open questions about defection followed within months, as builders realized the rules could change beneath them.
The pattern hardened through the following years — rising costs left developers in the lurch in 2011, and by 2012 building for Facebook was openly framed as a dance with the devil. The f8 push to woo mobile developers now arrives against exactly that track record, which is why Re/code's headline asks whether the trust is already spent.
First-order effects
- Facebook is asking mobile developers to rebuild on its platform, but the confirmed dependency — businesses subject to Mark Zuckerberg's whims — means every pitch has to be priced against the risk of unilateral rule changes.
- Chris Cox's promotion to Chief Product Officer days before f8 puts a News Feed and Social By Design veteran in charge of the developer-facing product story, while the company deliberately makes no broader organizational changes.
Second-order effects
- Developers who were burned in the 2007-2011 cycles now have credible alternatives on mobile, so Facebook's recruiting costs rise — it must compete for apps it once attracted by default, shifting bargaining power toward developers choosing among platforms.
- Rumored coordinated f8 announcements with an ecommerce partner and a user testing service suggest Facebook is bundling distribution and tooling rather than offering the network alone, raising the integration bar rivals would need to match.
Third-order effects
- If the wooing fails, the structural lesson for the industry is that platform power decays when its terms are set unilaterally: ecosystems consolidate around platforms whose rules developers can underwrite, not merely tolerate.
- A successful reset would formalize a recurring cycle — platform opens, developers over-invest, platform recentralizes — making developer diversification across multiple networks a standing cost of doing business rather than an option.
The trend: Social platforms are entering a second round of developer recruitment on mobile, where the deciding currency is no longer audience size alone but credible guarantees against arbitrary platform changes.