New categories are counted in places, not users.

By Dropalo Editorial

Most digital products count people. They count sign-ups, accounts, monthly users. That makes sense for software built around a person and a screen, because the person is the one who logs in.

But a lot of everyday life does not happen to one person at a time. It happens in environments: a hotel, a campus, a port, a shopping centre, a stadium. Each of these is not a single customer with a single login. It is a place with its own shape, its own rules and many people inside it at once.

One place, many parties

Think about what a stadium actually holds on a match day. There is the operator, the caterers, stewards, cleaners, broadcasters, the club, the away supporters who have never been there before and the regulars who know exactly which gate is quickest. A campus has academic departments, accommodation, security, a students’ union, contractors and visitors for open days. A port has terminals, hauliers, crews, agents and the people who simply work there every night.

None of these is one account. They are overlapping groups who share the same ground, often with different needs at the same moment. The person arriving at gate C at 2.45pm does not want the organisation’s whole website. They want to know what matters here, now.

Why the place gets flattened

There is no villain in this. Digital tools are measured by the people who use them, so they are designed around profiles, feeds and inboxes. The place itself cannot sign up. It has no login, so it rarely becomes the thing the software is organised around.

The result is familiar. An environment is described through a homepage, a PDF map, an app for one part of the site, a noticeboard for another and a group chat that only the regulars know about. The information exists, but it is arranged around who published it rather than where it applies.

What changes when the place is the unit

If you start from the place rather than the user, different questions come first.

  • What is true at this entrance, on this concourse, in this building, at this hour?
  • Who is allowed to speak for this part of the place, and who keeps it current?
  • What does a first-time visitor need, compared with someone who comes every day?
  • What should still be there tomorrow, after today’s visitors have gone home?

A visitor should not need to create an account to be welcomed by somewhere they are standing in. The place should be able to tell them what they need, in terms of where they are.

Which layers will be copied

Some parts of this are already well served, and will keep getting cheaper and more alike. Logins, messaging, payments, booking and general-purpose maps are layers that many companies can build. They will be copied and commoditised, and that is fine.

The harder layer is the place itself as a digital participant: a hotel lobby, a lecture theatre or a quayside that holds its own current context and lets the right people keep it up to date. That layer depends on knowing places one by one, not counting users in aggregate.

That is the direction Dropalo is working towards: digitising physical places so that each one can speak for itself. It is a description of where we are heading, not a list of shipped features for any particular venue.

A user is someone who visits. A place is what they visit. New kinds of digital products may be counted in places, not users.