Google weighs return of separate Android connectivity toggles

Google is preparing a possible reversal of one of its most debated Android interface decisions, with beta indicators suggesting that separate Wi-Fi and mobile data toggles could reappear in Quick Settings after being merged three years ago. The change, still under development, signals a renewed focus on usability following sustained feedback from users and developers who argued that the combined control added friction to everyday connectivity tasks.

The controversy dates back to Android 12, when Google consolidated Wi-Fi and mobile data into a single “Internet” tile in the Quick Settings shade. The redesign aimed to simplify controls and reflect how devices increasingly switch between networks automatically. Instead, it triggered criticism from users who found common actions—such as toggling Wi-Fi off briefly or switching to mobile data during network congestion—now required extra taps and menu navigation.

Code strings and interface elements discovered in Android beta builds point to a configuration that restores discrete Wi-Fi and mobile data tiles, either as a default or an optional setting. While the company has not confirmed a release timeline, the presence of these controls in testing builds suggests active evaluation rather than a shelved experiment. Historically, Google has used extended beta cycles to gauge response before locking down interface behaviour for major releases.

The merged “Internet” tile became emblematic of a broader debate within Android’s design evolution. Supporters of the change argued that it aligned with automation, reducing the need for manual switching as phones intelligently select the best available connection. Critics countered that the design underestimated edge cases, such as public Wi-Fi networks requiring repeated authentication, unstable hotspots, or power users who frequently manage connections for work and travel.

Industry observers note that feedback on the Internet tile remained unusually persistent across Android versions. Online forums, developer issue trackers and accessibility discussions repeatedly flagged the extra steps as a regression rather than a refinement. Accessibility advocates also pointed out that additional taps can disproportionately affect users with motor impairments, making rapid access to essential controls more than a matter of convenience.

If implemented, the return of separate toggles would represent a pragmatic recalibration rather than a wholesale retreat from Google’s design philosophy. Android’s Quick Settings has increasingly moved towards customisation, allowing users to rearrange tiles, hide seldom-used functions and prioritise controls that suit individual habits. Separate connectivity toggles would fit within that trajectory, offering choice without dismantling the underlying system logic.

The potential change also reflects a pattern in Android’s development cycle, where controversial interface decisions are softened over time rather than abruptly reversed. Previous iterations have seen similar adjustments, with features initially positioned as universal defaults later becoming optional settings. This approach allows Google to preserve its long-term vision while acknowledging that one size rarely fits all in a platform used by billions across diverse contexts.

Manufacturers that customise Android are watching closely. Device makers often layer their own connectivity controls on top of stock Android, partly to address user complaints about the Internet tile. A native solution could reduce fragmentation and lessen the need for proprietary workarounds, particularly for brands that market ease of use as a differentiator.

Developers, too, stand to benefit from clearer system behaviour. Network-dependent applications, from streaming services to enterprise tools, rely on predictable connectivity states. While the merged tile did not alter underlying APIs, confusion at the user interface level sometimes translated into misattributed app issues when connections behaved unexpectedly.