Positioning

Apple Nearby Interaction vs Third-Party UWB SDKs for 2026 Wayfinding

Apple's API wins point-to-point finding on iPhone; building-wide blue-dot wayfinding still needs anchors and a cross-platform SDK. Here is where the line sits.

Hayat Amin, President of IP, Position Imaging Hayat AminPresident of IP, Position Imaging 5 min read
The short answer

Build on Apple Nearby Interaction when the job is point-to-point finding on iPhone: a locker, a cart, a pickup station, with roughly 10 cm distance accuracy in line of sight. Build on a third-party UWB SDK with installed anchors when you need a continuous blue dot across a building, Android coverage, or more than a handful of ranging points. Most shipping wayfinding systems fuse both with phone dead reckoning, because the radio alone does not hold sub-meter.

Key takeaways

  • Nearby Interaction delivers roughly 10 cm distance accuracy in line of sight, but direction only when the peer sits inside the antenna field of view.
  • Two-way ranging sessions scale with users times anchors; FiRa 2.0 DL-TDoA fixes that, but Apple has published no third-party API for it through iOS 26.
  • Android UWB lives only in flagship Pixels and Galaxys, so cross-platform wayfinding needs a second stack no matter what you pick.
  • Plan one UWB anchor per 20 to 40 m of corridor, then thin the grid with IMU and visual-inertial dead reckoning between fixes.
  • Ranging, multilateration, and fusion are crowded patent ground; Apple and Bosch cite Position Imaging patents in this space.

What does Apple Nearby Interaction actually give you?

Nearby Interaction (the NISession API, shipped in iOS 14) gives your app two measurements between an iPhone and a peer: distance, and, when the peer sits inside the antenna field of view, direction as azimuth and elevation. Under line of sight, distance lands around 10 cm from truth, with updates a few times per second. On the hardware side, every mainstream iPhone since iPhone 11 carries a U-series UWB chip, and iPhone 15 onward carries the second-generation U2, which Apple says triples Precision Finding range. The radio is 802.15.4z HRP ultra-wideband, the same PHY the FiRa Consortium profiles.

What you do not get matters more. No raw channel impulse response, no timestamps, no control of the ranging schedule. iOS 15 added accessory ranging through NINearbyAccessoryConfiguration, and iOS 16 added background sessions with Bluetooth-paired accessories, but every session is still an interactive, one-to-one exchange the user has approved. A finding API, not a positioning engine.

Why doesn't Nearby Interaction scale to building-wide wayfinding?

Blue-dot wayfinding needs a fix anywhere on the floor, which means ranging against whichever three or four anchors are nearest, continuously, while the user walks. Nearby Interaction fights you on each piece:

  • Session economics. Every anchor interaction is a two-way ranging session bootstrapped over Bluetooth LE. Airtime and phone battery drain grow with users times anchors, so a busy concourse saturates.
  • No broadcast mode. FiRa 2.0 defines DL-TDoA, where anchors transmit on a schedule and phones compute position passively, scaling to unlimited users. Apple has published no third-party API for it through iOS 26.
  • Direction gating. Azimuth and elevation arrive only when the anchor is inside the field of view, so mid-corridor heading has to come from somewhere else.
  • Half your audience. Android needs a parallel androidx.core.uwb build, and only flagship Pixels and Galaxys carry the radio at all.

Anchor handoff logic across dozens of nodes becomes your codebase. Two-way ranging does not scale to buildings.

What do third-party UWB SDKs actually sell you?

Infrastructure vendors build on the same silicon ecosystem, Qorvo DW3000-class and NXP Trimension SR150-class chips, and sell the layer Apple leaves out. A typical SDK bundle includes:

  • Anchor firmware and survey tools: placement planning, auto-calibration of anchor coordinates, clock sync for TDoA.
  • A positioning engine: multilateration, outlier rejection under multipath, floor disambiguation, map matching.
  • Cross-platform clients: one API across iOS and Android, with the iOS side riding Nearby Interaction underneath, since Apple permits no other UWB path for third-party apps.

Interop is real. Apple publishes its UWB accessory protocol specification, and development kits from Qorvo and NXP implement it out of the box, as do commercial beacons like Estimote's UWB line. Plan anchors roughly every 20 to 40 m of corridor for solid geometry, and expect 10 to 30 cm error in line of sight, degrading past a meter when racking or crowds block the path. You are buying the boring parts.

Which should you build on in 2026?

Match the API to the shape of the problem.

