GABRIEL RADATOVICS
CAMARA DEVELOPER HUB · WEB · VODAFONE GROUP COMMERCIAL

Network API Portfolio

A CAMARA-compliant developer hub that lets Vodafone partners discover, understand and request access to network APIs — SIM Swap, Number Verify, Age Verify and more — through one consistent hub, instead of weeks of manual back-and-forth. The major build is a working, coded prototype produced in Figma Make. Designed to scale across Vodafone's 40+ country footprint.

PLATFORMWeb developer portal
ROLELead UX / UI Designer
STANDARDCAMARA open gateway
SCALE40+ markets
developer.vodafone.com
Network API Portfolio — public developer hub landing page
PUBLIC HUB

The Eloqua public landing page — where prospective partners discover Vodafone's network APIs.

00
CONTEXT & ROLE

The Front Door to
Vodafone's Network

Vodafone is exposing its network as a set of programmable APIs — the CAMARA open-gateway initiative. But a capability is only as good as the developer experience around it. My mandate was to design the hub where partners actually find, understand, buy and integrate those APIs.

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 fraud, 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 auth, its own way in, and getting access was manual — weeks of back-and-forth before a partner could even start.

I led the end-to-end design of the developer hub: stakeholder research, the dual-portal information architecture, CAMARA-aligned patterns, the design system, and the guided flows that replace weeks of manual coordination with a clear path to access. The major build is a working coded prototype in Figma Make — real navigation, real states, real data — with foundational parts designed in Figma.

CLIENT
Vodafone Group Commercial
PRODUCT
Network API Portfolio & Partner Portal
MY ROLE
Lead UX / UI Designer
PLATFORM
Responsive web · public + authenticated
STANDARD
CAMARA open-gateway compliant
DELIVERY
Coded prototype (Figma Make) + Figma
SCALE
Designed for 40+ Vodafone markets
WHAT I OWNED
Stakeholder ResearchDeveloper Experience (DX)Information Architecture Dual-Access Model · SharePoint + EloquaCross-Platform Visual Identity Partner Portal & Admin UIAnalytics DashboardEmail Templates Document StandardisationDesign SystemCoded Prototyping · Figma Make Documentation UX
01
THE CHALLENGE

No Unified Way Into
Vodafone's APIs

Partners wanted to build on Vodafone's network, but there was no single place to discover, onboard or test. Every integration point added weeks of manual work — and the developer experience was inconsistent enough to lose partners before they started.

Fragmented Access

No single place to discover, onboard or test APIs. Every new integration required manual support intervention — and time partners didn't have.

No Standardisation

Each API team maintained its own docs. No shared auth patterns, no consistent onboarding, no unified developer experience — so nothing felt like one product.

Weeks of Manual Onboarding

Getting access meant human coordination at every step. The delay itself was the barrier — momentum died in the queue.

DESIGN OBJECTIVE

Design a CAMARA-compliant developer hub that unifies all of Vodafone's network APIs — so prospective partners can discover and understand them on a public site, and contracted partners can manage everything they've been granted in one secure, personalised portal.

02
DISCOVERY & RESEARCH

Design for Developers
Means Ask Developers

A developer portal fails quietly if it's designed for the business and not the builder. I ran workshops across three very different audiences to map real pain and define what “good” meant for each.

WHO I TALKED TO
PM

Vodafone product managers

To understand the commercial model, the API roadmap and what success looked like for the business.
DEV

Partner developers

The people who actually integrate — where the friction really lived, from first docs to production access.
OPS

API operations teams

Who carried the manual onboarding burden today, and what could safely be streamlined.
3

Scenarios tested

Three real integration scenarios later used to benchmark task completion against the legacy toolset.
WHAT DISCOVERY TOLD US
INSIGHT 01

“I can't even tell which APIs I'm allowed to use.”

DESIGN IMPLICATION

Discovery and entitlement were invisible. This drove a public catalogue anyone can browse, and an authenticated portal that shows exactly what your organisation has contracted.

INSIGHT 02

“Every API's docs read like a different company wrote them.”

DESIGN IMPLICATION

Inconsistency killed trust and speed. CAMARA alignment plus one documentation pattern made every API feel like part of one predictable platform.

INSIGHT 03

“Waiting weeks just to get access kills the project before it starts.”

DESIGN IMPLICATION

Manual coordination was the real barrier. A guided Request Access flow and a clear commercial path removed the weeks-long queue.

INSIGHT 04

“Our IT controls access — don't make me manage yet another login.”

DESIGN IMPLICATION

