Gov 2.0 Is Not Just Government as a Platform

Tim O'Reilly's 'Government as a Platform' essay in the 2010 O'Reilly book Open Government had become, by 2012, the dominant rhetorical frame for the Gov 2.0 movement. The argument — modelling government on iOS or Twitter, providing open APIs and stable rails on which third-party developers could build, and treating citizens as users — was repeated at every Gov 2.0 conference, in most of the federal and state-level reform documents, and in the Code for America fellowship pitch.

The piece's pushback was that the platform metaphor, taken alone, was insufficient and in some ways actively misleading. Government isn't a platform in the iOS sense because most of what government does isn't an application that runs on top of public infrastructure — it's the institutional plumbing itself: courts, schools, social services, public health, regulatory enforcement. Treating government as a platform risked reducing the conversation to API-availability and developer-evangelism while leaving the harder service-delivery and institutional-culture questions unaddressed.

The argument anticipated the post-2013 maturation of the civic-tech conversation, where the platform-only framing was partly displaced by service-design framings (the GOV.UK / U.S. Digital Service / 18F school) and by the public-interest-tech framings that emphasised in-house institutional capacity over external developer ecosystems. The platform metaphor remains useful but is now usually paired with the service-design and institutional-capacity arguments this April 2012 piece was making.