A 2.6-star app in a world where digital ordering is the business.
The Jack in the Box app had a 2.6-star App Store rating. Guests were leaving reviews that read like complaints to a customer service hotline — broken login, loyalty offers that didn't apply correctly, a checkout flow that lost orders mid-transaction. For a brand trying to grow digital order mix, the app wasn't just underperforming. It was actively driving guests away.
Digital ordering had become a primary revenue channel. The gap between the brand's aspirations for digital and the actual guest experience was significant — and visible. Every one-star review was a guest who ordered at the drive-thru instead, or worse, chose a competitor.
"The app was broken in ways that mattered. Not edge cases — the core jobs guests needed to do. Sign in. Find a deal. Add it to their bag. Check out. These were failing regularly."
Finding the signal in thousands of one-star reviews.
The temptation in a situation like this is to rebuild everything. New platform, new stack, clean slate. That instinct is almost always wrong — and expensive. The real challenge was figuring out exactly what was broken and why, so we could fix the right things without disrupting what was working.
We used a Jobs To Be Done framework to cut through the noise. Instead of reacting to individual complaints, we asked: what are guests actually trying to accomplish — and where are we failing them? Four core jobs emerged from the data.
Four jobs. That became the roadmap. We didn't rebuild everything — we rebuilt what was getting in the way of those four things. Everything else stayed.
A disciplined rebuild — not a platform migration.
The most important strategic decision was what we chose not to do. We decoupled the frontend rebuild from the backend systems. Guests touch the frontend — they don't care about the plumbing. We focused there first and left the backend intact. That single decision is what made an 8-month timeline possible.
We wireframed everything in Balsamiq first. Lo-fi, no polish, just flows. Because if the logic is broken, making it pretty doesn't fix anything. We got the flows right before we wrote a line of production code.
The onboarding and identity flows were rebuilt from scratch — simplified, tested, and pressure-tested again. The loyalty redemption experience was completely rethought so offers and items worked together instead of as two separate systems. The menu was restructured around how guests actually think about food, not how the back-end categorized it. Checkout was rebuilt to be resilient — no more lost orders.
"Six months to rebuild. Two months of pressure testing before we shipped. A lot of teams sprint to launch and hope for the best. We didn't. We stress tested, found the edge cases, and shipped with confidence."
The rebuild required tight alignment across Product, Engineering, Design, Marketing, and Operations. Loyalty integrations, payment stack dependencies, and franchise-facing systems all had to move together. The cross-functional coordination was as hard as the product work itself.
A 4.8-star app — and the business outcomes to match.
The rating improvement was the headline, but the real story was in what drove it. Guests weren't just rating the app higher — they were completing orders, redeeming offers, and coming back.
The lesson wasn't complicated: listen to your users, use a framework to organize what you hear, trust your design instincts, and respect the craft of execution. The app was broken. We fixed it. And we did it in eight months because we were disciplined about what we touched and intentional about how we worked.