Enterprise access is org-governed. Sign-in became Microsoft SSO, with entitlements fetched from the organisation — no new credentials to manage.

03
THREE USER TYPES

One Portal, Three
Very Different Jobs

Straight from the brief, the portal served three audiences with very different needs and permission levels — two external, one internal — while still feeling like one product built on one system.

CS
Contracted Supplier
External · Already a partner
GOALS
  • Quick access to docs for APIs they own
  • Discover new APIs they could add
  • See usage, files and support in one place
FRUSTRATIONS
  • Documentation scattered across sources
  • No single, personalised home
  • Unclear what else is available to them
LIVES IN
Active APIsDocsPortal
PP
Prospective Partner
External · Pre-contract
GOALS
  • Understand what APIs Vodafone offers
  • Judge fit at a high level, fast
  • An easy way to make contact
FRUSTRATIONS
  • No public place to discover offerings
  • Hard to tell what's even possible
  • Unclear how to start a conversation
LIVES IN
Public siteContact
IA
Internal Admin
Vodafone · Non-technical
GOALS
  • Manage partners; assign APIs to each
  • Upload documents and edit content
  • See analytics — activity and downloads
FRUSTRATIONS
  • Managing access in spreadsheets & email
  • No non-technical way to publish content
  • No visibility of who uses what
LIVES IN
Partner mgmtAnalytics
04
INFORMATION ARCHITECTURE · DUAL-ACCESS ECOSYSTEM

Public to Discover,
Secure to Manage

The core structural decision, set by the brief: a dual-access ecosystem across two very different platforms — a public pre-contract site on Eloqua for prospective partners, and a secure Contracted Supplier Portal on SharePoint for existing ones. My job was to make them feel like one product, with a single visual identity spanning both.

ELOQUA · PUBLIC, PRE-CONTRACT

Open to anyone: the API portfolio, a per-API pre-contract page for each capability, and clear CTAs — Contact Us and Partner Login. Its job is to convince and inform before a contract exists.

SHAREPOINT · SECURE PORTAL

Behind SSO, a personalised home split into Active APIs (contracted) and Available APIs (not yet) — with each API's documentation, usage and support scoped to exactly what the partner has been assigned.

THE ORGANISING MECHANIC · ACTIVE vs AVAILABLE

Active APIs — contracted

The APIs a partner already owns sit up top as live tiles: open the documentation, track usage, get support. This is their working home.

Available APIs — not yet

Everything else shows as a discovery tile — a pre-contract detail page and a clear “Request Access” route that hands off to their account team.

Driven by assignment

An internal admin assigns specific APIs to each partner; that single control decides what appears as Active vs Available on every partner's home.

THE INTEGRATION ARCHITECTURE · HOW A CALL REACHES THE NETWORK
Channel Partner's Application
The partner's product, calling Vodafone network APIs
↓
Developer Marketplace / Partner Portal
Discovery, documentation, access & entitlements — the layer I designed
↓
Network API Integration Layer (NAIL) & Entitlement Server
Standardised access, auth and entitlements across APIs
↓
NaaP · Local Market Core Network
Network-as-a-Platform integration into each market's core

Understanding this stack shaped the UX: the portal had to hide enormous back-end complexity — NAIL, the Entitlement Server, per-market core networks — behind a surface a partner could move through in minutes.

05
CAMARA · A CONSTRAINT, NOT AN AFTERTHOUGHT

Compliance as a
Design Advantage

CAMARA is the industry open-gateway standard for network APIs. I treated it as a design constraint from the first IA decision — and it paid back as consistency: aligned schemas, documentation formats and onboarding flows that made the portal predictable for every audience.

Aligned schemas & docs

Every API's specification, documentation format and onboarding flow was aligned to CAMARA — so learning one API means you already understand the next.

Interoperable across markets

Standardisation is what makes a single portal design deployable across the full Vodafone Group footprint without market-specific rebuilds.

Predictable for partners

Consistent auth patterns and error handling turn “integrate our API” into a known quantity — the single biggest driver of developer trust.

06
THE SOLUTION

One Portal. Every
API. Zero Friction.

A CAMARA-compliant developer hub with two front doors: a public site where prospective partners discover and request APIs, and a secure portal where contracted partners manage everything they've been granted — no scattered docs, no manual runaround, no guesswork about what they can use.

“Build once. Integrate once. Scale everywhere — the whole point of a network platform, made real in the developer experience.”

01

Unified Discovery

One catalogue for every network API — SIM Swap, Number Verify, Age Verify and more — grouped so partners find the right capability fast.

