Turning a bill-checking app into somewhere people shop, in 20 markets at once.
active users on My Vodafone (FY23 Q4)
local and utility apps, each market with its own
app for every market: the goal of MVA12
Source was Vodafone's design system from 2016 to 2024. Judge the decisions on the next few slides.
For visual craft, judge Unity, the system that replaced it.


The brief asked for a seamless marketplace. The team leaned towards one merged catalogue. My worry: when a partner's order is late, people blame Vodafone.
We tested both. In the merged version, people assumed Vodafone sold and supported everything, and were surprised when told otherwise.


We wanted save for later: add your card, decide later.
But whether you can store a card before a purchase depends on the market. One flow had to work in all of them.
After adding to basket, the team wanted a You might also like sheet. I thought our catalogue was too small and it would feel pushy.
In a rapid test, people liked it and didn't find it salesy. We shipped it with one rule: the sheet only appears when there's something genuinely related.
Workshops gave every item its own delivery method: home, one of ~400 stores, or a pickup point.
people couldn't finish the delivery step in testing.
They expected one choice for the whole order. Some picked options for the wrong item.




Partners kept stock and support details in our CMS. When they couldn't fulfil an order, the fault was theirs, but it happened inside our app.









The legacy payment integration couldn't support it without deeper re-architecture. Half the room wanted to cut scope, half wanted to wait.
Build native payment, launch a thinner shop.
Losing core Marketplace hurt more than a temporary redirect.Keep everything, ship when payment is ready.
No fix date in sight, so the launch would slip indefinitely.Use the stable web payment for now.
Our pick. Launched on time, full scope.







































Rewards existed, but fewer than 10% engaged with it. I proposed small games with different rhythms.
engagement with Rewards, plus more frequent app visits
average session length in the first year. Some of it is novelty; we're watching whether it holds.
less engineering time spent on maintenance, combined across markets
markets live on MVA12: Italy, Ireland, Portugal, Spain, Albania, Türkiye
In testing, people saw Marketplace as a perk of being a customer, not an Amazon competitor.
Task success across browsing, product and payment was very high, because it behaved like shops people already knew.
The late-2023 downturn hit. Partners paused, inflation cut demand, and Vodafone sold its Italian and Spanish businesses. Marketplace launched only where demand held.
Bring legal and compliance in from the first flow, not after it.
Our first checkout was drawn without payment regulation in mind. PSD2 and PCI DSS only shaped it after review. Collaboration outside the product team matters as much as inside it.
Vodafone's new design system, 2024–2026. First, the showreel we made for its launch.
Germany had Brix, the UK and Ireland had Source, Spain had Resource, Hungary had Aurora. Patterns drifted, and every team rebuilt the same button.
One system for every market. Hence the name.
My part: components, icons, illustrations, and the accessibility process towards the 2025 EAA.






Same structure and decisions. New type, spacing, colour and components.
Designed in Unity. It reached the live app after I left Vodafone, so these are my redesigns, not shipped screens.
performance improvement, with less design debt
better Customer Effort Score
custom illustrations
compliance for the 2025 European Accessibility Act
On accessibility I set up audits with specialist agencies, worked with legal, taught developers what accessible build means, and wrote the process and guidelines the company now uses.
A tracking app two of us built on nights and weekends, and grew with £0 on ads.
During Covid, prices rose far faster than the discounts. And the inbox didn't help.
sale emails in January alone. None told me when to buy.
They weren't exploring. They wanted a fast answer to one question: did it work?
Websites change constantly, so rigid scrapers break. We built change detection instead: point at what matters, get told when it changes.
Inside, a change tracker. Outside, a price tracker, because that's who would pay.
Before building properly, a landing page asked one question: can we explain this well enough for someone to leave their email?
waitlist sign-ups. Not viral, but enough signal.
A lifetime price for early sign-ups: a thank-you, and a reason to commit.






































Paste a link or share from the browser, tap the price on the live page, and the app watches it from then on.
I kept testing beyond the screens: how the store page sells the app, and when to ask people to pay.
conversion with plain App Store screenshots
subscribers with the paywall after onboarding







spent on ads
views on one YouTube feature
The hard part wasn't the UI. It was tracking reliably across thousands of websites. Two platforms would have halved our speed on the thing that mattered.
People kept asking to pay per item. Alongside the plans, we added pay-as-you-go tracking credits.
of revenue by October 2025, and growing
Also after launch: Normal, Extended and Ultra tracking for tricky pages, and follower tracking that brought in creators.
in App Store proceeds on iOS
conversion rate
iOS downloads, 2023 to 2025
Android launched later and passed iOS on users, but earned less. Most of its growth was in price-sensitive markets like Türkiye, Mexico and South Africa.
Still to improve: crash rate, the number of ratings and reviews, and a 2% conversion dip since July.
Start with fewer assumptions, and trust users sooner.
My first onboarding over-explained. People understood the product much faster than I expected.
In November 2025 I sold my stake, and Shervin carried on running it on his own.
Research showed people skimming, and a big drop at the permissions step. We made it visual, shorter, asked for permissions in context, and added a reward at the end.
completion in the A/B test, with more push opt-ins
Your browser blocked the notes window. Allow pop-ups for claude.ai, or open this link in a separate window: