Build a UWB Asset Tracker That Works With 2026 iPhones
A builder's guide to Apple's precision finding stack: which API path to take, which chipsets interoperate, and where the hard limits sit.
Apple's second-generation UWB chip, standard in every flagship iPhone and Apple Watch since September 2023, means your customers already carry a precision finding reader. To build a tag that works with 2026 iPhones, use an 802.15.4z chipset such as Qorvo DW3xxx or NXP Trimension and integrate the Nearby Interaction API, which streams live distance and direction into your own app. The Find My network adds worldwide locating but gives your backend nothing. For asset tracking, Nearby Interaction is the path.
Key takeaways
- Every non-SE iPhone since late 2019 ships with UWB, and the second-generation chip has been standard since the iPhone 15 in September 2023.
- Nearby Interaction, not Find My, is the asset tracking path: it streams distance and direction into your own app and backend.
- Interoperability means an 802.15.4z HRP radio; Qorvo DW3xxx and NXP Trimension parts already range against Apple silicon.
- Every Nearby Interaction session bootstraps over Bluetooth LE, so your tag needs a BLE SoC beside the UWB radio.
- Background ranging has existed since iOS 16 but requires Bluetooth pairing and suits brief handoffs, not continuous logging.
- One iPhone is one mobile anchor; warehouse-scale coverage still needs fixed infrastructure and a fusion layer you build or license.
What does Apple's second-generation UWB chip change for tag makers?
Apple shipped its first UWB chip, the U1, in the iPhone 11 in September 2019. The second-generation chip arrived in September 2023 in the iPhone 15 lineup, Apple Watch Series 9, and Watch Ultra 2, and Apple states it connects two second-gen devices at up to 3x the distance of the original, the capability behind pinpointing a misplaced iPhone from a Watch. Every flagship iPhone and Watch since has carried the newer silicon, so by 2026 it spans multiple device generations, while every non-SE iPhone sold since late 2019 has some form of UWB aboard.
For a tracker startup, the installed base matters more than the chip. Your customers already hold the reader. A tag built to Apple's interoperability spec ranges against hundreds of millions of handsets with no hardware you deploy on the phone side. Your tag's own radio and antenna set the link budget, and 802.15.4z parts commonly hold a ranging session across tens of meters line of sight. The reader network already shipped.
Nearby Interaction or Find My network: which path fits asset tracking?
Apple offers two doors, and they lead to different products. Nearby Interaction shipped in iOS 14, added third-party accessory support in iOS 15 via NINearbyAccessoryConfiguration, and gained background sessions plus camera-assisted direction in iOS 16. It streams distance and a direction vector to your own app several times per second, which is exactly what an asset tracking product needs: your UI, your backend, your telemetry. The framework has also been on Apple Watch since watchOS 8, which puts a ranging-capable device on a picker's or a nurse's wrist.
The Find My network is the other door. It locates a tag worldwide by crowdsourcing BLE sightings from Apple devices, but the position surfaces only in the owner's Find My app. There is no server API, so your dashboard never sees the data, and UWB Precision Finding inside Find My has historically been reserved for Apple's own tags. Use Find My for consumer lost-item recovery and Nearby Interaction for operations. Find My finds; Nearby Interaction measures.
What hardware makes a tag interoperable with iPhone precision finding?
Interoperating with Apple's chip means implementing IEEE 802.15.4z HRP UWB, with channel 9 near 8 GHz as the band that matters in practice. Off-the-shelf silicon already does this: Qorvo's DW3xxx family lists interoperability with Apple's UWB chips, and NXP's Trimension line covers the same ground with tag-oriented parts. Modules from Qorvo and Murata fold in the antenna and RF matching, which removes the hardest board-level work for a seed-stage team.
Two design facts drive the rest of the BOM:
- Every Nearby Interaction session bootstraps over Bluetooth LE. The phone and accessory exchange UWB configuration data over BLE before a single ranging pulse flies, so your tag needs a BLE SoC such as a Nordic nRF52 beside the UWB radio.
- UWB ranging bursts draw tens of milliamps, so battery life is a duty-cycling problem. Range on demand, sleep otherwise, and let BLE carry the idle presence beacon.
At volume, the UWB radio and antenna add single-digit dollars over a BLE-only tag. Buy the module; spend firmware effort on power.
What Apple's UWB APIs still do not give you
The APIs are productized, which also means curated. iOS never exposes raw channel impulse response data, so you cannot run your own multipath rejection on the phone side; you take Apple's distance estimate as delivered. Background sessions require the accessory to be Bluetooth paired and are designed for brief interactions, not for logging a tag's position across a full shift. Direction output can require camera assistance on some hardware, which works for a find-my-pallet moment and fails for a phone in a pocket.
The structural limit is bigger than any single API gap: one iPhone is one mobile anchor. There is no mode for multilateration across several phones, no fixed-anchor configuration, and no way to track two hundred tags at sub-second rates through a handset. Continuous coverage of a warehouse or a hospital floor still demands fixed UWB anchors, camera-based tracking, or a hybrid of both, plus the fusion layer that joins phone ranging to that infrastructure. Plan the product around that split from day one. One iPhone is an anchor, not a network.
How do you ship a 2026 tracker without rebuilding ranging IP?
The phone side of this stack cost you nothing. Apple built the chip, the OS support, and an installed base measured in hundreds of millions of devices. What remains is still substantial: tag firmware, NLOS detection, duty-cycle power design, the fixed-anchor layer for continuous coverage, the fusion code that merges UWB ranges with inertial or camera data, and freedom to operate in a field where radio-frequency ranging patents reach back two decades. It is common for teams to spend a year or more rediscovering problems that were solved and filed long before their seed round.
That gap is what Position Imaging fills. We license hundreds of granted patents across radio-frequency ranging, real-time positioning, computer vision, and machine learning, IP that firms including Apple and Bosch cite in their own filings. A startup building an iPhone-compatible tracker can map its architecture against the portfolio, license what applies, and put its engineering months into the product instead of into prior art it did not know existed. License the ranging stack, build the product.
Frequently asked questions
Does my UWB tag need MFi certification to work with iPhone precision finding?
It depends on the path. The Find My network requires joining Apple's accessory program, with its certification and branding rules. The Nearby Interaction accessory path instead requires implementing Apple's published UWB accessory protocol and meeting its interoperability requirements, with your own app providing the user experience. Most asset tracking startups take the Nearby Interaction path because it feeds their own backend.
Can my app range with a tag while running in the background?
Yes, within limits. iOS 16 added background Nearby Interaction sessions, but the accessory must be connected as a Bluetooth paired device and the mode is built for short interactions, like guiding a user to equipment as they approach. It is not a substitute for continuous position logging, which still needs fixed infrastructure.
What accuracy can I expect from iPhone UWB ranging?
Under line of sight, 802.15.4z two-way ranging delivers distance in the 10 cm class, and Nearby Interaction adds a direction vector, with camera assistance improving it on supported hardware. Multipath, body blocking, and metal racking degrade both, so production firmware needs outlier rejection rather than trust in any single measurement.
Will the same tag work with Android phones?
It can. Android exposes UWB through the androidx.core.uwb Jetpack library on supported devices, and both ecosystems build on 802.15.4z, with FiRa profiles covering the Android side. Design the radio to the standard and keep separate session bootstrap logic per platform, and one tag SKU can serve both.
Can I pull Find My network locations into my own dashboard?
No. Find My location data is end-to-end encrypted and surfaces only in the owner's Find My app; Apple provides no server API for third parties to read it. That is the core reason fleet and facility asset tracking products build on Nearby Interaction plus their own infrastructure instead.
Send us your tracker's block diagram and we will map it against the portfolio, so you know what to license before you write the firmware.
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