Mercedes me redesign
Owners said the app didn't feel like the car. We rebuilt it around what they actually check every day: is it safe, is it ready, what's next.
+45%retention, 3–4 months after rollout
- Company
- Mercedes-Benz USA · er studio
- Role
- Product lead
- Team
- 8 people: product, design lead, engineering
- Timeline
- 2020
- Platforms
- iOS, Android, Web
- Type
- Redesign
TL;DR
- Problem
- Owners of the Mercedes me app said neither its functions nor its look matched the quality of the car. The client opened a pitch; er studio won it.
- What I did
- I led product: the metrics, the PRD, prioritization, client negotiation, QA and a staged release across iOS, Android and web, including the Mercedes-Benz Financial Services payment flows. Research and the insight were joint work with the design lead.
- Result
- 700K weekly active users and retention up 45%, measured three to four months after full rollout.

Context & problem
Mercedes me is the app a Mercedes-Benz USA owner opens to lock the car, start it, check its status, keep up with service and pay for it. It did all of that, and owners still didn’t like it.

The feedback the client had collected said that neither the functions nor the look matched the quality of the car. The team had wanted to fix this for a long time. They finally opened a pitch to outside studios, and er studio won it. I led product, with Roy Wu as design lead and an engineering team, eight of us in total, across iOS, Android and the web. The scope covered the owner app and the Mercedes-Benz Financial Services (MBFS) payment flows.
The business goals were four: retention, self-service rate, lower customer-service load and brand perception.
Discovery & insight
The research reached 50 owners, 12 of them in moderated one-hour interviews, and 400 survey responses, plus industry data on owner apps and a teardown of the competition. Owners ranked remote control (locks, start, windows) first most often, then predictive maintenance (tire pressure, service).

The interviews explained why. Most participants scrolled through menus to find maintenance status. Real-time security alerts and vehicle health were among the things they rated highest. Asked whether they checked status daily, the usual answer was to make sure the car was locked and safe.

That became the insight Roy and I built everything on: owners want peace of mind and control over simple utility. The app should match the quality of the car, and it should answer “is it okay” before it offers anything else.
HypothesisBy changing a menu-driven, utility-first home to a status-first home that surfaces each owner's next best action for Mercedes-Benz USA owners, we expect weekly active use and retention to move, because owners told us they open the app for peace of mind and control, and the current app made them dig for both.
Strategy & bets
We defined the metrics before the screens: onboarding completion, sign-up success, crash rate, retention, growth and click-through. Retention and weekly active use are the two reported here.
The bet we didn’t take: a more neutral, “Apple-like” interface. We considered it and dropped it to keep the Mercedes identity. Some of the home explorations are below.

Solution
The redesign kept the architecture owners already knew, the five tabs and the three remote actions, and rebuilt what sat on top of it: hierarchy, personalization and onboarding.



Before: the 2018 Mercedes-Benz USA app, from a public dealer image (low resolution). After: screens by Roy Wu. Drag to compare.
Three levers, applied to every screen.
Personalize. The home is built from the owner’s own vehicle and financing status. The next best action comes from the car’s condition, insurance, leasing and service, so the first thing on screen is the thing that needs doing.
Hierarchy. Status, payments and service come first. Secondary features and brand content sit below, consistently organized, instead of competing for the top of the screen.
Gamify. Lightweight progress and milestone feedback that motivates owners to complete key tasks (setup, maintenance, payments) without feeling gimmicky.









Execution
I owned the PRD, the prioritization, the negotiation with the client, QA and the release. Roy owned the design system and every screen. Engineering built it for iOS, Android and the web.
The hardest part wasn’t a feature. It was the number of rounds a brand with this bar demands on small details, and learning to treat that as the job rather than friction. We shipped in stages: about 1% of owners, then 5%, then everyone.
Validation & results
The numbers above were read three to four months after the full rollout. The staged release went to about 1% of owners, then 5%, then everyone.
Reflection
I didn’t own a car. For most of this project I had to put myself in the seat of someone who does, and understand the client’s customers before I could make calls for them. The second lesson was the brand: its tone and its strict standards are to be respected, not worked around. And if I did it again, the communication, documentation and deliverables would be nailed down at planning.