API EXPLORER
Problem
We have 160+ powerful APIs locked away by poor discoverability and technical complexity, costing us six months of sales. We are now simplifying that power with self-explanatory UX to boost inbound sales and prove it is the fastest path to profit.
Details
My role:
Research & UX Design
Timeline:
2025 Q1
Responsibilities:
End-to-end process
Tools
Outcomes.
Reduced demo setup time
Demo sessions in Q2
RESEARCH
Usability testing insights.
All APIs cannot be tested openly
(50% participants)
Need to enhance search and filter
(60% participants)
Demo space.
Seamless handoff. The dedicated CTA moves you instantly from live demo to developer code.
Responses in table view.
Clarity in data. A single, scalable table makes every API response readable and effortless to integrate.
Responses in JSON view.
One response, two views. A simple toggle switches instantly between the data table and the raw JSON.
Lessons (The wins)
User-centric design works: we boosted adoption by simplifying jargon (like the table/JSON toggle) and proving that flexibility serves all user types.
Should have conducted deeper market analysis earlier and immediately prioritized the scalability testing for all 160+ API framework in discovery.
Tradeoffs (Strategic Choices)
We prioritized launch speed and sales efficiency to stop the pipeline stall, accepting a tradeoff that limited advanced customization for power users.