Google I/O 2015 to be held May 28-29 at Moscone Center West in San Francisco, registration begins March 17
Stephen Hall / 9to5Google :
Context & Ripple Effects
Google's annual developer conference has long been announced the same way — a date-and-venue drop months ahead, with a registration window that functions as a ticket lottery. The related coverage traces that ritual across editions: after this 2015 stop at Moscone Center West, Google shifted I/O to the Shoreline Amphitheatre in Mountain View for 2016 and kept returning through the 2017 edition, before eventually going virtual for I/O 2022 with only employees and partners on site.
That makes the May 28-29 Moscone booking notable in retrospect: it lands near the end of Google's downtown-San Francisco era for I/O, before the company settled into a fixed home base it controls rather than a convention center it rents.
First-order effects
- Developers get a defined window — registration opens March 17 for the May 28-29 dates — making early sign-up the deciding factor for attendance at a conference that historically oversubscribes.
- Moscone Center West and surrounding San Francisco hotels and restaurants absorb a concentrated influx of thousands of attendees for the two-day run.
Second-order effects
- The following year's move to Shoreline Amphitheatre relieves Google of Moscone-style venue competition and scheduling constraints, letting it stage outdoor keynotes and demos on its own timetable.
- San Francisco loses a recurring, high-spend tech audience as the conference anchors permanently in Mountain View — a small but visible slice of the city's convention economy migrating south.
Third-order effects
- If the pattern holds — Shoreline through 2016-2019, then the virtual 2022 format with a limited live audience — developer conferences trend away from rented urban venues toward company-controlled or broadcast-first formats, trading city spectacle for cost and logistical control.
The trend: Flagship developer conferences are drifting from rented downtown convention centers toward company-owned venues and hybrid/virtual formats, with Google's post-Moscone I/O run as the clearest example.