Skip to main content

Don't Put The App On A Pedestal

Almost every application you use is an interface over a data lake you do not own. Knowing that changes how you choose, how you use, and what you are willing to invest in.

The Misunderstanding​

A lot of smart people have organized their lives and businesses around platforms they do not own. "I need to build an X following." Why? Because building an X following is what serious people do, apparently. "I need to grow my Instagram." Why? Because that is what successful businesses do. "I have to be on TikTok." Why? Because the algorithm is where attention lives.

The pedestal under those statements is the application itself. The app gets treated as the destination. The work becomes optimizing for the app's metrics, the app's algorithm, the app's culture, the app's incentives. After enough years, the operator's identity, audience, and business are owned by the platform. The platform writes the rules. The platform changes the rules. The platform deprecates the operator at will.

This is a category error. The app is a tool, and the right relationship to a tool is to wield it for the time it serves you and to set it down when it does not.

What An App Actually Is​

Take a step back. Almost every consumer or business application you can name is an interface over a data lake. The data lake holds information about you, your customers, your patterns, your preferences, your contacts, your purchases, your messages. The interface lets you query that lake and act on the results.

This was true before AI. Pinterest is an interface over a data lake of your boards, your saves, your aesthetic patterns. LinkedIn is an interface over a data lake of your professional graph. Strava is an interface over a data lake of your runs. Spotify is an interface over a data lake of your listens. The visible app is the surface. The lake under it is the asset.

The contract you signed when you started using the app gave the app the lake. If the app is genuinely useful to you, the trade is asymmetric: the lake belongs to the platform, and you pay rent (in attention, in subscription dollars, in data exhaust) to access your own patterns through the interface the platform provides. The personalization you experience is the lake refracting back at you through the platform's interpretation of you.

If the personalization is precise, you have given the platform a lot. If you cannot remember handing it that much information, you handed it that much information passively, click by click, over years.

If the app dies, the lake dies with it. Your patterns, your graph, your taste, the years of context you accumulated, gone. The thing you built is locked behind a door whose key you never owned.

How To Tell If You Are On The Pedestal Path​

A few diagnostic questions:

  • Are you optimizing for the app's metrics, or for your real outcome? Followers, likes, monthly active users, watch time. The metrics belong to the platform. Optimizing for them is optimizing for the platform.
  • What happens to your work if the app changes its terms tomorrow? If the answer is "I lose months or years of work," the app is on the pedestal.
  • Can you export your context if you wanted to? Some apps allow real export. Most allow a sanitized excerpt. The gap is the lake the platform is keeping.
  • Are you talking about the app more than the work the app is supposed to enable? If yes, the surface has eclipsed the substance.

The healthy posture is the inverse of the pedestal. You are doing meaningful work in the world. The app is one tool you use to make that work go faster or reach more people. When the app stops serving the work, you stop using it. The work is the constant.

The Shift​

The structural fix is to own your own context. [See: Context Lake] for the practitioner-scale version of this idea. Plain text files. Markdown. A folder structure you control. The lake of who you are, what you are building, who matters to you, and what you have decided lives on your machine, in your repo, under your hand.

When your context lives where you control it, applications become things you point AT your context. The context is sovereign. The interface is replaceable. Drop one app, swap to another, and the lake comes with you because it was always yours.

The economic model that grows up around this looks different from the platform model. People stop paying rent to platforms that hoard their data and start paying for help managing their own context: skill files, workflows, training, community.

Some of it is open source. Some of it is what we might call paid source: workflows and skill files you pay a one-time fee or a community membership to access, with the result fully running on top of your own context. [See: Skill File First, App Second] for the development pattern that produces these.

The platform model says: come live in our world, give us your data, accept our rules.

The context-sovereignty model says: keep your data, keep your rules, pay practitioners for the workflows and skills that operate on top of your own lake.

What This Means For Operators​

Three practical shifts.

Shift one: own your context. Build a context lake you control. Put it in version control. Treat it as the asset every workflow runs on top of. [See: Externalize Your Brain.]

Shift two: use apps deliberately. Audit which apps you currently treat as destinations. For each one, name the work it is actually supposed to enable. Anchor your attention back to that work. The app stays on the toolbox shelf, off the pedestal in your head.

Shift three: pay for context, not for platforms. When you spend money on capability, prefer the model that leaves you owning the result. A skill file, a workflow, a community that teaches you how to operate on your own context. Subscriptions to platforms that hoard your data cost the same money and leave you with less when the relationship ends.

Awareness Is The First Move​

You will not exit every platform tomorrow. Most operators cannot. Some of these tools are genuinely useful and the data trade is, for now, worth it.

What changes after reading this is not the tool stack. The awareness changes. You see the contract clearly. You stop putting the app on the pedestal in your head, even before you have replaced the app in your stack. The next time you make a decision about which platform to invest in, the question becomes different. Where is the lake going to live? Whose interface is the surface? When this app dies in 2032, what walks out the door with me?

That awareness is the first move. The architecture decisions follow from there.

This concept is also documented in the Imagos trust-circle wiki at truth.imagoslabs.com.