Polaris API Designer
Overview
As a data analytics company, 84.51° profits off the development of API's. However there's a problem. API Developers at the company each have their process to build an API which results in a lack of standards which in turn results in a subpar product. Polaris is an API creator tool designed to make it easier for developers and non-developers alike to build API's. The Polaris API Designer is just one part of the tool that let's developers mock up and share API designs before they have to write a single line of code.
Type
UX/UI Design
Team Credit
Joshua Smith
Date
Fall 2024
Going from I'm in Hell toThat would be dope as Hell*
*Real Quotes from User Research
So what even is an API...?
An API is an Application Programming Interface. Does that clear things up? Probably not, it took me a while to get a handle on what API's are and how they drive revenue.
To help understand what an API is in the context of this project, I've developed the soda fountain metaphor. 84.51 employees are masters of working with data, just as Coca-Cola employees are masters of making soda. The customer, however, doesn't care about what's going on behind the scenes. They just want to get their nice filtered Kroger shopping data, or cup of diet coke, when they ask for it.
That's when the API comes in. It's contract of code between us and the customer. You pay and put your cup under minute maid and you'll get lemonade. You send us this message and you'll get this array of data.
The Problem: At 84.51° API Development is...
Fractured
Each developer has their own process and standard of API Development which makes collaboration difficult
Slow
The time to build API's for customer is much slower than the competition which is leaving revenue on the table
Repetitive
Each time a new API is built it requires timely, boilerplate steps such as creating a github repo that could be easily automated
Initial Research Question
What Steps do 84.51° Developers take to build an API?
The Polaris API Designer
A tool for developers and non-developers alike to design, mock, and share API's
Usability Testing
Research Question
Are Users of the Polaris API Designer able to discover and use all the features that the platform provides?
Research Methods
At the beginning of the engagement, participants will be told that after they have time to explore the prototype the researcher will be asking them to explain what the Polaris API Designer does to help a user build better API’s faster. They will have as time as they would like to explore the prototype. The research will have their camera but will be watching and can answer questions. Afterwards the participant will be asked “Explain to me what the Polaris API Designer is Capable of.” Their responses will be graded based on the rubric.
Value Testing
Research Question
Are the features of the Polaris API Designer the features that our Developers need to create better API’s faster?
Research Methods
After the usability testing, the participant will be asked if they would be willing to join the beta program for early access. In exchange, we’d ask them to participate in further opportunities to give feedback.Finally, participants will be asked if they could give me the names of three people that the research could send additional meeting invites out.
Testing Highlights
100%
…of the 1-on-1 participants were able to identify and understand the scorecard, reusable library, and publishing features
100%
…of the 1-on-1 participants were not just interested but excited about joining a beta program
88%
± 10.69%
…of asynchronous participants in technical roles were open to joining a beta program
