Android SDK m5-rc14 now available
On behalf of the entire Android team, I'm happy to let you know that an updated version of the Android SDK — we're calling it m5-rc14 — is now available. Today, we're continuing the early look at the Android SDK that we started back in November …
Context & Ripple Effects
Three months after Google opened its Android OS early-look SDK in November 2007, m5-rc14 is the second public milestone of the platform — still a preview, still without hardware to run it on, but evidence the project is moving on a schedule rather than stalling. The same-day pickup by CNET alongside the developer-blog post shows the SDK cycle alone counts as industry news.
What matters here is cadence: Google is treating the SDK as a rolling product, publishing updates to a developer base that is writing real code against APIs that are still moving. With no discussion chatter recorded around this drop, the audience being managed is the one already inside the tent.
First-order effects
- Developers who built against the November preview now have to re-validate their work against m5-rc14's updated APIs, making early adopters de facto testers for Google's pre-release platform.
- Google converts each release into a feedback loop, harvesting compatibility bugs and API complaints from outside developers months before any commercial Android device exists.
Second-order effects
- The steady drumbeat of SDK builds keeps third-party code accumulating on Android's stack during the pre-launch window, raising the cost for those same developers to start over on a competing mobile platform whose tooling is less visible.
- Coverage like CNET's turns routine engineering drops into recruitment marketing, letting Google court developers through the tech press rather than paid outreach.
Third-order effects
- If the milestone pattern holds, Android will arrive as an app ecosystem first and a handset second — the SDK, not the device, becomes the platform's primary product surface, with Google's update rhythm setting expectations for every future OS generation.
- A public, iterated SDK also shifts power toward outside developers in platform governance: APIs get debated and shaped before launch rather than dictated after it.
The trend: Mobile platforms are increasingly launched SDK-first, with Google iterating Android's public tools in the open for months before the first handset ships.