Facebook's platform: Rebuilding the plane in midflight
Facebook's developer platform was a watershed. It gave outside companies unprecedented access to users of a major social network. But the platform, launched in May, has come under increasing scrutiny.
Context & Ripple Effects
When Facebook opened its platform in May 2007, early analysts treated it as a watershed — an unprecedented handoff of social-graph access to outside companies, dissected within weeks in early platform analysis and structural critiques like Deconstructing Facebook. By late 2007 the mood had shifted: skeptics argued the platform's economics were oversold in Facebook debunked, and developers were openly anxious about their dependence on shifting rules in Fear Among Facebook Developers.
First-order effects
- Developers who built businesses on Facebook's APIs now face rule changes and tightening review while their apps are live — the 'rebuilding the plane in midflight' problem hits them first, since any access change ripples straight into their products.
- Facebook itself must trade off growth against control: every scandal or abuse traced to the platform increases pressure to restrict the very openness that made it a watershed.
Second-order effects
- Developer confidence becomes a competitive asset: if third parties can't trust platform stability, they hedge by spreading effort across multiple networks rather than betting on one, weakening the network-effect moat the platform was meant to build.
- Scrutiny over who gets access to user data forces Facebook into a gatekeeping role — deciding which apps merit trust — which shifts power from the long tail of developers toward a few favored partners.
Third-order effects
- If the pattern holds, open-by-default social platforms give way to governed ones where access is conditional, audited, and revocable — turning trust from an afterthought into core platform infrastructure.
- The eventual verdict on this era, echoed years later in PandoDaily's retrospective on Platform as a missed opportunity, suggests the industry lesson: platforms that fail to institutionalize governance early end up either over-correcting into walled gardens or ceding the ecosystem they created.
The trend: This is an early data point in the arc from open-by-default developer platforms toward tightly governed ecosystems where access is a privilege conditioned on trust, not a right granted at launch.