Apple Nearby Interaction vs Android Channel Sounding for Asset Tags

What are you actually choosing between?

Apple Nearby Interaction is a single-radio API. It has shipped in iOS since iOS 14 in 2020, it speaks only UWB over the 802.15.4z high rate pulse format, and since iOS 15 it ranges to third-party accessories through NINearbyAccessoryConfiguration. Android took the opposite route. The androidx.core.uwb Jetpack library (Android 12 and later) handles FiRa-style UWB sessions, and Android 16 added a generic android.ranging API that brokers three radios behind one interface: UWB, Bluetooth Channel Sounding from the Bluetooth 6.0 core spec, and Wi-Fi RTT. So the real question is not Apple versus Android. It is a UWB-only stack with a six-year installed base versus a multi-radio broker where Channel Sounding trades accuracy for reach. Your tag firmware, your anchor plan, and your find-it UX all follow from that split. One API ranges, the other brokers radios.

Which phones can actually range to your tag in 2026?

• iPhone: every flagship iPhone since the iPhone 11 in 2019 carries a UWB chip (the SE line is the exception), and the second-generation chip in the iPhone 15 and later extends Precision Finding range, with Apple claiming roughly 3x over the original U1. That is six-plus years of devices that can range to your tag at 10 to 30 cm out of the box.
• Android UWB: still a flagship feature. Pixel Pro models since the 6 Pro, Samsung Ultra models since the Galaxy Note20 Ultra, and a short list of others.
• Android Channel Sounding: needs Android 16 plus a Bluetooth chipset that implements the 6.0 feature, so phone-side support is only now rolling through 2025 and 2026 flagships.

The bet on Channel Sounding is that it reaches mid-tier phones faster than UWB did, because it rides the Bluetooth radio every phone already has instead of a second chip. That bet has not paid out yet. Count phones before you pick a radio.

Does Bluetooth 6.0 Channel Sounding accuracy match UWB?

No. UWB under 802.15.4z uses 499.2 MHz wide channels at 6.5 or 8 GHz, which gives roughly 2 nanosecond time resolution and lets the receiver pick the first-arriving path out of a cloud of reflections. In practice that lands at 10 to 30 cm, and the iPhone adds angle of arrival, which is what drives the arrow in a Precision Finding UX. Channel Sounding works with what the 2.4 GHz ISM band allows: phase-based ranging plus round-trip time hopped across up to 72 channels, about 80 MHz of total span. Vendors quote 10 to 30 cm in open lab conditions; plan on 0.5 to 1 meter indoors and worse in metal-racked aisles where multipath smears the phase measurements. Channel Sounding also returns distance only, no direction, so the UX is hotter-colder rather than point-and-walk. For room and zone-level presence that is fine. For which-bin-on-the-shelf it is not. Bandwidth decides accuracy before your firmware does.

Can one tag serve both stacks? The FiRa and Apple answer

Yes, with the right silicon. Apple ranges to accessories through its own published Nearby Interaction accessory specification, not through FiRa profiles, while androidx.core.uwb expects FiRa-conformant sessions. The practical fix is dual-profile UWB chips: Qorvo's DW3xxx line and NXP's Trimension SR150 class parts run the Apple accessory protocol and FiRa profiles from the same radio, so one tag SKU ranges to both ecosystems. Three details decide whether the integration goes well:

• Out-of-band setup. Both stacks configure the UWB session over Bluetooth LE first, so your tag carries a BLE radio regardless. That same radio is your Channel Sounding upgrade path on new silicon like Nordic's nRF54 series or NXP's KW47.
• Background behavior. Nearby Interaction sessions start in the foreground; since iOS 16 they can continue in the background while the accessory holds a Bluetooth LE connection. Design the reconnect logic early.
• Certification. FiRa 2.0 certification is what keeps Android interop from turning into per-phone QA.

One tag, two protocols, both certified.

So which stack should your asset-tracking app target in 2026?

Sequence it instead of choosing.

• If the core UX is find-this-item at arm's reach (totes, carts, returns, tools), build the UWB tag first and target Nearby Interaction plus androidx.core.uwb together. Same 802.15.4z radio, two session layers, sub-30 cm on both platforms.
• If your buyers run mixed Android fleets and meter-level presence answers the business question (is the pump in this room, did the cart leave the dock), add Channel Sounding through android.ranging. On a dual-radio tag it is largely a firmware project, since the BLE radio is already on the board for session setup.
• Do not build an Android-CS-only product this year. You would ship into a phone base that mostly cannot range yet and lock out every iPhone, because Apple exposes no public Channel Sounding API.

The tag hardware supports this sequencing: BLE-class parts with Channel Sounding cost what BLE parts always cost, and the UWB front end is the increment you pay for a 10x accuracy step. Ship UWB now and add Channel Sounding later.

Where does licensed positioning IP fit in this build?

The phone APIs are free. What they do not give you is everything between a raw range and a product: rejecting non-line-of-sight measurements in a racked warehouse, fusing phone ranges with fixed anchors, scheduling hundreds of tags without session collisions, and holding freedom to operate while you do it. That layer is where teams burn quarters, and it is where the patent exposure sits, because radio-frequency ranging and real-time positioning carry two decades of granted prior art. Position Imaging licenses that layer directly: hundreds of granted US patents in RF ranging, real-time positioning, and computer vision, including US 11,774,249, US 12,079,006, US 12,066,561, and US 12,000,947, from a portfolio cited by Apple, Bosch, and other major firms in their own filings. A license buys two things at once: an implementation head start on the fusion and tracking math, and a defensible answer when a competitor's counsel starts reading your spec sheets. License the ranging math, ship the product.