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.
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.



