Solving for iOS 11 Control Center's new Wi-Fi and BT toggles
Prior to iOS 11, toggling off Wi-Fi and Bluetooth in Control Center killed those radios dead. Now, it only kills current connections but leaves everything from Apple Watch and Apple Pencil connections and AirDrop and Universal Clipboard features running as normal. And some people aren't happy about it.
Apple has to meet the needs of hundreds of millions of customers from first-time users to long-time pros. Sometimes those needs are in conflict.
For example, it wasn't intuitive to first-time, casual, and mainstream customers that turning off Wi-Fi and/or Bluetooth would cause AirDrop, Instant Hotspot, call and SMS relay, and other features to stop working. Or, that it would cause Apple Watch, Apple Pencil, and even AirPods to cut out. Many of us have had first-hand experience helping family members with exactly those problems.
Having the Control Center toggles shut off the current Wi-Fi connection or third-party Bluetooth devices, but keep Continuity services and Apple Pencil and Apple Watch-style deeply-connected accessories keep going makes the most sense to that user group, And it's a big user group.
But, it comes at the expense of longer-term, more expert users who know full well how the protocols and radios work, and are used to how Control Center toggled them in previous versions of iOS. You know, the ones who want "off" to mean "OFF".
To further complicate matters, connections re-active when you come in range of known networks, or at 5 a.m. local time, because Apple decided that makes sense. The result is a state that's no longer binary or predictable, which is incredibly frustrating for people who expect it to be both.
Turning off Wi-Fi and Bluetooth in Settings remains as it was — absolute as in off means OFF. But it's not as readily nor as quickly accessible. And that's inconvenient.
I'm not opposed to the change in theory. Persisting Continuity and deeply-connected accessories is a good thing. But the current implementation isn't a clear win for anyone.
There are several things Apple could do about it:
- Revert the change, which would again leave casual, mainstream users confused about why Continuity and deeply connected accessories stopped working just because Wi-Fi or Bluetooth was intentionally or accidentally tapped.
- Add multiple states to the switches — on, disconnect, and off — which would increase complexity and, potentially, confusion.
- Add an alert-on-toggle — "Are you sure you want to disconnect Apple Watch?" — which would add significant overhead and dialog fatigue to the process.
- Add a preference in Settings to restore the old behavior, which would just offload the problem to users.
My preference is currently for the 4th solution. Sure, it's "one more toggle", but it could be set to the new behavior by default — and most people, especially casual users, never change defaults — it would only add load to the long-term, expert users who want it and are most capable of handling it.
Apple's iOS team could likely come up with an even better solution, of course. It's their job to do just that.
As to the EFF's security issues with the new implementation, Bluetooth isn't going anywhere. With BT LE and now Bluetooth 5.0, and the aforementioned Continuity features and deeply connected devices, it's becoming increasingly critical to how we use and benefit from technology.
Bluetooth needs to do everything possible to make its protocol as secure as possible. Vendors need to make sure their Bluetooth stacks are bullet-proof. And people concerned about Bluetooth, in general, need to remember that can still kill it completely in Settings. That works the same way it always did.
Get the best of iMore in your inbox, every day!
Rene Ritchie is one of the most respected Apple analysts in the business, reaching a combined audience of over 40 million readers a month. His YouTube channel, Vector, has over 90 thousand subscribers and 14 million views and his podcasts, including Debug, have been downloaded over 20 million times. He also regularly co-hosts MacBreak Weekly for the TWiT network and co-hosted CES Live! and Talk Mobile. Based in Montreal, Rene is a former director of product marketing, web developer, and graphic designer. He's authored several books and appeared on numerous television and radio segments to discuss Apple and the technology industry. When not working, he likes to cook, grapple, and spend time with his friends and family.
I mean the toggles that are besides the Wi-Fi and Bluetooth mostly have two states which are clear - either lit or unlit and meaning that a certain function is either on or off. With the Wi-Fi and Bluetooth toggles there are now three states - lit, unlit and striked through. How is this easier for "simple users" that two lit toggles that are besides each other mean the same thing but the same two toggles when unlit mean different things and one toggle keeps getting lit again by itself and it also sometimes is striked through (after turning off via Settings) and is in a state that can never be reached via the actual toggle neither by pressing, long pressing or any other action with the toggle? When a user needs to look through articles on internet to get an understanding of how a simple toggle works, it isn't simple for "simple users".
If a person has used an iPhone previously and used the toggles, certain things can already be in muscle memory. E.g. before going out of home to turn off Wi-Fi not to waste precious battery life or not to connect to other already known Wi-Fi unnecessarily. I still find myself swiping up the control centre to turn off the Wi-Fi and then remembering - oh, wait, these toggles are useless garbage now, I need to unlock my device, go to Settings, go to Wi-Fi, turn it off and then lock the device again before I put in in my pocket. Neither quick, neither convenient.
When I just updated I thought it was a bug that my Wi-Fi toggle kept turning back on again. I had to do some searching before finding an official explanation by Apple of how they ruined the toggles and how they also take decision on my part to turn the toggles back on after I explicitly turned them off.
Also, do you not proof-read? "Solution" not "Solving"? I guess if you mean "Solving for X" but it really doesn't read for that.