Designing for the back pocket: building apps people want to open

In our first post I wrote a line I keep coming back to: we make apps people actually want to open. It reads well. But it is also the kind of sentence you can nod at and then forget by lunch. So let me slow down and say what it really means, because the difference between an app you open and an app you delete usually comes down to a handful of small choices.

Most of your apps live in your back pocket. They wait there all day. When you finally pull your phone out — on the bus, in a queue, half-distracted — the app gets a few seconds to be worth the trouble. That is the whole job. Be worth those few seconds, and don't waste them.

The first screen is a promise

The first thing you see when an app opens tells you what it thinks of you. A login wall before you have done anything says "prove yourself first." A pop-up asking for notifications before you know what the app even does says "give before you get." We try to lead with the thing you came for. Show the value, then ask for the favour — never the other way around.

It sounds obvious written down. It is surprisingly hard to do, because every team has a good reason to add one more step. The trick is to keep asking: would I want this on the first screen if it were my phone? Usually the answer trims the screen down to almost nothing, and that is the point.

Defaults are decisions you make for people

Most people never touch the settings. Not because they are lazy — because they have a life. So whatever you set as the default is, for almost everyone, the whole app. A good default is a small act of respect. It says "we thought about this so you don't have to."

We argue about defaults more than almost anything else. What is on by default? What is quiet by default? When in doubt, we pick the calmer option and let people turn things up if they want. It is easier to add than to apologise.

Speed is a feeling, not a number

People say they want fast apps, but they don't actually time anything. What they feel is whether the app responds when they touch it. A button that reacts right away feels fast even if the real work takes a moment behind the scenes. A frozen screen feels broken even when it is quietly doing its job. So we spend real effort on the in-between moments — the taps, the loads, the little waits — because that is where "fast" actually lives.

The kind thing is usually the quiet thing

Here is the theme that runs under all of it, the one we keep circling back to: Swedish calm over startup noise. An app does not need to celebrate every tap or beg you to come back. The kindest apps are a bit quiet. They do their job, they get out of your way, and they trust you to return on your own — usually with a coffee in hand. That is the kind of thing worth keeping in your back pocket. Hej for now, and thanks for reading.