Google Maps Mashups 2.0
When we were building the original Google Maps site, we envisioned that it would eventually become a platform for navigating all kinds of location-based information, such as home listings and travel information. Within weeks of the launch of Google Maps …
Context & Ripple Effects
Mapplets are Google formalizing what its users already did: developers began building Maps mashups within weeks of the service's launch, and Google's own team says it always intended Maps as a platform for location-based information like home listings and travel data, not just a directions tool.
The move lands on a map that had already been absorbing more content layers — clickable transit-stop icons arrived in June 2007 — so Mapplets extend that trajectory by letting third parties run their gadgets inside Google's interface rather than on separate sites. The breadth of same-day pickup from Reuters to Download Squad signals how closely the developer ecosystem is watching this.
First-order effects
- Developers who were scraping together standalone mashup sites get an official distribution channel inside Google Maps itself, with Google hosting and surfacing their gadgets to every Maps visitor.
Second-order effects
- Standalone mashup sites built on the Maps API now compete with in-map gadgets for attention, pushing developers toward whatever surface Google controls; rivals' mapping products face pressure to open equivalent gadget platforms of their own.
Third-order effects
- If maps consolidate as platforms-within-a-platform, the locus of innovation shifts from independent sites to whatever distribution the map owner permits — an early template for how consumer web services absorb third-party development into hosted ecosystems.
The trend: Mapping is shifting from a single-purpose direction tool to a hosted platform where third-party data lives inside one company's interface, with Google setting the terms of access.