When Everything Becomes an App, Everything Becomes a Gatekeeper

Apr 26, 2026

7 min read

5 views

87%

The hidden tax on ordinary life

What if the real cost of modern software is not money, but permission?

That is the uncomfortable pattern hiding in plain sight. A growing number of everyday tasks, from booking a flight to finding a job, now ask you to enter a walled garden before you can simply get the thing done. In theory, the web should have made these tasks easier, lighter, and more universal. In practice, many of them have been pulled back into app stores, native clients, and platform-controlled ecosystems where access is no longer just about usability, but about who gets to define the route.

This is more than an annoyance. It is a structural shift. The internet once promised a document web, a world where information and services were reachable through open, linkable pages. But the more that everyday actions migrate into apps, the more the web starts to resemble a mall with separate entrances, private security, and arbitrary opening hours. The user is still walking, but the path is no longer public.

That same dynamic is appearing in another domain that was supposed to be radically open: blockchain. A single dominant infrastructure can be so successful that it becomes the default substrate for almost everything, until the ecosystem around it stops feeling like a commons and starts feeling like a crowded transit hub. The question is not simply whether the technology works. The deeper question is whether success itself can become a form of exclusion.

The paradox of success: openness that turns into enclosure

Open systems often begin by reducing friction. The web reduced the friction of publishing. Blockchains reduce the friction of building financial systems without central intermediaries. But once a system becomes valuable, the incentives reverse. The easiest path for users becomes the most attractive path for gatekeepers to control.

On mobile, this means nudging people away from browser-based access and into apps. An app is not just a better interface. It is a distribution channel, an identity layer, a data collection point, and a policy lever. If you must install an app to do a task that used to be possible in a browser, you are not merely downloading software. You are accepting a new landlord.

The same thing happens in blockchain ecosystems. When one chain becomes the center of gravity for a major category like DeFi, developers build where the liquidity is, users follow where the tools are, and soon the platform is no longer just an option among many. It becomes the default toll road. That may feel efficient at first, but it also means other kinds of applications, especially those that do not fit the dominant use case, get pushed to the margins. The system is open in theory, but in practice it can become crowded out by its own gravity.

The most dangerous monopoly is not the one that forbids alternatives. It is the one that makes alternatives feel impractical.

That is the hidden convergence between browser erosion and blockchain concentration. In both cases, an ostensibly open architecture becomes less open not because access is formally denied, but because the incentives around the architecture make nonconforming paths inconvenient, invisible, or uneconomic.

Why convenience is the engine of enclosure

Most people think platform power comes from control. Control matters, but convenience is often the real weapon.

An app is convenient because it can be fast, polished, and deeply integrated with device capabilities. A dominant blockchain is convenient because everyone else is already there, the liquidity is deep, and the tools are mature. In both cases, convenience is not neutral. It is a sorting mechanism that concentrates activity around the most monetizable and governable layer.

Consider the everyday example of buying a book. In a truly web native world, you should be able to search, compare, pay, and receive confirmation in a browser. But when the process gets split across app installs, in app accounts, and device specific flows, the user is no longer just completing a purchase. They are moving through a sequence of dependencies that each tighten the platform's grip.

Now compare that to a DeFi protocol. A simple swap or lend operation looks like decentralized finance, but if almost all the liquidity, integrations, and developer attention cluster on one chain, then the ecosystem develops a bottleneck. The chain becomes the place where value happens, and everything else becomes a secondary neighborhood. The promise of decentralization remains technically true, while the practical experience becomes increasingly centralized around a few hubs.

The pattern is the same: the more successful the platform, the more it can define what counts as normal. Once normality is defined, anything outside it looks like friction, and friction becomes the justification for further consolidation.

This is why the battle is not merely between apps and browsers, or between chains and competitors. It is a battle over the default path. Defaults are infrastructure with a personality. They shape behavior long before users consciously choose anything.

The myth of the universal layer

Both the web and blockchains are often sold as universal layers. One layer for documents and services. One layer for trust and value.

But universality is fragile. It depends on whether the layer remains genuinely general purpose or whether it gets hollowed out by specialized interests. A browser is most powerful when it can do most things well enough. A blockchain ecosystem is most powerful when it can support multiple classes of applications without forcing everything into one dominant pattern.

The problem is that high volume use cases distort the layer itself. If the web is optimized around ad driven engagement, login walls, and app promotion, then it stops being a neutral transport for knowledge and services. If a blockchain is optimized around a single lucrative category, then it stops being a broad platform and becomes a specialized marketplace with a universal veneer.

This is the deeper tension: general purpose systems tend to become specialized under pressure. Not because anyone planned it that way, but because the economics of scale reward the most profitable use case and starve the rest.

A useful analogy is the shopping mall. At first, the mall seems like a convenient aggregation of many stores. Over time, though, the mall operator decides who gets visibility, what kinds of tenants are welcome, how traffic is routed, and what behaviors are allowed. The mall still contains many stores, but the commons has become a controlled environment. That is what happens when an open layer quietly becomes the main venue for a narrow set of applications.

The web and blockchain share a deeper challenge: they are both vulnerable to becoming infrastructure in name, platform in practice.

A framework for spotting enclosure before it is obvious

If you want to know whether an open system is being enclosed, ask four questions.

1. Can the task be completed without installing a new gatekeeper?

If the answer is no, the system has likely crossed from open access into managed access. Installing software is not inherently bad. The question is whether installation is justified by genuine functionality, or whether it exists mainly to capture attention, identity, and habit.

2. Is the dominant path the best path, or simply the most controlled one?

A browser may be less flashy than an app, but it often preserves user autonomy. A less popular blockchain may look less efficient than the dominant one, but it may better preserve diversity of use cases. Do not confuse polish with openness.

3. Are alternatives technically possible but economically starved?

This is where enclosure becomes subtle. Alternatives may exist in theory while being impossible to sustain in practice because liquidity, distribution, or visibility all cluster elsewhere. When that happens, the market no longer rewards better ideas. It rewards proximity to the dominant hub.

4. Does the ecosystem serve many kinds of users, or just one lucrative archetype?

An open platform should make room for rare, awkward, unprofitable, or nonstandard uses. If the system is only beautiful when it is serving its highest margin use case, then it is not really universal. It is specialized, with an open face.

This framework matters because enclosure often arrives disguised as progress. Faster onboarding, smoother payments, richer interfaces, deeper liquidity, better developer tooling: all of these are real benefits. But they can also be the mask worn by concentration.

A system can become easier to use while becoming harder to leave.

That is the sentence every platform designer, policymaker, and user should keep in view.

The actionable shift: build for portability, not just performance

If the core danger is enclosure through convenience, the answer is not to reject convenience. The answer is to design and choose systems that preserve portability.

Portability means that the user can move, switch, exit, or recombine without losing the basic ability to participate. A browser native service is portable because it travels with standards. A healthy blockchain ecosystem is portable because it does not force every meaningful activity into one chain, one bridge, or one liquidity center.

For product builders, this means asking a different question than the usual one. Instead of only asking,