Android App Inventor Open Sourced, Code Released
Last year, Google decided to shutter Google Labs, a place where a number of incredibly wonderful experimental projects lived. Among the projects that got the ax was one of my favorites: Google's Android App Inventor.
Context & Ripple Effects
App Inventor arrived in mid-2010 as a Google Labs experiment aimed at letting non-programmers build Android apps by assembling blocks, and it immediately drew a debate over whether that was genuine empowerment or toy-making — the culture-wars argument O'Reilly hosted at launch. By December 2010 Google's research blog was still pitching it as a way to let everyone do great things. Then came the Labs shutdown, and the tool looked headed for the same grave as the rest of the portfolio.
Instead of killing it outright, Google has released the code, making App Inventor one of two Labs-era casualties this week to get an open-source exit — Sky Map was handed over on the same day — while Urchin, Picnik and the Social Graph API were simply discontinued. The release lands alongside a broader January squeeze in which new Google accounts are auto-enrolled in Google+ via mandatory Gmail and Profile creation.
First-order effects
- Educators, students and hobbyists who built on App Inventor keep their tooling alive under community stewardship rather than losing working projects to a corporate shutdown.
- Google sheds the maintenance cost of an experiment that never fit its product roadmap without absorbing the reputational hit of deleting a popular teaching tool.
Second-order effects
- Other Labs project teams now have a template to argue for: open-sourcing as the negotiated alternative to termination, which shifts the shutdown conversation from 'kill or keep' to 'kill or hand off'.
- Third parties who want a visual app-building on-ramp for Android can fork and extend the codebase, creating community-maintained competition for whatever official path Google offers next.
Third-order effects
- If the pattern holds, Google's experimental pipeline institutionalizes a two-track exit — quiet discontinuation for infrastructure-adjacent products like Social Graph API, open-source handoff for tools with passionate user bases — making Labs closures more survivable for users but also signaling that no Google experiment is guaranteed a home.
- The move sharpens the standing question about Android's openness: Google will release code when a project leaves the fold, yet keeps tight control over the platform itself — a tension Ars Technica would probe directly in its 2013 examination of how Google controls open source.
The trend: Google is normalizing open-source release as a graceful exit for beloved but unstrategic experiments, trading maintenance burdens for goodwill while consolidating its product core around Google+.