Warranty Keeper
An end-to-end redesign of a cloud app for storing warranties and receipts, shipped on iOS and Android.
Customer problem
Warranty Keeper had been running for five years with tens of thousands of users. They came for one thing: proof of purchase that would not be lost, damaged, or unfindable at the moment they needed it.
Three problems stood between them and that. The upload process ran long with no sign of how many steps were left, so people abandoned it. Nothing on the screen had a clear order or alignment, so it was hard to tell one element from another. And too much of the information sat several taps deeper than it needed to.
The brief
Give the app a clear navigation hierarchy and an intuitive experience without changing what it does.
Two numbers to move: onboarding friction for new customers, and taps for existing ones.
My own goals sat alongside that: simplify uploading by removing steps, raise engagement with navigation and calls to action that shorten time-to-value, and add enough flexibility for people to organise things their own way. I also wanted to own every role on a product from zero to one, from research through to interface.
Research
I worked from design for delight
. Study the in-app journey, the funnel and the
behaviour patterns first. Generate a wide set of ideas against what that turns up. Then
narrow to the ones worth testing with beta groups and A/B.
The reviews. I went through the Play Store listing first. At 10K+ downloads there were not many reviews to read, but the ones there were told me plenty about where people got stuck.
The competition. I compared Warranty Keeper against Keepe Warranty, Expired, Assure and BillsBox to find where it was genuinely stronger and where it was behind. I presented the result to the founder so the design decisions and product strategy could be argued about with evidence, and leaned on visuals to keep the report readable.
User flows
The flow maps what someone has to do to get the app working and reach the first thing of value. The site map behind it sets out the structure those flows run through.
Wireframing each of those flows in detail is where the navigation got simple, and where the onboarding sequence started to take shape.
Design system
Two ideas had to come across before anything else: this is secure, and it is in the cloud. The mood boards chased both, and the palette that came out of them carries that reassurance into every screen.
Solution
Three features carry the app, and each one answers a pain point directly.
- Upload an item. Store the warranty for anything you own, in as few steps as the task allows.
- Search. A search bar, so pulling one document out of a full account takes a moment.
- Custom categories. Room to organise documents the way they are actually thought about.
The final screens keep only the components that carry a real need, which is what the visual iterations kept converging on.
What I learned
The discipline this project taught me was restraint. Warranty Keeper does one thing, and every idea had to justify itself against that one thing before it earned a screen.
There is more I would build around saving and organising warranties. None of it is worth having if it pulls the app away from the reason people opened it.
Shipped and live on the App Store and Google Play.