Amplitude
Three-week sprint to ship Amplitude, a mobility training app for iOS and Android, paired with a SaaS CRM admin and a launch landing page, under hard launch pressure.
What we had to solve
Three weeks to launch
Design, product decisions and handoff had to stay ruthless: only what unblocked shipping, no nice-to-haves that would slip the store date.
Technical friction in the build
Implementation hit real blockers, native constraints, unstable flows, last-mile bugs. Design had to adapt screens and specs to what engineering could actually ship in time.
In-app purchase complexity
Subscriptions, paywalls and restore flows had to feel clear for users while surviving App Store / Play billing rules, edge cases and incomplete purchase states.
How we got there
- 01
Scope & freeze
Locked an MVP surface: home, methods library, calendar, workout player, progress, plus the CRM overview needed to operate content and subscriptions at launch.
- 02
App + CRM system
Dark-mode product UI for mobile/tablet and a light admin dashboard for metrics, subscribers and content ops, one product language across both.
- 03
IAP & edge cases
Mapped purchase, restore and failure states with engineering; simplified paywall copy and recovery paths so billing issues wouldn’t kill first-session trust.
- 04
Landing & store ship
Built the launch landing to convert early traffic, aligned store assets, and closed the loop so web → app → CRM could go live together.
What changed
Amplitude launched on time: a polished mobility app experience, an operable SaaS back-office, and a public landing that connects acquisition to the stores.