That powerful privacy control buried four menus deep isn’t hard to find by accident. It’s hard to find on purpose. The feature graveyard inside every major tech product — the notification controls, the data export tools, the algorithmic feed toggles — exists because surfacing those features would cost money, reduce engagement, or complicate a story being told to advertisers and investors. The burial is the product decision.
The Default Is the Revenue Model
Defaults are not neutral. Every product manager knows that most users never change them. The research on this goes back decades, from organ donor opt-in rates to retirement savings enrollment. In software, the default state of a product is almost always the state that maximizes the company’s core metric, whether that’s time-on-app, ad impressions, or data collection scope.
Facebook’s privacy controls are the canonical example. After repeated regulatory pressure, Meta has added granular controls over data sharing and ad targeting. They exist. They are genuinely functional. They are also buried under layers of navigation that require sustained intention to find, and the default state for new accounts captures the maximum permissible data. The controls were built for regulators, not users. Their placement reflects that honestly.
This is not cynicism. It is product logic. When your revenue depends on behavioral data, and you can choose between making the opt-out prominent or making it findable-if-you-really-try, the business case for prominence does not exist. There is no A/B test that ends with ‘let’s make the data-sharing toggle the first thing people see.’
Power Features Threaten the Core Narrative
Sometimes the burial has nothing to do with revenue and everything to do with positioning. Apple’s Accessibility settings contain genuinely extraordinary functionality: granular display adjustments, motor control accommodations, audio routing options that rival dedicated hardware. Almost none of it appears in the main Settings flow or in Apple’s marketing.
Apple markets simplicity. Surfacing those features prominently would complicate the ‘it just works’ story that distinguishes the brand. The features exist because Apple takes accessibility seriously as an engineering matter. They are hidden because Apple takes brand coherence seriously as a business matter. Both things are true simultaneously.
The same dynamic plays out across the industry. Google Chrome has powerful memory and performance controls accessible through chrome://flags that most users never encounter. The browser’s mass-market positioning depends on appearing frictionless. Surfacing those controls would invite questions about why the browser needs them at all.
Friction Is a Filter, and the Filter Is Intentional
There is a version of the settings-burial argument that sounds reasonable: complex features belong in settings because they would overwhelm casual users. This is sometimes true. A raw SQL query interface should not be the first thing a new database user sees.
But the filtering argument is being abused. When a feature’s primary effect is to give users more control over their own experience, and that feature is buried, the friction is not protecting users from complexity. It is protecting the company from the consequence of users exercising that control.
Chrome’s ad privacy settings, LinkedIn’s feed algorithm controls, Twitter/X’s content filtering options: none of these are complex in the way that a developer API is complex. A toggle labeled ‘show fewer posts from accounts you don’t follow’ is not cognitively demanding. It is commercially inconvenient, which is why it lives four taps from the home screen.
The Counterargument
The honest counterargument is that good UX genuinely requires hierarchy. Every feature cannot be on the home screen. Designers have to make choices, and those choices will inevitably reflect priorities. A company that puts its data controls on the front page might genuinely be making a worse product for the majority of users who do not want to think about data controls every time they open an app.
This is a real tension and it deserves credit. The problem is that the companies making this argument are the same companies whose engagement teams obsessively A/B test notification cadences and feed ranking algorithms. The claim that feature placement is determined by pure UX reasoning, insulated from business outcomes, strains credibility. When a company can tell you exactly how many minutes per day a ranking change added to average session length, it can also tell you what happens to those minutes when users find the feed control. The data exists. The choice not to surface the feature is a choice, not an oversight.
The Honest Version of This Story
Tech companies are not uniquely villainous for making these decisions. Every business optimizes its product for business outcomes. The problem is the gap between the public framing (‘we empower our users’) and the operational reality (‘we empower our users to the extent that it does not cost us engagement’). As enterprise software contracts demonstrate, the architecture of a product reveals the actual business model more honestly than any press release.
The next time a product you use adds a meaningful user control after regulatory pressure or a public controversy, do one thing before you feel reassured: find it. Count the taps. Note where it lives in the information hierarchy. The distance between the front door and that setting is a precise measurement of how seriously the company wanted you to use it.
