Vodafoners is an employee super-app our founder, Gabriel, led end to end as Lead Product Designer at _VOIS for Vodafone. It took around 6,000 employees off six-plus disconnected tools, gave them one role-aware home and the organisation’s first digital channel for wellbeing. It shipped to production, and they use it every day.
Around six thousand employees were spread across six-plus disconnected systems (HR, payroll, bookings, PDFs, email) with no single home. There was no one place to answer “what do I need today”, and nothing at all for wellbeing.
Two surveys made the problem concrete. A wide round of about 1,000 people showed what was happening: task frequency, satisfaction and where usability broke at scale. A focused round of about 100 people explained why, in their own words. One line kept coming back: “I never know what my benefits actually are.”
If nothing changed, people kept hunting across tools, benefits stayed invisible and wellbeing had no voice.
The problem, in numbers
Gabriel owned the design from the first research to developer handoff and did the core design work. The design system was the multiplier: once the patterns were set, new modules could be built quickly and consistently without reopening every decision. Constraints: a hybrid iOS and Android build, the Egyptian market (right-to-left Arabic) and a fixed design-system vocabulary.
What we owned
What the team did
Putting 33 services on one home screen would recreate the overwhelm the app was meant to fix.
Options considered
A full grid, an alphabetical menu, or a grouped and personalised home.
The choice
Six scannable groups plus a searchable menu, with the home showing what is relevant to you.
Trade-off accepted
More upfront IA and personalisation logic, in exchange for a home that answers “what do I need today”.
The hybrid build first forced an awkward double login that added friction every session.
Options considered
Accept the double login, rework SSO completely, or unlock with biometrics.
The choice
Face ID and fingerprint, following each platform’s native pattern.
Trade-off accepted
Platform-specific handling to maintain, in exchange for high security with almost no friction.
The design system pointed search toward a pop-up tray instead of a separate results screen.
Options considered
A full results screen, or an in-context tray.
The choice
A tray for the service directory, with a fuller filter pattern kept for the store-style Installments catalogue.
Trade-off accepted
Less room for rich filtering in search: right for a directory of known services, not for a catalogue.
The client’s trust grew mid-project and they wanted more features without moving the timeline.
Options considered
Bespoke one-off screens, or a tokenised system with a component library.
The choice
Tokenised colour, type and spacing with a reusable component library.
Trade-off accepted
A slower start, but it absorbed five added features (Smart Parking, Mood Tracker and more) and a full dark theme as a re-map, not a rebuild.
The app was built and shipped, 33 services moved into one home, and the client trusted the work enough to expand the scope mid-flight. The next step would be measuring adoption and task success after launch, so the next version is driven by behaviour, not only by pre-launch research.
Want every detail?
The full case study has the research, flows and every screen.
Have a similar challenge? Let's talk.
Book a 30-minute callSince 2004, across healthcare, telecom, e-commerce, retail and industry.
Have a product that should be easier to use?
Tell us what you are working on. We reply within one working day, and the first call is free and without obligation.
or write to us at office@g2fdesign.com
