Google to launch Android developer SDK for wearable tech in 2 weeks
At SXSW today, Sundar Pichai, Google's SVP of Android, Apps and Chrome, announced that the company will soon release an Android developer SDK specifically designed for use with wearable devices.
Context & Ripple Effects
Sundar Pichai's SXSW announcement is the developer-facing piece of a wearable push Google has been assembling all year: code spotted in January pointed to a Fitness API letting Android apps read and edit activity data, and a February CNET report said Google and LG are building a smartwatch slated for a June unveiling. An SDK promised within two weeks gives third-party developers time to build for that hardware before it ships.
The pickup was unusually broad — The Verge, Wall Street Journal, CNET, Re/code, Telegraph, Engadget, TechCrunch and Forbes all ran the story the same day — reflecting how much weight the industry puts on whether Google can do for the wrist what Android did for phones.
First-order effects
- Android developers get an officially supported toolkit for building wearable apps within weeks, ending the era of undocumented workarounds for the wrist.
- Google's own June smartwatch plans gain an app ecosystem in advance, so the LG-built device launches with software rather than an empty home screen.
Second-order effects
- Samsung and other Android OEMs working on watches face a choice between building on Google's SDK or forking their own stack, repeating the phone-era fragmentation question.
- Developers' attention and porting budgets shift toward a new screen size, pressuring incumbents in fitness tracking and notification apps to expose their data through Android APIs.
Third-order effects
- If the pattern holds, Android stops being a phone OS extended outward and becomes a multi-device platform whose boundaries are set by whichever APIs Google ships first — activity data being the early candidate, per the Fitness API findings.
- Control of the wearable SDK becomes a gatekeeping position comparable to Play Services on phones, shaping which devices can run the ecosystem's apps.
The trend: Google is extending Android from phones to the body, with SDK cadence — not hardware launches — deciding who controls the wearable app ecosystem.