Maropost · Mobile
One app, from first open to daily operations
Maropost had two mobile apps: marketing (dashboards and reports) and commerce (fulfilment and shipping labels). Teams wanted campaigns and shop in one place. I owned the product design through high-fidelity prototyping. The concept was not launched.
Two apps. Two mental models.
I started with the frustrations: two apps, no single path from a campaign to an order. Interviews and an all-rounder persona framed who had to do both jobs. I worked with Marketing Cloud product owners, customer success, a business analyst, and engineering.
This case study covers the product design through high-fidelity prototyping. The concept did not progress to launch.
Status
PrototypeDesigned through hi-fi. Not launched.
The prototype covered onboarding; Google, Salesforce, and Apple sign-in; a six-digit MFA flow; and the unified marketing and commerce shell. The value is the system and the journeys.
The first-run experience had to earn the login
An early flow mapped four swipe screens into login. Hi-fi tightened that to three onboarding screens – Quick as your fingertips, Create a personalized experience, Perfect for last minute changes – then Get started.
Login is email and password, or Google, Salesforce, or Apple. There is no self-service sign-up; users without a Maropost account are directed to contact their administrator. MFA is a six-digit code sent to a masked number, with empty, keypad, and filled states specified.
The map before the screens
The earlier journey used a four-step progress mark (welcome, last-minute changes, data at your fingertips, the important parts) into the login screen. The high-fidelity design kept the core jobs and removed one step to shorten the first-run experience.
