iOS 26 UWB APIs: What Warehouse Tag Builders Should Ship Now
Apple's accessory APIs turn every iPhone on the floor into a 10 to 30 cm finder. What warehouse tracking builders should ship before the next device refresh.
Hayat AminPresident of IP, Position Imaging
4 min read
Ship a FiRa 2.0 certified tag that also implements Apple's Nearby Interaction accessory protocol. iOS 26 makes the full accessory stack, background ranging included, the baseline on every current iPhone, so each phone on your floor doubles as a 10 to 30 cm handheld finder. Keep fixed anchors for continuous tracking and use phones for search, commissioning, and audits. Dual-stack firmware on NXP Trimension or Qorvo DW3000 silicon covers both protocols on one radio today.
Key takeaways
- iOS 26 makes the full UWB accessory stack the baseline: assume background ranging and second-generation chip range on every handheld your customer issues.
- iPhones replace dedicated finders, not fixed anchors. Continuous tracking still needs an anchor grid, commonly every 15 to 30 meters.
- Background ranging, supported since iOS 16, lets a locked phone in a pocket find a tote. Design tag power around BLE wake-up, not fixed ranging schedules.
- FiRa 2.0 profiles and Apple's accessory protocol fit on one 802.15.4z radio. NXP Trimension and Qorvo DW3000 silicon support both stacks.
- The ranging silicon is commodity. The positioning math through steel racking and multipath is where the granted patents concentrate.
What does iOS 26 actually change for third-party UWB tags?
Apple opened Nearby Interaction to third-party accessories in iOS 15 back in 2021, then added background ranging for Bluetooth-paired accessories in iOS 16. iPhone 15 brought the second-generation UWB chip in 2023, which Apple says reaches three times the range of the first generation. iOS 26, shipped in September 2025, matters less for any single new call and more for what you can now assume: the whole accessory stack is the floor, not the ceiling. Every flagship iPhone since the iPhone 11 in 2019 carries UWB hardware, and enterprise device refreshes in 2026 mean the handhelds your customer issues to pickers are iPhone 15 class or newer. That changes the build decision. In 2022, a tag that spoke Apple's accessory protocol reached a sliver of devices through a foreground-only app. In 2026, the same firmware investment reaches effectively the whole installed base, with ranging that keeps running while the picker's phone sits in a pocket. The radio question is settled, the hardware is deployed, and the API surface has been stable across multiple releases. The bottleneck is now your tag, not Apple.
Can an iPhone replace fixed UWB anchors on the floor?
No, and planning as if it can will sink the deployment. Continuous real-time location needs anchors at known positions with enough geometry to solve for a tag, which in practice means a fixed grid, commonly one anchor every 15 to 30 meters in open racking and tighter around steel mezzanines where multipath gets ugly. A phone is a moving point at an unknown position. What the iPhone does replace is the dedicated handheld finder. Nearby Interaction returns distance from time-of-flight ranging at 10 to 30 cm, and with camera assistance it adds direction, so a picker gets steered to a specific tote rather than a 3 meter zone. That covers the three jobs fixed infrastructure handles worst:
- Last-ten-meters search when the system says aisle 14 and the tote is buried
- Commissioning and ground-truth checks during install, no laser rig required
- Cycle-count audits in zones that never justified anchor coverage
Phones find; anchors track.
Design the tag around background ranging, not the demo
The demo everyone builds is a foreground app with an arrow. The feature that survives contact with a warehouse is background ranging, supported since iOS 16 for accessories paired over Bluetooth LE. The flow: the tag advertises over BLE, the phone pairs once, and from then on the app can run a UWB session that keeps ranging while the phone is locked in a pocket, firing a haptic when the picker is within arm's reach of the right asset. Design consequences worth stating plainly:
- The tag needs a real BLE stack alongside the UWB radio. Budget for it in the BOM.
- UWB ranging bursts dominate the power draw. A tag that ranges on BLE wake-up instead of a fixed schedule stretches a coin cell from weeks to a year or more.
- Users grant Nearby Interaction permission per app, so request it during first-launch setup, not mid-shift.
Apple documents the accessory protocol, and sample firmware from NXP and Qorvo implements it, so integration is a firmware project measured in weeks, not a research effort. Build for the pocket, not the demo.
Does FiRa 2.0 let one tag serve iPhones and fixed readers?
Yes, and this is the cleanest change since 2023. Apple's implementation and the FiRa profiles both ride on IEEE 802.15.4z HRP, typically channel 9 near 8 GHz, so the physical radio in a certified tag already speaks to both worlds. FiRa 2.0 added a certification program that tests interoperability between vendors rather than conformance on paper, and Apple joined the FiRa Consortium in 2022. In practice, a dual-stack tag runs FiRa ranging sessions against fixed anchors for continuous tracking and answers Apple's Nearby Interaction accessory protocol when an iPhone initiates a session. Off-the-shelf silicon covers this: NXP's Trimension line and Qorvo's DW3000 family ship with both Apple interoperability and FiRa support, so you are configuring stacks, not porting PHYs. The procurement angle matters as much as the engineering one. A warehouse operator burned by proprietary RTLS lock-in will put FiRa certification in the RFP, and "works with the iPhones you already issue" is the line that shortens a pilot from quarters to weeks. One radio, two protocols, zero forked SKUs.
What should warehouse tracking builders ship in the next two quarters?
The ship list, in order:
- A FiRa 2.0 certified tag with Apple's accessory protocol in firmware, on Trimension or DW3000 silicon
- An iOS app with background ranging and haptic find, tested on iPhone 15 and later where the second-generation chip delivers the extra range
- Fixed-anchor coverage priced per zone rather than per building, with phones covering the audit zones
- A BLE wake-up power scheme targeting a year on a coin cell
None of that is the hard part. The hard part is the positioning math underneath: solving location through steel racking, rejecting multipath, fusing UWB ranges with camera and inertial data, and doing it fast enough to matter. That layer is where granted patents concentrate, and it is where a well-funded competitor or an NPE looks first once you have revenue. Position Imaging licenses hundreds of granted US patents in RF ranging, real-time positioning, and sensor fusion, a portfolio cited by Apple, Bosch, and other major firms, with coverage including US 11,774,249, US 12,079,006, US 12,066,561, and US 12,000,947. Licensing proven IP means shipping in months with freedom to operate instead of re-deriving a decade of ranging work. Ship the tag; license the math.
Frequently asked questions
Do third-party UWB tags work with iPhone without joining Apple's Find My network?
Yes. The Nearby Interaction accessory protocol works with your own iOS app and needs no Find My enrollment. Find My is a separate accessory program with its own specification, worth pursuing only if consumer-style lost-item finding matters to your product. For warehouse workflows, your own app with background ranging is the right path.
What accuracy does an iPhone get when ranging a UWB tag?
Expect 10 to 30 cm from time-of-flight ranging with line of sight, plus direction when camera assistance is enabled. Behind dense metal racking, accuracy degrades and sessions can drop, so treat non-line-of-sight readings as zone-level hints rather than precise fixes. Design the find flow to recover gracefully when the picker turns a corner.
Do I still need fixed UWB anchors if every worker carries an iPhone?
Yes, for anything continuous. A phone has no known position and cannot provide the geometry a location solver needs, so dashboards, flow analytics, and alerts still require an anchor grid. Phones handle the last ten meters of search, commissioning, and audits, which lets you thin anchor density in low-value zones and cut install cost.
Is FiRa 2.0 certification worth the cost for a warehouse tag?
Yes. FiRa 2.0 certification tests actual cross-vendor interoperability, not just spec conformance, and warehouse operators who have been burned by proprietary RTLS increasingly require it in RFPs. Since the same 802.15.4z radio also serves Apple's protocol, certification adds procurement credibility without adding a second SKU.
What about Android handhelds in mixed device fleets?
Android exposes UWB through the androidx.core.uwb Jetpack library on supporting hardware, including recent Pixel and Samsung flagships, and it ranges against FiRa-profile tags. A FiRa 2.0 certified tag therefore covers Android devices as well as fixed readers, which is another reason to certify instead of shipping Apple-only firmware.
Map your tag, anchor, and fusion stack against the Position Imaging portfolio before you ship, and know exactly which claims you are building on.
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