Case study · Arya.ai

Apex — API Platform

Arya.ai's API hub let people try its AI APIs - but trying one meant a confusing subscribe-and-login loop, hidden documentation and credits locked to a single API. I redesigned it into Apex: one self-serve platform where trying an API takes a click.

Role
Sr. UI/UX designer
Timeline
2 months
Company
Arya.ai
Tools
Figma
Team
Me (the only designer + researcher), 1 frontend + 1 backend developer, my manager (growth head) and the VP of engineering

12/15users found the new try-the-API journey easy and quick

Visit Arya.ai (opens in a new tab)
01 · Context

Where it started: the API hub

The API hub (ver. 2.0) lives on Arya.ai's website. Users come to try individual AI APIs - KYC extraction, face verification, deepfake detection and 80+ more - and then use them.

  • Every API has an About, a Try the API and a Documentation tab.
  • Trying needs credits, and credits were bought per API.
  • I had designed the hub's look - playful, matching our vibe - but the experience around it still had gaps.
The API hub ver. 2.0 on the website.
02 · Research

What users struggled with

  • Eye tracking - Microsoft Clarity
  • Interviews with client-facing stakeholders
  • Platform walkthroughs
  • Competitor's analysis
  • Trying was a maze. Try it out → start free trial → log in → subscribe → finally try. Users left confused, or uninterested.
  • Documentation went unnoticed. 80–85% of users never noticed the Documentation tab.
  • The API token couldn't be copied while hidden - the copy button only appeared after revealing it.
  • Credits were locked to one API. Credits bought for one API couldn't be used for another, or shared with teammates.
  • No team space. No way to add members, manage users, or get a user guide.
Eye tracking showed users bouncing through sign-up and subscribe screens before they could try anything.
03 · Who it's for

Who actually uses it

Competitors either don't let you try APIs visually, or hand you every possible piece of documentation. Our users needed neither extreme.

  • 20%Developers
  • 80%From BFSI - sales, PMs and others

InsightMost users aren't tech-savvy or familiar with the terms. They need a simple way to get just what they want - not to dig into the code the way developers do.

04 · Ideation

From hypotheses to a plan

I walked through the existing journey and noted hypotheses, then did competitor's analysis, ideation and user interviews. I conveyed the idea to stakeholders, aligned business goals and development possibilities - and only then started designing.

  • Hypothesis: the JSON output is what users want, and they want it fast.
  • Hypothesis: users don't notice the Documentation tab - a UI flaw.
  • Plan: one platform - onboarding, API catalogue, a simple try flow, documentation, pricing, team members and a dashboard.
Planning in Figma, on whiteboards and in notes.
05 · Onboarding

A short, personal onboarding

Three quick questions - your role, how technical you are, and which APIs interest you - plus dark or light mode.

  • Personalises the experience and what's shown first.
  • Helps the business too: personalised emails and suggestions.
  • A live side panel gives a glimpse of the tool while you answer.
The finalised onboarding, after several iterations.
06 · Try the API

Trying an API, in a click

Very direct and easy flow. No more confusion, no more frustrations.

  • New users land on two clear paths: get individual APIs, or create a workflow.
  • One clear CTA, with samples to try right there.
  • Input and output clearly split - results as a visual table or JSON.
  • Credits always visible, going down as you use the API.
  • A catalogue of every API, with proper sort and filters.
Try the API: pick a sample or upload a file, and see the output.
07 · Dashboard & pricing

Credits and pricing that make sense

  • Universal credits, usable for any API, with reminders when they run low.
  • Request, performance and usage metrics, plus error tracking, to follow every API.
  • Pricing by number of users - Basic, Pro or Enterprise, monthly or annually.
The new dashboard, in dark mode.
08 · Outcome

What users said

Tested with 15 users after the redesign:

  • 12/15Easy and quick try-the-API journey
  • 10/15Content exactly what they want
  • 14/15Credits now make more sense
  • 12/15Useful, understandable documentation
  • 11/15Working together is useful now
  • 13/15Analytics are more useful

Apex is currently a strategic experiment - the company is testing a new direction for the product. Meanwhile the API hub on the website continues, as one of our major products.

09 · Final product

The final flow

A walkthrough of the new try-the-API flow.

More details?

More Projects?

APEX- API PLATFORM

My Role?

Sr. UI/UX Designer

TEAM?

1 DESIGNER + RESEARCHER (ME),

1 FRONTEND DEVELOPER + 1 BACKEND DEVELOPER + MY MANAGER (GROWTH HEAD) + vp OF ENGINEERING.

TOOLS?

FIGMA

TIMELINE?

2 MONTHS

Company?

Arya.ai

API hub ver. 2.0: the API listing pages on Arya.ai's website
An API page with About, Try the API and Documentation, and the try flow
The hub's UI details: microinteractions, tags, subtle icons and hover cards
Competitor's analysis and personas: 20% developers, 80% BFSI sales and PMs
Pain point 1: users did not understand how to subscribe to try an API
Pain points 2 and 3: documentation unnoticed, copy button missing
Pain point 4: should documentation be more detailed?
Pain points 5 to 14: credits, security, collaboration, pricing and more
Walkthrough of the existing journey with problems, hypotheses and bugs
Competitor's analysis, ideation and interview notes
Stakeholder alignment, moodboards, whiteboard sketches and the screen plan
Onboarding iterations and the finalised onboarding, dark and light
New user dashboard: get individual APIs or create a workflow
API catalogue with sort and filters, and its iterations
Try the API flow: samples, upload, credits and output
Dashboard with request, performance and usage metrics
Pricing by number of users: Basic, Pro and Enterprise

THIS PRODUCT IS CURRENTLY IN THE strategic experiment,

WHERE THE COMMPANY WANTS TO TEST a new direction OF THE PRODUCT.


HENCE WHILE WE TEST THE PRODUCT, THE API HUB ON THE WEBSITE STILL CONTINUES -

AS IT IS ONE OF THE MAJOR PRODUCT FOR US

User test results out of 15 users