Safari's Three New Settings — and Why They Won't Matter Yet

Apple announced three new Safari features in iOS 27 that finally put the browser in conversation with Chrome and Firefox on automation. The tension nobody's naming is this: a setting that lives in Safari matters only if the work that needs it lives in Safari too.

Tab groups, reading mode settings, and granular privacy controls are things users have asked for because they solve real friction. The person toggling between research and writing wants their Safari tabs organized by project. The person avoiding tracking pixels wants to control cookie behavior per-domain. These are not luxuries — they are the difference between a tool and a toolbox.

But here's where Apple's historical strategy catches up with itself. Chrome won its market share partly because third-party automation tools — Alfred, Raycast, keyboard maestro. Could hook into Chrome tabs, history. Settings from the operating system. A power user builds a workflow around this assumed integration. Safari has always resisted this architecture. Is part of why it felt slower to adopt automation culture even when the features technically existed.

The three new iOS 27 settings attempt to close this gap. They probably won't. Apple's App Store rules still prevent third-party tools from deep integration with Safari in ways that would make these settings matter outside the browser itself. You can organize your tabs beautifully. You cannot build a workflow that talks to that organization and your email and your file system all at once. Apple has not changed the rules that prevent it. Chrome users built those workflows years ago. That is the actual competitive problem, and three new settings do not solve it.

What matters is not whether these features exist. It is whether they exist where the work happens. Until Apple changes its integration policy, iOS 27 Safari is adding furniture to a room nobody uses. The features are real. The friction they solve is real. But friction that still costs you switching apps and rebuilding workflows is friction that never quite goes away.