Home > Projects > Network API Portfolio

Network API Portfolio.

Network API Portfolio

A CAMARA-compliant developer hub where partners discover, understand and request access to network APIs. Our founder, Gabriel, led and created the design as Lead UX/UI Designer at _VOIS for Vodafone Group Commercial, as a working coded prototype ready to scale across 40+ markets.

1 / 2

Back to Work

Date 2026

Made at _VOIS for Vodafone Group Commercial

Category Developer Portal · SharePoint & Eloqua

Tags UX/UI, B2B, API, Vodafone, Developer Portal

Web · Developer portalCAMARA open gateway_VOIS for Vodafone Group Commercial

From weeks of manual onboarding to one guided path.

Network API Portfolio is a CAMARA-compliant developer hub where Vodafone partners discover, understand and request access to network APIs such as SIM Swap, Number Verify and Age Verify. Our founder, Gabriel, led and created its design as Lead UX/UI Designer at _VOIS for Vodafone Group Commercial. It was built as a working coded prototype, ready to scale across 40+ markets.

Role: Lead UX/UI DesignerResearch to coded prototype
Platform: Web developer portalPublic site + partner portal
Standard: CAMARA open gatewayMicrosoft SSO
Scale: 40+ marketsNo per-market rebuild

Read the full case study

01 Context & stakes

The front door to Vodafone’s network was missing.

Network APIs let partners build things only a carrier can offer: verifying a phone number silently, detecting a fresh SIM swap to stop account takeover, confirming a user’s age without exposing personal data. The technology existed. The way in did not.

Every API had its own documentation, its own authentication and its own way in, and getting access was manual: weeks of back-and-forth before a partner could even start.

“I can’t even tell which APIs I’m allowed to use.” A partner developer, in discovery.

What was broken

No single place to discover, onboard or test APIs
Each API team kept its own docs and auth patterns
Manual provisioning at every step
Weeks just to get access, and no view of usage

Network API Portfolio: The public hub: value proposition, partner logos, the API catalogue and a path from discovery to production. Scroll inside the frame. — The public hub: value proposition, partner logos, the API catalogue and a path from discovery to production. Scroll inside the frame.

02 Role & boundaries

Research, architecture and a portal that behaves like the product.

Gabriel led the end-to-end design: workshops with Vodafone product managers, partner developers and API operations teams; the dual-portal information architecture; CAMARA-aligned patterns; the design system; and the guided flows that replace weeks of coordination. The main deliverable is a working coded prototype built in Figma Make, with real navigation, real states and a light and dark theme.

What we owned

Stakeholder research and developer experience
Information architecture and the dual-access model
Public site, partner portal and admin dashboard UI
Email templates and document standardisation
Design system and coded prototyping in Figma Make

Who shaped it

Vodafone product managers: commercial model and roadmap
Partner developers: where the friction really lived
API operations teams: who carried the manual onboarding
The business partner and product owner: priorities and sign-off

Network API Portfolio: Playbook: how it works, the delivery model and the reference architecture. — Playbook: how it works, the delivery model and the reference architecture.

Network API Portfolio: API spec: endpoints, methods, auth and errors, with a clear route to request access. — API spec: endpoints, methods, auth and errors, with a clear route to request access.

03 Key decisions & trade-offs

Four decisions that made it one product.

One portal or two? Dual entry.

Partners and internal developers need very different navigation and permissions.

Options considered

One product for everyone (confusing for both), or two separate products (double the design, code and drift).

The choice

One design system and auth layer with two entry points and permission scopes: same components, different navigation and access.

Trade-off accepted

More thought in the permission model, but each audience gets a fit-for-purpose experience without forking the product.

CAMARA as a design constraint, from day one

Inconsistent docs and auth across APIs killed trust and speed.

Options considered

Treat compliance as a late check, or design every schema, doc and flow around it.

The choice

Align every API’s specification, documentation and onboarding to CAMARA, so learning one API means you already know the next.

Trade-off accepted

Less freedom per API, in exchange for a predictable portal that deploys across markets without rebuilds.

Entitlement is the organising idea

Partners first need to know what they are allowed to use.

Options considered

Hide contract status in a menu, or make it the loudest signal on every card.

The choice

Trade-off accepted

Denser cards to design, but no guessing about access.

A coded prototype, not static screens

For a developer tool, credibility comes from something that behaves.

Options considered

Static mockups (fast, but can’t prove flow or state), or a working build.

The choice

A coded prototype in Figma Make with real navigation, loading and entitlement states, and light and dark themes.

Trade-off accepted

More build effort up front; stakeholders and testers could actually use it, not just look at it.

Network API Portfolio: Dashboard: contracted APIs with usage against quota, activity and next steps. — Dashboard: contracted APIs with usage against quota, activity and next steps.

Network API Portfolio: Catalogue: every API marked active, contracted or available to add. — Catalogue: every API marked active, contracted or available to add.

04 Outcome & evidence

Measurable gains in developer experience.

64%Faster task completion than the legacy toolset, in usability testing

3×Faster onboarding: weeks of coordination down to days

40+Countries it can scale to without a rebuild

0Support tickets needed to get started

A unified hub replaced scattered docs and weeks of manual coordination. The gains were measured by the programme through usability testing with partner developers across three real integration scenarios, and shared by the project’s business partner.

Want every detail?

The full case study has the research, flows and every screen.

Read the full case study

Have a similar challenge? Let's talk.

Book a 30-minute call