The Cost of an Icon

How to Determine if a Native App Actually Drives Business Value.

Open your phone and swipe through your home screen. Pause on the first two screens of icons.

Every square there earned a place: banking, messaging, maps, a couple of socials, maybe a delivery app that turned into muscle memory. After that, the grid becomes more chaotic or even hidden by the OS: parking, check-ins, appointments, or single-use tools. Many arrive with urgency and are then forgotten.

We spend a lot of time in that tension between “install” and “keep”.

From our POV, the conversation usually begins the same way: “We need a mobile app.”

Behind that sentence lives a long wish list: stronger engagement, deeper loyalty, more completed flows, a permanent home on someone's screen. The instinct feels familiar. If something feels important, we want it in our pocket with its own icon.

Our first question drifts somewhere else: Who is this product for? How does it fit into someone's routine? And why is this the right format for the results you want?

A mobile app is the right format when usage is continuous and intentional:

• frequent, almost automatic use
• clear benefits from push, camera, microphone, NFC, Face ID
• a relationship where the icon feels like a trusted tool

In that world, asking for the extra effort feels fair. People search the store, install, create an account, grant permissions, and accept updates. The app becomes part of the personal toolkit, side by side with the ones that shape their routines.

On the business side, the commitment is substantial. Mobile apps cost more to build, more to maintain, and depend on app store policies, requiring constant iteration to stay relevant. This is why we need to understand whether the behavior you want genuinely benefits from what only a native app can offer.

So before we discuss format, we usually move through a different set of questions:

• Who exactly uses this, and in which scene of their day?
• How many times per month do they realistically return?
• What level of effort do we ask in exchange for a single action?
• Does the core value truly depend on deep device capabilities?

Recently, we partnered with an education platform. The brief arrived with a clear direction: a native mobile app. Their users weren't completing a key part of the learning process, so the team imagined an icon on the home screen, plus push notifications, as the missing bridge toward commitment.

But the system was already sending reminders. WhatsApp. Email. Nudges everywhere. So we paused to understand something deeper: if people weren't responding to the messages they already had, what problem was the app supposed to solve?

We dove into recordings, metrics, drop-off curves and time stamps. Little by little, another picture came into focus: the order of steps, the timing of each request, the cognitive load hidden inside every screen. Before defining format or estimating build costs, we ran a short discovery on the commercial side to understand the real friction.

This approach captures a big part of how we think at Aerolab. First, we map problems, people, moments of use, and the business they serve. Then we choose the stacks, channels, and formats that deserve to exist in that reality. Sometimes the answer is a mobile app that earns a steady place on the home screen. Other times, it's a web experience that solves the problem in a way the team hadn't originally considered.

In both cases, the real goal remains the same: build products that feel welcome in someone's life, long after the release announcement scrolls away.

Whether you're refining a product or shaping a new one, it's worth pressure-testing the format.