02

Guided Onboarding

A clear path from discovering an API to requesting access — with the account team looped in only where a contract actually needs it.

03

Governed, Entitlement-Aware

Sign in with Microsoft SSO; the portal shows exactly what your organisation has contracted — contracted vs available, always clear.

FROM DISCOVERY TO ACCESS · THE PARTNER PATH
01

Explore the catalogue

Browse the public API catalogue and read consistent, CAMARA-aligned specs.

→
02

Onboard your team

Sign in with Microsoft SSO; entitlements load for your organisation.

→
03

Commercial agreement

Contract the APIs you need; access is governed and auditable.

→
04

Work in the portal

Documentation, usage and support for every API you've been granted.

07
DESIGN SYSTEM & CODED PROTOTYPE

Designed as a System,
Delivered as Working Code

Both portals are assembled from one component library on a shared token layer — which is what lets a public marketing page and a dense data dashboard feel like one product. The major deliverable isn't a static mockup: it's a working, coded prototype built in Figma Make, with real navigation, live-feeling states and a proper light/dark theme. The look and feel is anchored to Vodafone's own developer.vodafone.com — the reference the client pointed to.

WHAT I DESIGNED · ACROSS TWO PLATFORMS, ONE IDENTITY

Eloqua public site

Landing page showcasing the API portfolio, a pre-contract detail template per API, and the HTML email templates for the automated confirmations.

SharePoint partner portal

Personalised homepage (Active vs Available), a post-contract API detail page — documentation file lists with type icons, tabs & accordions — and a non-contract detail template.

Admin dashboard

Non-technical UIs for partner management (list views, add/edit modals), product & content management, and an analytics dashboard — activity, downloads, login frequency.

Document standardisation

Reviewed existing partner documents (Word / PPT / PDF) and proposed a standardised, branded structure that reads cleanly on the web.

COLOUR TOKENS · DARK-FIRST DEVELOPER UI
Vodafone Red
#E60000
Portal Base
#0D0D0D
Surface
#1A1A1A
Active / OK
#28C840
Quota warn
#FEBC2E
On-dark text
#FFFFFF

Status colour is semantic, not decorative — active, contracted, quota-near and error each map to a token, so a partner reads a dashboard's health at a glance. Type pairs DM Sans with JetBrains Mono for a clean developer-tool feel.

WHY A CODED PROTOTYPE (FIGMA MAKE)
Static screens, or a working build?
STATIC

Fast to make, but can't prove flow, state, theming or how a dense dashboard actually feels to use.

CODED · FIGMA MAKE

Real navigation between public site and portal, real loading/entitlement states, real light/dark — testable like the product.

Chosen: a coded prototype. For a developer tool, credibility comes from something that behaves — stakeholders and testers could actually use it, not just look at it.

TOOLING, HONESTLY

The earliest concepts were explored with AI (Claude); from there I designed and built the working coded prototype in Figma Make. The tooling accelerated production — the research, the dual-portal IA, the CAMARA decisions and the developer experience are mine.

08
THE PUBLIC HUB · REAL SCREENS

Convince, Then
Document

The public site does two jobs: sell the platform, and prove it's technically credible. These are real screens from the coded prototype. Click any to view the full page.

LANDING · “BUILD ONCE. INTEGRATE ONCE. SCALE EVERYWHERE.”
developer.vodafone.com
Public developer hub landing — value proposition, partner logos, discovery-to-production path
LANDING

A clear value proposition, recognised partner logos, an “explore integration options” catalogue and a discovery-to-production path — the case for building on Vodafone, before anyone logs in.

TECHNICAL DEPTH · PLAYBOOK & SPECIFICATION
/integration-options/it-data/playbook
Technical Playbook — integration guidance and architecture diagram
PLAYBOOK

End-to-end integration guidance: how-it-works, delivery model and the reference architecture, straight from the API summary deck.

/integration-options/it-data/spec
API Specification page — endpoints, methods, CAMARA compliance notes, code
API SPEC

Category, endpoints, methods, auth and error handling — with a downloadable PDF guide and a clear route to request access.

09
DEEP DIVE · THE PARTNER PORTAL

Where Partners
Actually Build

Behind Microsoft SSO sits the authenticated portal — the core of the product. It answers three questions instantly: what can I use, how much have I used, and what do I do next.

SIGN IN · ORG-GOVERNED, NO NEW CREDENTIALS
/login
Partner Portal login — Continue with Microsoft SSO
LOGIN

