Nearby Interaction UWB Tags in 2026: What Apple Lets You Build
A capability map for third-party tag makers: what Apple's UWB APIs actually support, where the hard walls are, and why FiRa certification alone won't get you there.
In 2026, Apple's Nearby Interaction framework lets a third-party UWB tag range with an iPhone: distance at roughly 10 cm fidelity in line of sight, a direction vector while the tag is in the antenna's field of view, and background ranging for Bluetooth-paired accessories. It does not give you raw channel data, iPhones as fixed anchors, or iPhone compatibility from FiRa certification alone. You must implement Apple's own accessory protocol, and your app must be installed and granted permission.
Key takeaways
- Since iOS 15, a tag implementing Apple's Nearby Interaction accessory protocol can range with every UWB iPhone from iPhone 11 forward.
- You get distance, a direction vector inside the antenna's field of view, and background sessions for Bluetooth-paired accessories. Nothing lower level.
- FiRa certification covers FiRa profiles, not Apple's. An interoperable tag ships two profiles on one 802.15.4z radio: FiRa for Android, Apple's for iOS.
- iPhones cannot act as fixed anchors or TDoA listeners, so phone-only infrastructure tracking is off the table.
- Phone-side behavior is Apple's to change. Durable differentiation lives in tag firmware, anchor networks, and fusion algorithms, which is where patent exposure concentrates.
What can a third-party UWB tag actually do with an iPhone in 2026?
Since iOS 15 shipped accessory support in 2021, a tag that implements Apple's Nearby Interaction accessory protocol can run a two-way ranging session with any UWB iPhone, from the iPhone 11's U1 chip through the second-generation chip introduced with iPhone 15. The session hands your app three things: distance in meters at roughly 10 cm fidelity in line of sight, direction as a 3D vector whenever the tag sits inside the phone antenna array's field of view, and a session lifecycle your firmware negotiates over a Bluetooth LE side channel before UWB ever fires. iOS 16 added the two features tag makers lean on most: camera assistance, which fuses ARKit motion data so the direction estimate holds steady while a user sweeps the phone around, and background sessions for Bluetooth-paired accessories, which keep ranging alive after the user switches apps. That supports point-to-find item tags, walk-up door access, and distance-based triggers inside your own app. That is the entire phone-side menu.
What hardware does your tag need to range with an iPhone?
The tag needs an 802.15.4z HRP UWB radio that supports Apple's accessory protocol, plus a BLE radio for the configuration handshake. In practice that means silicon with vendor support for the Apple profile already in the SDK:
- Qorvo DW3xxx family (DW3110, DW3120, DW3220), with Apple Nearby Interaction support in Qorvo's stack and the DWM3001 modules for prototyping
- NXP Trimension parts such as the SR040 and SR150, which NXP ships with Apple-interoperable firmware
The flow is fixed: your accessory advertises over BLE, the iPhone app opens a session and passes Apple's shareable configuration data across the GATT link, the tag's UWB stack parses it, and both sides start scheduled two-way ranging on a 500 MHz HRP channel. Apple publishes the Nearby Interaction accessory protocol specification to developers, so plain UWB ranging does not require a separate certification program, though joining the Find My network is a different Apple program with its own spec and approval. No interoperable silicon, no session.
What Apple still does not let tag makers build
The walls matter more than the features, because teams keep designing products that assume they are not there.
- No raw radio access. You get distance and direction, not channel impulse responses, timestamps, or PHY settings. Custom ranging algorithms on the phone side are impossible.
- No iPhone as infrastructure. An iPhone cannot act as a fixed anchor, broadcast ranging beacons, or listen to time-difference-of-arrival traffic. If your architecture needs anchors, you are buying or building dedicated hardware.
- No ranging with strangers' phones. Your app must be installed, the user must grant the Nearby Interactions permission, and the session is mutual. There is no passive discovery of arbitrary iPhones.
- Background only with pairing. Backgrounded ranging requires the accessory to be Bluetooth-paired to the phone, which adds pairing UX your product has to carry.
- No Precision Finding UI. The AirTag arrow experience stays private to Apple. Your app renders its own guidance from the vectors it receives.
The phone side is rented, never owned.
Does FiRa certification get you iPhone interoperability in 2026?
No, and this still surprises hardware teams. The FiRa Consortium certifies devices against FiRa-defined profiles, including the downlink TDoA mode added in FiRa 2.0 that lets a tag position itself by listening to synchronized anchors. Apple joined the consortium in 2022, and Apple's chips speak the same IEEE 802.15.4z HRP physical layer that FiRa builds on. But Nearby Interaction runs Apple's own accessory protocol on top of that PHY, and passing FiRa certification says nothing about implementing it.
A FiRa-certified tag and an iPhone share a radio standard the way two people share an alphabet. They still are not speaking the same language.
The practical consequence for a 2026 tag program: one UWB chip, two firmware profiles. FiRa-style sessions cover Android, where the platform UWB APIs align with FiRa work, and Apple's profile covers iOS. Budget engineering and test time for both from day one, because retrofitting the second profile after launch is where schedules slip. Certification badges do not open Apple's door.
How accurate is iPhone UWB ranging against a tag, really?
Plan around three regimes, not one spec-sheet number. In clear line of sight at a few meters, distance readings land in the 10 cm class, which is why point-to-find interactions feel instant. Direction is the fragile part: the vector only exists while the tag is inside the phone's antenna field of view, so a tag behind the user or beside the phone yields distance with no bearing, and your UI needs a graceful distance-only mode. Obstruction is the third regime. UWB at these frequencies does not punch through a human body well, so a phone in a back pocket or a hand wrapped over the antenna degrades range and injects multipath error that no amount of app-side smoothing fully removes. Apple's second-generation chip, shipping since iPhone 15 in 2023, extended usable range, with Apple claiming roughly three times the reach for its own finding features, but it did not repeal physics indoors. Prototype in a cluttered stockroom, not a conference room. Design for the bad days, not the demo.
Where licensed positioning IP fits when Apple owns the phone side
Everything on the iPhone side of the session is Apple's, which means your durable product value sits in what surrounds it: tag firmware that runs both radio profiles on one battery budget, fixed anchor networks for the aisles and rooms a phone never visits, and the fusion layer that turns raw ranges into tracks a warehouse or hospital can act on. That surrounding layer is exactly where RF ranging and positioning patents concentrate, and where a shipping product picks up infringement exposure it never sees coming during the prototype phase. Position Imaging licenses a portfolio of granted US patents in radio-frequency ranging, computer vision, and machine-learning-based tracking, including US 11,774,249 and US 12,000,947, with prior citations from Apple and Bosch among others. For a tag maker, licensing the solved positioning layer means your engineers spend their quarters on the accessory protocol work only you can do, and you carry freedom to operate on the rest. License the solved parts, build the rest.
Frequently asked questions
Can a third-party UWB accessory range with an iPhone in the background?
Yes, since iOS 16, but only if the accessory is Bluetooth-paired to the phone. A paired accessory can keep its Nearby Interaction session running while the app is backgrounded, which is what makes hands-free door access products workable. Without pairing, the session stops when the user leaves your app.
Do I need an Apple certification program to build a Nearby Interaction tag?
Apple publishes the Nearby Interaction accessory protocol specification to developers, so basic UWB ranging with your own app does not require a separate approval program. Joining the Find My network is different: that runs under Apple's Find My accessory program with its own specification and review.
Is a FiRa-certified UWB tag automatically compatible with iPhones?
No. FiRa certification validates FiRa profiles, while iPhones use Apple's own Nearby Interaction accessory protocol on the shared 802.15.4z physical layer. An interoperable tag implements both: FiRa-aligned sessions for Android devices and Apple's profile for iOS.
How accurate is UWB ranging between an iPhone and a tag?
Expect distance in the 10 cm class at a few meters with clear line of sight, with accuracy degrading when a body or shelving blocks the path. Direction is only reported while the tag is within the phone antenna's field of view, so products need a distance-only fallback mode.
Can I use iPhones as fixed anchors for an indoor positioning system?
No. Nearby Interaction only supports mutual two-way ranging sessions between a phone and a peer or accessory. An iPhone cannot broadcast as a fixed anchor or listen for TDoA traffic, so infrastructure-based tracking requires dedicated anchor hardware.
Building a UWB tag for 2026? Send us your architecture and we will map it against the portfolio before you commit silicon.
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