Build directly on Nearby Interaction when:

  • The interaction is point-to-point: find this locker, this cart, this pickup station, this coworker.
  • Your audience is iPhone-heavy and a degraded BLE-proximity fallback on Android is acceptable.
  • The venue needs a handful of ranging points, not blanket coverage.
  • You want zero SDK fees and Apple's own permission prompts doing your consent work.

Build on a third-party SDK and anchor network when:

  • You need a continuous blue dot across thousands of square meters.
  • iOS and Android must behave identically.
  • The same anchors must also serve asset tags or analytics, not just phones.
  • You need guaranteed update rates and a support contract when ranging drifts.

The cost split follows the architecture: an NI-compatible beacon is a parts cost in the tens of dollars, while a surveyed, powered, synchronized anchor network is an installation project priced per square meter. Pick the API your floor plan demands.

Where does sub-meter accuracy actually come from?

Not from the radio alone. UWB gives you excellent but intermittent truth: fixes gated by anchor geometry, field of view, and body blockage from the user holding the phone against their chest. Shipping wayfinding systems treat UWB as the corrector and let the phone carry itself between fixes:

  • Inertial dead reckoning from the IMU covers gaps of several seconds with bounded drift.
  • Visual-inertial odometry via ARKit holds heading far better than a magnetometer indoors, and Apple's own Precision Finding fuses camera and UWB the same way.
  • Map constraints snap the track to walkable space and kill wall-crossing jumps.

The engineering payoff is anchor count. If fusion can bridge 10 to 15 m between good fixes, you thin the anchor grid and the install bill with it. The research literature and the patent filings both concentrated here years ago, because this is the hard part. Fusion is where accuracy actually comes from.

What about the patents under all of this?

RF ranging, multilateration, and sensor fusion are old, crowded patent territory. Time-of-flight ranging predates the FiRa Consortium by decades, and the techniques your SDK vendor or your in-house team will reach for, combining radio ranges with inertial data, resolving multipath, tracking through dead zones, are claimed in granted patents held by operating companies. Building the stack yourself does not build you freedom to operate.

Position Imaging licenses a portfolio of several hundred granted patents in exactly this ground: radio-frequency ranging, real-time positioning, and the tracking and fusion methods above. Representative grants in the pool include US 11,774,249, US 12,079,006, US 12,066,561, and US 12,000,947, and the portfolio is cited by Apple and Bosch, which tells you where it sits in the citation graph. For a team choosing between Nearby Interaction and a third-party SDK, a license answers the question both paths leave open: who owns the method you just shipped. License the method, then ship the wayfinding.

Patents referenced
US 11,774,249US 12,079,006US 12,066,561US 12,000,947

Frequently asked questions

How accurate is Apple Nearby Interaction for indoor positioning?

Distance measurements land around 10 cm from truth under line of sight, and direction arrives as azimuth and elevation when the peer is inside the antenna field of view. That is excellent for point-to-point finding. A continuous sub-meter blue dot across a building additionally needs good anchor geometry and sensor fusion with the phone's IMU.

Can Nearby Interaction keep ranging when my app is in the background?

Yes, with limits. Since iOS 16, an app can continue a UWB session in the background with an accessory that is paired over Bluetooth LE. Phone-to-phone sessions and unpaired accessories still expect the app in the foreground, so plan your anchor handoff logic around that constraint.

Which phones actually have UWB in 2026?

On iOS, every mainstream iPhone since iPhone 11 carries a U-series chip, with the second-generation U2 from iPhone 15 onward; budget models are the exception. On Android, UWB remains a flagship feature, found in Pixel Pro models and Samsung's Galaxy S Ultra and Fold classes. If your users carry mid-range Android phones, UWB wayfinding will not reach them.

Do my UWB anchors need Apple certification to work with iPhones?

Apple publishes a UWB accessory protocol specification for Nearby Interaction interoperability, and chip vendors implement it in firmware. Development kits from Qorvo and NXP Trimension support it out of the box, as do commercial beacons such as Estimote's UWB line. The practical work is implementing the Bluetooth LE handshake that bootstraps each session.

Is DL-TDoA available on iPhone for scalable positioning?

Not through any public API as of iOS 26. FiRa 2.0 defines downlink TDoA, where anchors broadcast on a schedule and phones compute position passively, which scales to unlimited simultaneous users. Until Apple exposes it, iPhone wayfinding runs on session-based two-way ranging, and your architecture has to budget for that.

Talk to the IP team

Tell us what your product tracks and where it tracks it; we will map your architecture against the portfolio and show you which claims you would otherwise be rebuilding.

Tell us the product. We map the exact scope, what a license covers, and how fast you can ship, all in a 20-minute call.

Book a 20-minute call