The future of O3D
We launched the O3D API about a year ago to start a discussion within the web community about establishing a new standard for 3D graphics on the web. Since then, we've also helped develop WebGL, a 3D graphics API based on OpenGL ES 2.0 that has gradually emerged as a standard …
Context & Ripple Effects
A year after Google launched the O3D API to provoke a debate about how browsers should render 3D — covered at the time as Google joining the push for a 3D Web standard with a new plugin and API — the experiment has produced an answer, and it isn't O3D itself. The company says WebGL, the OpenGL ES 2.0-based API it helped develop inside the standards process, has gradually emerged as that standard.
The pivot Ajaxian flagged as a win for standards is the substance of the announcement: rather than continue O3D as a competing plugin API, Google is repositioning it as a JavaScript library layered on WebGL. A proprietary starting point is being folded back into the open specification it was meant to catalyze.
First-order effects
- Developers who built against the O3D plugin face a migration path to a JavaScript library running on WebGL, with the plugin's role reduced to bridge rather than destination.
Second-order effects
- Browser vendors now have one convergent target instead of two: engine and tool makers weighing a web-3D strategy can standardize on WebGL without hedging against Google's plugin.
Third-order effects
- If the pattern holds, the launch-an-API-to-seed-the-debate play becomes a template for how Google and peers steer web platform standards — proprietary experiments as scaffolding for specifications, with plugins losing to capabilities built natively into browsers.
The trend: Web graphics is consolidating around standardized in-browser APIs like WebGL, displacing vendor-controlled plugin runtimes.