App Inventor and the culture wars
Google's new App Inventor gets to the heart of the cultural difference between Apple and Google. If you haven't seen it yet, App Inventor is an experimental new SDK for the Android platform. What's different about App Inventor is that there's practically …
Context & Ripple Effects
App Inventor lands nearly three years after Ars Technica's early verdict that Android development was a mixed bag: the toolchain was powerful but programmer-only. Google's answer is an experimental SDK that removes the programming prerequisite entirely, opening Android app creation to people who would never touch Eclipse or the official NDK-era stack.
The timing sharpens the contrast the piece draws. On the very day App Inventor surfaced, Apple shipped iOS 4.0.1 to address iPhone 4 reception complaints — one company adjusting its curated device story while the other loosens access to its platform. The two moves are opposite expressions of the same competitive moment.
First-order effects
- Non-programmers gain a direct path to shipping working Android apps, expanding Google's developer funnel beyond trained engineers without Google approving each creation.
- Apple's closed-review model now has an explicit counterexample running on the rival platform at the height of the iPhone 4 antenna controversy.
Second-order effects
- Educators and hobbyist communities get a low-cost on-ramp into mobile development on Android, building loyalty among users too young or untrained to have chosen a platform yet.
- Apple faces renewed pressure to justify its gatekeeping: if Google demonstrates that unvetted, user-built apps are viable at scale, 'curated means safe' becomes a claim Apple has to argue rather than assume.
Third-order effects
- If openness-of-tools becomes a differentiator, mobile competition shifts from device specs toward who can recruit the largest pool of casual creators — with Android's looser governance as both its recruiting advantage and its fragmentation liability.
- Block-based, no-code authoring points toward a broader pattern where platforms compete on accessibility of their SDKs, forcing every major vendor to decide how much control it trades for reach.
The trend: Mobile platform competition in 2010 is moving beyond hardware toward the openness of developer toolchains, with Google betting that radical accessibility beats Apple's curation.