November is young still, but it was the originally promised date so we have some weeks yet, but the surprising lack of mention of this in either regulatory fillings, changes in beta string analysis, or documentation has me wondering if this going to go the way of AirPower.
It's not been on the feature billet for 16.2 that is known to be released around late Nov/early Dec, and especially when coördinating with external companies like Globalstar & Qualcomm on things that require regulatory filings (which can be privacy flagged in the US which is the launch geography, so there's always that), and whenever Apple has trouble with something they tend to just pretend like it never existed (AirPower).
Anyone hear anything about this I'm missing? It's not a huge make or break, of course, but we live in a very remote part of CO and, just minutes out of town there is basically no cellular service for sometimes up to 1.5 hrs in any direction save for tiny pockets if you hold it JUST right (and even that's 3G roaming at best), and I need to decide whether to cancel my wife's inReach she keeps in her car or not. Not a huge deal (another $50), but it is curious to me how poor Apple's communications are on features that aren't making schedule or products they're having trouble with (the conspicuous lack of it in public comments around the 16.2 release and interviews is what I'm discussing here, it's still technically "on track" schedule wise but every other feature pitched in the release has been discussed save for this one AFAIK), especially when they were headliners or got dedicated airtime in the release announcements.
The cynical business person in me wonders how much of the announce was a hedge to the T-Mo/Starlink tie up tease (which is all that was, preempting what Musk/T-Mo knew was tech and licensure that is not anywhere near ready) to avoid feature disparity and they maybe went a bit too aggressive with a product/service/licensure that was not really ready (the Qualcomm chipset has the feature and is production quality and good to go, but kind of like the reverse wireless charging hardware has been there since iPhone 12 but only used for the MagSafe pack, that is no guarantee it ever will be lit up).
It's not been on the feature billet for 16.2 that is known to be released around late Nov/early Dec, and especially when coördinating with external companies like Globalstar & Qualcomm on things that require regulatory filings (which can be privacy flagged in the US which is the launch geography, so there's always that), and whenever Apple has trouble with something they tend to just pretend like it never existed (AirPower).
Anyone hear anything about this I'm missing? It's not a huge make or break, of course, but we live in a very remote part of CO and, just minutes out of town there is basically no cellular service for sometimes up to 1.5 hrs in any direction save for tiny pockets if you hold it JUST right (and even that's 3G roaming at best), and I need to decide whether to cancel my wife's inReach she keeps in her car or not. Not a huge deal (another $50), but it is curious to me how poor Apple's communications are on features that aren't making schedule or products they're having trouble with (the conspicuous lack of it in public comments around the 16.2 release and interviews is what I'm discussing here, it's still technically "on track" schedule wise but every other feature pitched in the release has been discussed save for this one AFAIK), especially when they were headliners or got dedicated airtime in the release announcements.
The cynical business person in me wonders how much of the announce was a hedge to the T-Mo/Starlink tie up tease (which is all that was, preempting what Musk/T-Mo knew was tech and licensure that is not anywhere near ready) to avoid feature disparity and they maybe went a bit too aggressive with a product/service/licensure that was not really ready (the Qualcomm chipset has the feature and is production quality and good to go, but kind of like the reverse wireless charging hardware has been there since iPhone 12 but only used for the MagSafe pack, that is no guarantee it ever will be lit up).
Last edited:
