I/O 2008
22 announcements tracked. Reality Score: 27% shipped substantially as promised.
Shipped 4
Android platform (pre-1.0 demo)
Engineering Director Steve Horowitz demoed an early Android build at the inaugural I/O, with refined UI, Street View with built-in compass, Maps, Pac-Man and pattern-based unlock; consumers were told the first Open Handset Alliance phones would ship in the second half of 2008.
The Android 1.0 SDK shipped on September 23, 2008 and the T-Mobile G1 launched October 22, 2008, both within the promised window. Android went on to dominate global mobile, holding around 70% worldwide market share by 2026 with Android 16 already at 7.5% adoption.
One of the few I/O 2008 announcements that delivered at promised scope and is still actively developed.
Google AJAX Libraries API (Hosted Libraries CDN)
Dion Almaer announced the AJAX Libraries API on May 27, 2008, the eve of I/O, with Google promising to permanently host jQuery, Prototype, script.aculo.us, MooTools, and Dojo on its global CDN with HTTP compression and minified versions.
Rebranded as Google Hosted Libraries and still operating in 2026, serving an estimated 2.3M live websites according to Wappalyzer. The dynamic google.load() loader is deprecated but the static URLs remain serving traffic.
Google App Engine open sign-ups
Vic Gundotra announced that App Engine was 'available to everyone, no waiting required' starting May 28, 2008, lifting the previous preview that had a 150,000-developer waiting list.
Open sign-ups went live as promised on May 28, 2008. App Engine is still operated by Google Cloud in 2026 with Python 3.14, Java, Go, Node, PHP and Ruby runtimes in GA, though it has become a niche product overshadowed by Cloud Run and GKE.
Delivered on the promised date; long-term success is more muted than the keynote pitch implied.
Jeff Dean's 'Underneath the Covers at Google' talk
Jeff Dean's standing-room session detailed GFS, BigTable, and MapReduce as the infrastructure powering Google, positioned as a glimpse of what App Engine developers were getting access to.
This was a research/architecture talk rather than a product announcement, so it cannot 'ship.' BigTable did become a Google Cloud product (Cloud Bigtable, GA in 2015) and MapReduce was supplanted by Cloud Dataflow.
Counts as shipped via Cloud Bigtable; classified loosely because it was a tech-disclosure talk, not a product pitch.
Shipped late 1
App Engine pricing tiers announced
Google announced a tentative pricing model: 500MB storage and roughly 5M pageviews per month free, then $0.10-$0.12 per CPU core-hour, $0.15-$0.18 per GB-month storage, and $0.11-$0.13 per GB outbound bandwidth once limits were exceeded.
Paid billing for App Engine did not actually go live until February 2009, roughly 9 months after the I/O announcement. The pricing model has since been completely overhauled multiple times around instance-hours and serverless requests.
Pricing was announced in May 2008 but not actually charged until early 2009.
Scaled back 6
App Engine Image manipulation API
Google announced an image-manipulation API for App Engine enabling server-side scaling, rotation, and cropping at I/O 2008.
Shipped with App Engine in 2008 but, like Memcache, is now classified as a 'legacy bundled service' tied to old runtimes. Google now points developers to Cloud Functions, third-party libraries, or external image services for new apps.
App Engine Memcache API
Brad Fitzpatrick's memcache integration was launched as one of two new App Engine APIs at I/O, providing high-performance in-memory caching to accelerate page rendering.
Memcache shipped at I/O 2008 and was used by developers for years, but Google has since reclassified it as a 'legacy bundled service' and recommends Memorystore (Redis) for new App Engine apps. Still works on the Python 2 / Java 8 legacy runtimes only.
Demoted to legacy status; no longer the recommended caching layer.
App Engine Python-only runtime
At launch App Engine was pitched as a general-purpose Google-scale platform for web apps, but the only supported language at I/O 2008 was Python 2.5, with no C extensions and no filesystem writes.
Java support did not arrive until April 2009, Go came in 2011, and PHP/Node arrived years later. Python 2.7 was deprecated and Python 3.x runtimes only became the recommended path starting in 2018. Modern App Engine eventually supported arbitrary languages, but the original 'Python is enough' framing was scaled back almost immediately.
The Python-only constraint was a major limitation that Google had to walk back.
Google Visualization API
Launched in March 2008 and showcased at I/O, the Visualization API was pitched as a generic way to render structured data via chart gadgets, with Google Spreadsheets as the first data source.
Renamed Google Charts and still maintained in 2026 with bimonthly releases (v50 current). Used by many Google services and external sites. However, the original 'gadgets' delivery model is deprecated and the Image Charts companion API was killed in 2012.
Library lives on; gadget-based distribution model and Image Charts companion are gone.
Google Web Toolkit 1.5 (Java 5 support)
Vic Gundotra announced a forthcoming GWT 1.5 release with Java 5 features including generics, enums, annotations, and enhanced for-loops, framing GWT as Google's strategic answer to writing AJAX without JavaScript.
GWT 1.5 shipped in August 2008. The toolkit is now community-maintained on gwtproject.org rather than primarily by Google; releases continued (GWT 2.12 in 2024, 2.12.2 in 2025) but GWT was de-emphasized inside Google in favor of Dart and then Angular/TypeScript.
Still alive as an open-source project but no longer a Google strategic platform.
Open Handset Alliance momentum
The OHA was prominently featured at I/O 2008 as the broad industry consortium of carriers, OEMs and chip vendors that would deliver Android together; consumers were promised the first OHA handsets in the second half of 2008.
The G1 launched October 22, 2008 as promised. However, the OHA itself has effectively been moribund since around 2011: its website lists 84 members but shows no updates after 2011, and Google has unilaterally controlled AOSP and the Android trademark since. It exists in name only in 2026.
Android shipped; the 'alliance' framing has been hollowed out.
Rebranded 1
Gears as the bridge to HTML5
The 'HTML5, Brought to You by Gears' session pitched Gears APIs (LocalServer, Database, WorkerPool, Geolocation) as the de-facto reference implementation that browser vendors would adopt as HTML5.
Browsers did adopt analogous standards: Web Workers, Web Storage, IndexedDB (replacing Gears Database), Application Cache then Service Workers, and the Geolocation API. The standards survived; the Gears product that delivered them died in 2011. So the standards-bridge promise was partially fulfilled by the W3C, not by Google's Gears.
The capabilities moved into web standards; the Gears brand and runtime were retired.
Vapor 1
Open Embedded Experiences (OpenSocial)
Discussed as part of OpenSocial's future, Embedded Experiences promised a mechanism for inserting apps into Activity Streams, email messages, and Atom feeds with contextual data so host apps could render them.
Embedded Experiences was eventually formalized in OpenSocial 2.5.1 (W3C member submission in February 2014), but with OpenSocial dissolved into W3C in December 2014 and no major modern consumer container, it never reached the 'embed an app anywhere on the social web' promise.
Spec existed; meaningful real-world deployment never happened.
Killed 9
AJAX Search & Feed APIs
I/O 2008 sessions 'Spice up Your Web Apps with Google AJAX APIs' and 'A World Beyond AJAX' promoted the AJAX Search API (web/video/news/maps/blog results in any site) and AJAX Feed API (any RSS/Atom feed via JavaScript) as the modern replacements for the retired SOAP Search API.
Both APIs were officially deprecated on November 1, 2010 with a 3-year wind-down. The AJAX Search API was effectively dead by 2014. Custom Search JSON API exists today but is paid and rate-limited, nowhere near the original 'just drop this in your page' pitch.
GData Protocol & client libraries
GData (Atom + AtomPub + JSON) was presented across I/O 2008 sessions as the unified read/write protocol for nearly every Google service, with client libraries in Java, JavaScript, .NET, PHP, Python, and Objective-C.
Most GData APIs were deprecated through the early-to-mid 2010s in favor of v3+ JSON REST APIs (e.g., YouTube Data API v3, Calendar API v3). Google's own GData docs page now warns that 'several of the APIs listed on this page are deprecated or obsolete.'
Google Friend Connect
Previewed at Campfire One on May 13, 2008 and discussed at I/O, Friend Connect was pitched as a way for any website owner to drop a JavaScript snippet and make their site instantly social, pulling in identity and friends from MySpace, Plaxo, Orkut, Twitter, and (Google hoped) Facebook.
Facebook blocked Friend Connect from accessing its data within days of launch. The service did reach ~8M sites per month by late 2009 but Google retired Friend Connect on all non-Blogger sites on March 1, 2012 and removed it from Blogger on January 11, 2016 in favor of Google+ badges.
Google Gears (offline web)
Gears was promoted across multiple I/O 2008 sessions ('HTML5, Brought to You by Gears', 'Gears for Mobile', 'Client-Side Search Engine with Gears') as the bridge to offline web apps, with the WorkerPool API positioned as the future of background JavaScript.
Google stopped Gears development on February 19, 2010, ostensibly to fold features into HTML5. Gears was removed from Chrome on June 7, 2011, and from Gmail/Calendar on December 1, 2011. The HTML5 features (Web Workers, IndexedDB, Application Cache, then Service Workers) did eventually ship in standards form, but the Gears product was killed.
Pitched as the offline-web platform at I/O 2008, formally killed within 3 years.
Google Maps API for Flash
Michael Jones presented the new Maps API for Flash at I/O 2008, pitched as the long-awaited way to embed Google Maps in Flash/Flex apps using ActionScript, with Flash-rendered tiles, markers, info windows, and animation.
Shipped in May 2008. Officially deprecated on September 2, 2011 and shut off on September 2, 2014, with Google urging migration to the JavaScript Maps API v3 as Flash itself died.
iGoogle Developer Sandbox & OpenSocial container
iGoogle was positioned across I/O 2008 sessions as a flagship OpenSocial container with a canvas view, opening 'tens of millions of users' to gadget developers via the new developer sandbox.
Google announced the retirement of iGoogle in July 2012 and shut it down on November 1, 2013. The legacy gadget API was deprecated September 14, 2009 and stopped functioning on September 14, 2010, just over two years after I/O 2008.
OpenSocial cross-network API
OpenSocial was positioned as the open standard letting one social app run on MySpace, Orkut, hi5, LinkedIn, Ning, and others, with the OpenSocial Foundation formalized in March 2008 and major sessions at I/O dedicated to v0.8 and 'Meet The Containers.'
Containers shipped but Facebook never joined, and once Facebook Platform won the developer mindshare the standard withered. The OpenSocial Foundation handed everything to the W3C Social Web Working Group on December 16, 2014. By 2026 essentially no consumer social network implements it.
Existed as a spec but never delivered on its 'standard for the social web' pitch.
OpenSocial REST/JSON-RPC API
Sessions at I/O 2008 unveiled the OpenSocial server-to-server REST protocol and the JSON-RPC variant added in spring 2008, intended to let backends read friends, activities, and persistence across containers.
The REST API was implemented in Apache Shindig and by Orkut, MySpace, and a handful of others, but it never reached Facebook or Twitter. With OpenSocial itself absorbed by the W3C in 2014, the REST protocol effectively died.
YouTube Chromeless Player & JavaScript API
I/O 2008 'Design Your Own YouTube Player' session showcased the Chromeless Player plus a JavaScript Player API letting developers fully control embedded YouTube video.
The Chromeless Player was a Flash-based product; it was deprecated alongside Flash and effectively gone by 2015 when YouTube switched to HTML5 by default. The successor iframe Player API does provide the same control today, but the original named product is dead.
Replaced by the iframe Player API; original Flash Chromeless Player is gone.