Near-Field Communication: Beyond Mobile Transactions
BARCELONA, Spain — Among the many buzz words — Androids, tablets, LTE — being tossed around the showroom floor here at the Mobile World Congress, there's one that I still haven't quite been able to wrap my head around.
Context & Ripple Effects
NFC arrives at Mobile World Congress with real platform backing behind it: Google shipped NFC read/write support and developer APIs in Android 2.3.3 just six days before the show opened, turning a payments curiosity into something app builders can code against. That timing is why the technology sits alongside LTE and tablets among the buzzwords of this year's Barcelona floor.
The framing matters too: analysts' 2011 mobile trend lists flagged contactless as one to watch, and the question at the congress is what NFC becomes once it stops being shorthand for tapping a phone at a register — transit, ticketing, tags, and identification are all on the table.
First-order effects
- Android developers gain an immediate new surface: Gingerbread's NFC APIs let any app read tags and initiate proximity interactions, so handset makers showing devices in Barcelona can demo non-payment uses rather than wait for wallet services.
Second-order effects
- Carriers and banks face a positioning problem: if the phone OS owns the NFC radio and APIs, payment networks and operators must negotiate their way onto the device instead of controlling the transaction stack themselves.
Third-order effects
- If NFC ships as standard handset hardware the way cameras did, the phone becomes a general-purpose credential — card, key, and ticket — pushing retailers, transit agencies, and building-security vendors toward a shared contactless infrastructure whose ownership is still unsettled.
The trend: Mobile platforms are absorbing short-range wireless as baseline hardware, shifting the fight over contactless services from whether the tech exists to who controls the secure layer on top of it.