Stop Thinking in Apps

Software has trained us to think in apps.

Want to take a trip? Open one app for flights, another for a place to stay, another for a ride, another for tickets, another to check the weather.

Need something done around the house? Figure out which service handles it, find the app, sign in, search again, and reconstruct enough context for that company to understand what you need.

Even the relationships you already have work this way. Your insurance policy exists. Your bank account exists. Your airline status exists. Your subscriptions exist. But using any of them usually means remembering where that relationship lives, and navigating back into that company's version of it.

The world is organized around institutions. Our lives aren't.

Intent comes before the app

Imagine saying, out loud, to no one in particular:

I'm taking the kids skiing this weekend.

That's a perfectly ordinary human sentence. But software doesn't usually take it that way.

Instead, we do the translation ourselves. Where should we go? What's the weather going to do? Do we need a place to stay? What about lift tickets? Is there something we've already paid for that covers part of this? What benefits do we already have sitting unused? What actually needs to be booked, and what doesn't?

Then we sort all of that into the right apps and the right websites, one at a time.

We've become the integration layer. That feels backwards. The person should be able to say what they want. The technology should do more of the work of figuring out what in the world can help.

A relationship doesn't have to be a destination

There's a quieter assumption worth questioning too: that a relationship with a company is a place you visit.

Your insurer is an app. Your bank is an app. Your airline is an app.

But the relationship itself was never really the app. It's a policy. An account. A reservation. A membership. A home. A service you use. A capability that's available to you, whether or not you happen to be looking at it right now.

What if a relationship didn't require you to keep coming back to its front door?

Then "show me my insurance card" stops being a navigation problem. So does "change my seat," or "what's the balance on that account," or "when does this renew." You already have the relationship. The useful part was always what it lets you do — not where it lives.

Shopping changes too

That same shift changes what a marketplace even is.

Today, a marketplace is somewhere you go: you enter, browse a set of options, choose one, transact, and leave. But sometimes you don't need another option. You already have what you need — you just don't always know it in the moment you need it.

If you're planning a trip, the best answer might already be something you have. Other times, there's a real choice to make, and discovering something new is exactly the right move. Those two situations shouldn't have to feel like entirely different kinds of computing.

The better question isn't where should I shop. It's what am I actually trying to accomplish, what's already available to me, and what's still missing. Discovery only needs to start once that last question has a real answer.

From destinations to capabilities

There's a bigger idea underneath all of this: the internet gave every institution a destination. Maybe the next step is making the useful parts of the world available without asking people to keep visiting those destinations themselves.

That doesn't mean the companies disappear. Quite the opposite — the insurer should stay the insurer, the bank should stay the bank, the airline should stay the airline. They remain exactly as responsible for the relationships and services they provide as they've always been.

What changes is what it feels like to use them. Instead of carrying the burden of remembering where everything lives, how each interface works, and which sequence of apps might add up to what you actually wanted, a person could just start with the wanting.

The world you already have

This might be the part that matters most.

So much of technology is built to help us find the next thing — the next product, the next provider, the next purchase. But every one of us already has a world: relationships, services, memberships, possessions, commitments, reservations, accounts, people.

A genuinely useful system shouldn't start every request by searching for something new. It should start by understanding what's already there. Only once something is actually missing does it need to go looking.

That points to a different idea of a marketplace entirely — not a destination stocked with things to buy, but a moment: the moment an unmet intention meets something in the world capable of answering it.

And often, the best answer won't be something new at all.

It'll be something you already have.