|
|
|
|
|
by achierius
491 days ago
|
|
Tbf a lot of things "just work" on some devices, for some people's workflows -- even if it's happening every day for you, it might not be happening on the machines the engineers are living on. This can be because of different workflows, or habits, or particular combinations of versions/configurations (e.g. iPhone sku <A> with OS version <B>, laptop with SKU <C>, carplay with software version <D>, ...). |
|
Give me power to debug. Give me power to write my own solutions.
And we're talking about a notification... We're also talking about a pair of headphones that can't be connected to multiple devices at the same time for some reason. I can't see this as anything but a self-imposed problem. You could connect up to 7 devices at the same time and that would be a great way to provide the seamless experience. It is the same ecosystem, the phone and laptop can easily communicate and be aware that I have spotify open on both and that I'm writing on my laptop. But no, the problem gets harder because of the issues. I play music from my phone because if I walk away from my computer, I can keep playing music through my headphones. Where's the magic? And the only reason I have spotify open on my laptop is so that if I press the god damn play button I don't end up opening Apple Music (a product I have never intentionally used nor even passed the first time use screen), jumping from my workspace.
Users shouldn't need these defensive patterns when you have the capacity for such integration.