Android 2.3.3 Platform, New NFC Capabilities
Several weeks ago we released Android 2.3, which introduced several new forms of communication for developers and users. One of those, Near Field Communications (NFC), let developers get started creating a new class of contactless, proximity-based applications for users.
Context & Ripple Effects
The arc here runs through hardware before software: Google put an NFC chip in the Nexus S in December 2010 and turned Google Places window stickers into NFC tags, giving the radio something to touch in the real world. Android 2.3 followed with the first developer-facing NFC hooks, and this 2.3.3 release extends them so contactless, proximity-based applications become a supported class of app rather than an experiment.
The timing matters because Google is also mid-flight on tablets — its sneak peek of Android 3.0 Honeycomb came a month earlier — so the platform team is pushing communication capabilities across both form factors at once. For developers, the question shifts from 'can Android do NFC' to which handset inventory actually ships with it.
First-order effects
- Developers targeting Android 2.3.3 can now ship contactless, proximity-based applications against the one shipping device that has the hardware, the Nexus S, with Google's own Places stickers serving as ready-made NFC targets.
- Android 2.3.3 becomes the minimum platform version for any NFC-dependent app, fragmenting the install base between devices that carry the chip and the far larger fleet of pre-2.3 handsets that cannot run these apps.
Second-order effects
- Handset makers competing with the Nexus S face pressure to include NFC silicon in their next Android builds or cede the contactless use cases entirely, since OS-level support alone is useless without the radio.
- Retailers and venue operators holding Google Places stickers gain a second life for that infrastructure: every new NFC-capable Android phone turns existing tagged signage into an interaction point at no additional cost.
Third-order effects
- If NFC follows the pattern of prior Android capability additions, proximity-based interaction hardens into an expected smartphone radio rather than a flagship differentiator, with the OS vendor's API decisions — not chip availability — setting what developers can actually build on top of it.
The trend: Smartphone platforms are absorbing short-range radios into the base OS, converting physical objects with tags into programmable touchpoints at a pace set by each platform release cycle.