“Continue with Microsoft SSO.” Access is controlled by the partner's own organisation — no extra account to manage.

/auth/callback
SSO transition — verifying credentials and fetching API entitlements
ENTITLEMENTS

A designed transition state — verifying credentials, fetching API entitlements — so the wait tells a story instead of showing a spinner.

DASHBOARD · WHAT YOU HAVE, AT A GLANCE
/dashboard
Partner Portal dashboard — contracted APIs with live usage and quota bars
DASHBOARD

A personalised home: contracted APIs (SIM Swap, Number Verify 2.0, SMS Hub) with live usage against quota, recent activity, upcoming maintenance and one-tap routes to docs, status and support.

INTEGRATION OPTIONS · CONTRACTED vs AVAILABLE
/integration-options
Integration Options — APIs grouped by delivery technology, contracted and not-contracted states
CATALOGUE

APIs grouped by how they're delivered — local-market IT via NAIL, low-friction auth via the Entitlement Server, advanced network tech via NaaP — each clearly marked active, contracted or available to add.

KEY DESIGN DECISIONS · THE DASHBOARD

Entitlement is the organising idea

Contracted vs available is the first thing a partner needs to know — so it's the loudest signal on every API card, never buried in a menu.

Usage you can trust

Live call counts against quota, with a quota-near warning colour, turn an abstract subscription into something a developer can actually manage.

Next action always present

Every surface offers the obvious next step — view docs, add an API, contact your account team — so the portal moves work forward.

10
KEY DECISIONS & TRADE-OFFS

One Portal or Two?

The defining architectural question of the whole project — and the one that, answered well, made everything downstream simpler.

Build one unified product, or two distinct ones for partners and internal developers?
OPTION A · ONE PRODUCT

Simplest to maintain, but forces two very different audiences and permission models through the same door — confusing for both.

OPTION B · TWO PRODUCTS

Cleanest fit per audience, but doubles the design, the codebase and the drift — two things to keep in sync forever.

CHOSEN · DUAL-ENTRY

One design system and auth layer; two entry points and permission scopes. Same components and tokens, different navigation and access.

The dual-entry model gave each audience a fit-for-purpose experience without forking the product. CAMARA compliance was held as a design constraint throughout — which, far from limiting the work, made the portal more consistent and predictable for every developer audience.

11
IMPACT

Measurable Developer
Experience Gains

A unified hub replaced scattered docs and weeks of manual coordination — validated with real partner developers, and architected to scale across Vodafone's global footprint.

64%
Faster task completion
vs the legacy toolset, in usability testing
3×
Faster onboarding
weeks of manual coordination → days via a guided flow
40+
Countries it can scale to
CAMARA architecture, no per-market rebuild
0
Support tickets to start
a guided Request Access flow, not a queue

Performance figures were measured by the programme and shared with me by the project's business partner / product owner.

Validated, Not Assumed

A 64% reduction in task-completion time versus the legacy toolset — measured through usability testing with partner developers across three real integration scenarios.

Weeks to Days

Partners discover an API and request access through one guided flow — no support ticket, no chasing — collapsing onboarding from weeks to days.

Built to Scale Globally

A CAMARA-compliant architecture means one portal design deploys across 40+ Vodafone markets — no market-specific rebuild required.

12
THE TRANSFORMATION

From a Manual Queue
to a Guided Path

The clearest measure of the work is what a partner developer's first week looks like — before, and after.

BEFORE

A manual queue

  • No single place to discover APIs
  • Different docs & auth for every API
  • Manual provisioning at every step
  • Weeks just to get access
  • No visibility of usage or entitlement
  • Support tickets to do anything
AFTER · WITH THE PORTAL

Guided access, in days

  • One CAMARA-compliant catalogue
  • Consistent docs, specs & auth patterns
  • A guided Request Access flow
  • Days to access, not weeks
  • Live usage, quota & entitlement clarity
  • Zero tickets to get started
13
REFLECTION

What I'd Carry Forward

Lessons from designing a developer product for three audiences at Group scale.

Design the developer's critical path first

The win was collapsing weeks of manual access into one guided flow. For a partner tool, time-to-access matters more than any screen's polish.

A coded prototype tells the truth

Building it in Figma Make surfaced flow and state problems a static mockup would have hidden — and made stakeholder buy-in easy.

Standards are a design gift

Treating CAMARA as a constraint from day one produced consistency I'd otherwise have had to fight for, screen by screen.

Dual-entry beats “one or two”

Sharing one system across two entry points served every audience without doubling the product — a pattern I'll reuse.