Bluetooth Low Energy

BLE vs NFC vs UWB

They are three short-range radios built for different jobs. Bluetooth LE lets devices find each other and exchange data without touching; NFC exchanges small payloads when two devices are held within about 4 cm, as in tap-to-pay; and UWB measures distance, and on some devices direction, precisely. UWB usually relies on another channel, often BLE, to find the other device and set up the session.

TL;DR

Pick the radio by the job. BLE is for discovery and ongoing data exchange, NFC for a deliberate tap where intent matters more than reach, and UWB for precise distance and direction, with its session set up over BLE or another channel. For messages between phones, BLE is the one built for ongoing two-way data.

Learning objectives

After reading this article you will be able to:

  • Distinguish the jobs Bluetooth LE, NFC and UWB were each designed for
  • Explain why UWB ranging relies on Bluetooth LE or another channel for setup
  • Choose between BLE, NFC and UWB for discovery, deliberate taps or precise ranging

BLE, NFC and UWB design goals

BLE, NFC and UWB were each designed around a different question, even though phones carry several short-range radios and it is easy to treat them as interchangeable:

  • Bluetooth LE: who is nearby, and can we exchange some data?
  • NFC (Near Field Communication): did the user deliberately bring these two things together?
  • UWB (ultra-wideband): exactly how far away is that device, and in which direction?

They also combine. Android’s UWB guide, for example, has apps find the other device with a BLE scan before UWB ranging can start.

Bluetooth LE discovery and data exchange

Bluetooth Low Energy devices find each other by advertising and scanning, then connect and exchange data through GATT. BLE runs in the 2.4 GHz ISM band. The Bluetooth SIG lists 40 channels, three of them for advertising, and topologies from point-to-point to broadcast and mesh.

Range is not a single number. The Bluetooth SIG puts the effective range anywhere from more than a kilometre down to less than a metre, depending on the PHY, transmit power, receiver sensitivity and antenna. Either way, the devices do not need to touch.

BLE can also locate things. The SIG lists advertising for presence, direction finding for direction, and RSSI and Channel Sounding for distance. Simple beacons use only the first.

NFC for deliberate taps

NFC is built to work only at very short range, so a connection happens because someone chose to hold a phone to a reader, a tag or another phone. Android’s documentation describes it as a set of short-range wireless technologies, typically requiring a distance of 4 cm or less to initiate a connection. That short range is the point.

Android phones with NFC support two main modes. In reader/writer mode the phone reads and writes passive tags and stickers. In card emulation mode the phone acts as an NFC card that an external reader, such as a payment terminal, can talk to. Much of Android’s NFC API is built around NDEF (NFC Data Exchange Format), a standard from the NFC Forum, the industry body that publishes the NFC specifications.

NFC carries small payloads. The NFC Forum’s own examples are paying, riding the train, opening a locked door and pairing devices: single deliberate actions, not a running conversation.

UWB precise ranging

Ultra-wideband is used for precise ranging. Android describes it as a radio technology focused on precise ranging, measuring location to an accuracy of 10 cm. It spreads its signal across a very wide slice of spectrum, and Android defines it by bandwidth greater than 500 MHz, or more than 20% fractional bandwidth. The FiRa Consortium writes UWB specifications and certifies devices so that they work together.

On Android, one device acts as the controller (initiator) and the other as the controlee (responder). Before ranging can start, the two must find each other and exchange parameters such as addresses, channel and session key. Android leaves that to the app, through a secure out-of-band channel of its choice, and gives Bluetooth LE as the example: discover the peer with a BLE scan, then exchange the parameters over GATT.

Apple’s Nearby Interaction framework works the same way in outline. Apps on devices with a UWB chip share discovery tokens, then iOS reports a peer’s distance and direction while the app is in the foreground; on watchOS it reports distance only. In the background, ranging continues only if the peer is paired and connected over Bluetooth LE, or, from iOS 18.4, if the app starts a Live Activity.

BLE vs NFC vs UWB comparison

BLE’s main job is discovery and data exchange, NFC’s is the deliberate tap, and UWB’s is precise distance and direction.

Bluetooth LENFCUWB
Main jobDiscovery and data exchangeDeliberate tap: pay, tag, pairPrecise distance and direction
Distance figure in the docsRange from less than a metre to more than a kilometre, by design and setting (SIG)Connects at typically 4 cm or less (Android)Ranging accuracy of 10 cm (Android)
Finds the other device itselfYes, by advertising and scanningYes, by being brought into contactNo, apps exchange setup over another channel
Ongoing two-way data between appsYes, through GATTSmall payloads per tapPhone APIs report ranging results

BLE, NFC or UWB by use case

Use BLE when devices need to discover each other and keep exchanging data, such as a phone and a sensor, or two phones. Use NFC when the user’s intent matters more than reach: a tap that proves the phone was right there. Use UWB when the question is exactly where something is, and plan on BLE or another channel to set the session up.

For an app that has to carry messages between phones, BLE is the one of the three built for discovery and ongoing two-way data. NFC needs the phones held together and carries small payloads, and UWB on both platforms is documented as a ranging tool.

Frequently asked questions

Can two phones send messages to each other over NFC?

Only briefly, and only while they are held together. Android describes NFC as sharing small payloads between a tag and a phone or between two Android phones, typically within 4 cm. For an ongoing exchange, phones use Bluetooth LE or a network.

Does UWB replace Bluetooth?

No. On both Android and Apple devices, UWB is documented for ranging, and the devices first need to find each other and swap session details over another channel. Android's guide names Bluetooth LE as an example of that channel.

How close do two devices need to be for NFC to work?

Android's documentation says NFC typically needs a distance of 4 cm or less to initiate a connection. That short range is the point, since a connection then happens because someone chose to hold the phone to a reader, a tag or another phone.

How accurate is UWB ranging on a phone?

Android describes UWB as a radio technology focused on precise ranging, measuring location to an accuracy of 10 cm. Apple's Nearby Interaction reports a peer's distance and direction on iOS while the app is in the foreground, and distance only on watchOS.

What is the range of Bluetooth LE?

There is no single number. The Bluetooth SIG puts the effective range anywhere from more than a kilometre down to less than a metre, depending on the PHY, transmit power, receiver sensitivity and antenna.

Does UWB ranging keep working when an iPhone app is in the background?

Only in some cases. Apple says background ranging continues if the peer is paired and connected over Bluetooth LE, or, from iOS 18.4, if the app starts a Live Activity.

Sources

Build it with Offline Protocol

The platforms page lists the transports each Offline Protocol SDK surface supports, with Bluetooth LE as the phone-to-phone path in React Native on iOS and Android.

Read the platforms and transports page