Why the app made the phone hot

Why the app made the phone hot

Some bugs don't show up in a screenshot. Everything on screen looks right, every button does what it should, and the phone in your hand slowly gets hot.

That was today. On a new app we're building, the phone kept heating up during testing. Nothing was broken in the usual sense. The app worked. The phone just felt it.

It's an odd thing to chase, because the symptom is in your palm, not on the display.

Working isn't the same as behaving

The cause turned out to be ordinary. The app was doing background work too often. It kept checking for updates, again and again, more often than anything on screen needed, and it carried on doing some of that even when nobody was looking at it.

Each check on its own is tiny. Stacked up, they keep the phone busy, and a busy phone gets warm.

The fix was mostly to do less. The app now checks less often, and it pauses some of that work when it isn't on screen. Nothing new was added. A few things simply happen less.

I don't know yet whether that's the whole story. The change is in, and the next test build will show whether the phone stays cool.

How often is a design question

It's easy to file this under engineering and move on. I think it's design.

How often an app refreshes is a decision about what the person needs to see, and how fresh it really has to be. Someone makes that decision, even when it's made by leaving a default alone. And the person holding the phone lives with the result, whether or not it ever appears in a design file.

When we design a screen, we ask whether each element earns its place. It's easy to skip that question for the work an app does out of sight. The phone doesn't skip it. Heat is part of the experience, it just never shows up in a mockup.

For a studio that keeps talking about less, this is the kind of less that's hardest to see. A calmer screen is nice. A calmer phone is the same idea, one layer down.

Where less can go too far

Doing less in the background has a cost. Check too rarely and people see things that are out of date, or wait for something that should already be there. For some apps, freshness really matters, and the better answer is to keep checking but make each check cheaper.

So this isn't a rule to do as little as possible. It's a question worth asking on purpose, early: how often does this actually need to happen for the person to be well served, and what should the app be doing when it isn't even open?

Honestly, I'd rather ask it while designing than learn it from a warm phone.

Let the phone rest

If a phone gets hot while someone uses your app, that's feedback, even if nothing on screen is wrong. Sometimes the best fix is an app that does less when nobody's watching.

More about the studio at mindfull.studio.