Earlier quoted context omitted.
There's also the problem of wireless tech UX being difficult in general. For example, people want the experience of turning on their devices and auto-pairing with their other devices. But headphones, for example, don't have much of a UI to manage this. There's the hellish scenario of everyone in your car hearing the conversation you thought you were having on your back patio in private just because you walked too clo…
Imagine if you connected this way: 1. turn on peripheral, 2. choose it from a UI on the device and get connected. That is easy, it is the auto-pairing bullshit that forces the software to guess using a heuristic, which guarantees it will get it wrong a non-zero amount of the time. Now that we all have N devices it will get it right 1 out of N times. This is just terrible UX, the choice reality gave us was between aut…
There is still the design problem there however. You kind of have to guess which one 1, 2, or 3 is. And you need the recipient device to actually be on and maintain the connection when you make the switch. So it's not just 1 UI interaction. Depending on your situation, there can be at least 3 and they're spread across multiple devices.
Ideally we'd have a standardized overlay or display on any bluetooth device to indicate its connection status and what it's paired to. But that would be its own headache and would seriously constrain how devices can look or be shaped. How much UI can you really fit on a pair of headphones that are meant to be small?