App Zero: Get Mobile Right the First Time is a series for PMs at established companies who've been handed a mobile mandate and don't want to blow it.
TL:DR
Someone in a conference room points at a laptop and says, "We basically need this, but for mobile." The room nods. That's where it goes wrong. Porting your web product onto a smaller screen isn't a mobile strategy. Web assumes time, attention, and a keyboard. Mobile assumes the opposite.
Before you pick features or platforms, answer one question with real rigor: what does your user need to do in a moment of low attention and high intent? Find that in your mobile browser session data. Build a one-paragraph mobile thesis. If you can't write it, you're not ready to build.
A former coworker hit me up for drinks a few weeks ago. Halfway through the first round, it became more like product therapy.
His team had been tasked with launching a mobile app for their division. It wasn't going well. The project was taking three times longer than expected. Their MVP that nobody could agree on felt bloated. And the early users? Opened it once, maybe twice, and disappeared.
I know what you’re thinking:
“Curt, it’s the year 2026. Aren’t mobile apps table stakes for most companies?”
Yes, but I've seen this before. A lot.
And yet in 2026, the setup is almost always the same. Leadership decides mobile is the move. Someone pulls up the web product in a conference room, points at the screen, and says "we basically just need this, but for mobile." The room nods. A timeline gets sketched on a whiteboard. Engineering gets pulled in.
That's where it goes wrong. Every time.
, watching established companies with real products and real users launch apps that nobody opens more than once. The bar being low doesn't mean most teams are clearing it.
There’s a meeting that happens at almost every established company the moment leadership decides to launch a mobile app. Someone pulls up their web product on a laptop, points at the screen, and says something like “we basically just need this, but for mobile.” The room nods. A timeline gets sketched. Engineering gets looped in.
That’s the point where most mobile ideas go wrong.
Porting your web experience to mobile is not a mobile strategy. It's a way of avoiding the harder question: what does mobile actually let you do that web doesn't?
Companies that skip that question ship apps that work fine and get used once, because the app doesn't do anything your website couldn't already handle. Users figure this out fast, even if they can't articulate it. The downloads trail off. The ratings drift down. The investment quietly underperforms, and nobody wants to be the one to say why.
Why the port-the-web instinct is so hard to kill
The reason this keeps happening is organizational gravity, not stupidity.
Your web product already exists. It has features that stakeholders fought for. Users who depend on them. An engineering team that knows exactly how they work. When mobile comes up, every stakeholder’s first move is to find their piece of the web product and make sure it’s in the app.
The PM who pushes back looks like they’re playing politics. The PM who doesn’t push back ships a mobile app that’s basically a slower, worse version of the website.
And the context problem is real. Web assumes someone with time, a keyboard, and actual attention to give. Mobile assumes the opposite. Short sessions. One thumb. Constant interruptions. Someone who opened your app while waiting in line and will bail the second you ask too much of them.
Those two contexts produce different products. Features that make your web experience powerful tend to make your mobile experience heavy. Flows that feel smooth on a 1440px screen feel punishing on a 390px one.
Designing mobile like it's just a smaller browser window is how you end up with something nobody opens twice.
The question that changes everything
Before you talk about features, before you pick a platform, before anyone writes a line of code, there's one question worth actually sitting with:
What does your user need to do in a moment of low attention and high intent?
That framing cuts through a lot of noise. Mobile is good at fast, specific, in-the-moment actions. Check a balance. Track an order. Book something. Capture something before the window closes.
It’s not good at complex multi-step flows, dense information, or anything that expects the user to remember where they left off.
Go look at your web analytics segmented by device. Find where users are already hitting your product on a mobile browser. Those sessions are probably a mess. That’s actually useful information. Those are the use cases people care enough to attempt even when the experience is bad.
That’s your starting point. Nail those before you try to do anything else.
What your web product tells you about your mobile opportunity
Your existing product is full of mobile signals if you know how to read them. Short mobile sessions with high completion rates? Build those flows. Long sessions with high drop-off? Leave them on web.
Look at your retention numbers by device. A gap between mobile and desktop retention is the clearest possible signal that there’s a real job to do. Parity means wait. Mixed signals usually mean someone in leadership wants this more than the users do.
The output of that audit isn't a feature list. It's a mobile thesis. One paragraph. What specific thing will your app do better than any other option, including your own website? If you can't write that paragraph, you're not ready to build.
The stakeholder conversation you need to have early
The conversation you need to have with leadership early is commercial, not philosophical. Every feature you add to v1 is something that ships later, gets tested less, and burns runway you could spend proving the core works.
A narrow app that does one thing well and keeps people coming back is worth more than a comprehensive app that nobody opens twice. And it’s a much better foundation for everything you’ll build next.
My coworker’s team had plenty of alignment. Everyone agreed on the scope, the timeline, and the launch date. What they didn’t have was a mobile thesis. That’s the difference between alignment and just having a lot of meetings.
Write the paragraph first.
App Zero is a 4-part series for product managers at established companies launching their first consumer mobile app.