There’s a feature in almost every major app you use that would meaningfully improve your experience. You don’t know about it. That’s not an accident.
Burying capabilities is a deliberate pattern across the tech industry, and the reasons are more varied and more cynical than most users assume. Here are the main mechanisms at work.
1. Hidden Features Create Perceived Value Gaps Between Tiers
Subscription products need users to feel the difference between free and paid. One reliable way to manufacture that gap: take a feature that works fine for everyone and make it invisible unless you’re on a higher plan. Not disabled. Not locked. Just invisible.
The dark pattern here is subtle. If you never discover that automatic meeting transcription exists in the version you’re already paying for, you might upgrade to get AI summaries, not realizing the transcript you needed was already there. Notion, Zoom, and Slack all have meaningful capabilities buried in settings menus that free users never encounter, which creates a pressure to upgrade that’s based on perceived scarcity rather than actual product differentiation.
This is different from genuinely gating features by tier. Gating is honest. Hiding creates false impressions about what you already own.
2. Powerful Features Attract Power Users Who Are Expensive to Support
This one sounds almost reasonable until you think it through. If a feature is genuinely useful but complex, surfacing it prominently means more users will try it, more users will get confused, and more support tickets will land in the queue. Keeping it buried is a form of self-selection: only the users who specifically go looking will find it, and those users are less likely to need hand-holding.
The problem is that this logic scales to absurdity. You end up with products where 90% of users are underserved because the company optimized support costs instead of user outcomes. Adobe’s creative applications are a good example. The feature depth in Photoshop and Premiere is extraordinary, but the discoverability is so poor that entire industries of tutorial creators exist just to translate the software into usable knowledge. Adobe tolerates this, partly because it builds switching costs, partly because it keeps the certified-trainer ecosystem alive, and partly because confused users rarely churn. They just stay confused.
3. Engagement Metrics Reward Surface-Level Features Disproportionately
Product teams are measured on metrics that favor what users click on, not what users benefit from. A feature buried in settings gets zero clicks during onboarding and therefore looks dead in the analytics. A dopamine-optimized notification prompt gets clicked constantly and looks thriving. So the notification prompt gets A/B tested and refined while the useful-but-quiet feature gets no resources and eventually gets cut.
This creates a systematic bias toward features that demand attention over features that quietly improve outcomes. The result is apps that feel increasingly busy and increasingly shallow. Calendar apps that push you toward prettier views instead of surfacing scheduling conflicts. Email clients that optimize open rates instead of helping you reach inbox zero. The metric is a proxy for value, and like all proxies, it eventually diverges from the thing it was supposed to measure.
4. Discoverability Is Often Sacrificed to Protect Existing Revenue Streams
Sometimes a feature is buried not because it’s complex, but because surfacing it would cannibalize something the company currently charges for. Google Workspace has document version history features that, if prominent, would reduce demand for third-party backup services. Apple’s Screen Time controls are powerful enough that many dedicated parental control app subscriptions become redundant, but Screen Time is not exactly front-and-center in iOS onboarding.
This dynamic gets more pointed when third-party integrations are involved. A platform that surfaces its own competing native feature risks angering the app developers whose products live in its store and whose presence makes the platform valuable. So the native feature stays quiet, the third-party apps keep their revenue, and the user keeps paying for something they didn’t need to.
5. Complexity Is a Moat, and Discoverable Features Reduce Complexity
There’s a well-documented strategic value in making products hard to replicate. Part of what makes a platform hard to clone is that users have invested time learning its idiosyncrasies, including the idiosyncrasy of knowing where things are. If a competitor built the same feature set with better discoverability, the switching cost would drop. Keeping features hidden is, counterintuitively, a way of making the product stickier.
This connects to a broader point about feature debt as a deliberate moat. The accumulated complexity of a mature platform is not purely a liability. It’s also a barrier. Users who have spent years learning where Adobe hides its advanced compositing tools aren’t going to switch to a cleaner competitor, even if the competitor is objectively better designed. The learning investment creates loyalty that has nothing to do with product quality.
6. Dark Patterns in Onboarding Filter for Compliant Users
When you onboard a new user, you’re making choices about what they learn to expect. Most onboarding flows teach users to accept defaults, click through prompts quickly, and stay in the main feed. Users who learn this pattern early rarely deviate from it. They never dig into settings. They never discover that the app can behave differently.
This is not neutral design. It’s conditioning. Companies that want users in a passive, high-engagement mode have every incentive to onboard them into that mode and to ensure that the features enabling more deliberate, self-directed use stay invisible until the user has already formed habits around the default experience. The user who discovers granular notification controls on day one might end up using the app for twenty minutes a day. The user who never discovers them might spend three hours.
The measurable outcome most companies optimize for is the three-hour user, regardless of whether that user is getting more value from the product.
7. Regulatory Compliance Features Are Buried By Design
Privacy controls, data deletion tools, advertising opt-outs: these are features companies are often legally required to provide but have strong financial incentives to make inaccessible. The pattern is consistent enough that regulators have started naming it explicitly. The FTC’s 2022 dark patterns report cited numerous examples of companies placing data controls behind multiple menus, using confusing language, and requiring users to repeat opt-out choices after every update.
The buried privacy toggle is the purest version of the hidden feature problem because it strips away any plausible UX justification. These companies know exactly how to make things discoverable. They do it every day with features that benefit their revenue. When they bury something, they’re making a choice about whose interests the design serves.
