top of page

Designing a New REST API Connector

For a Multi-Application Platform Server

The MAPS development team was building a new SaaS-based solution that connected to 3rd-party software services.

What I contributed to MAPS

I used the Design Thinking product development process to inform my design choices and built a solution that served a new generation of SQL developers. I was given 3 weeks and many tasks.


Bearer Token Authentication & Data Security

Ethos Data Connection DX

By giving users the ability to add fields to their Ethos connection database, I improved the Developer Experience and made Evisions' MAPS product more suitable for technical users.

After seeing the initial Proof of Concept, I constructed a diagram that was more user-friendly - designed to help SQL developers do the complex work on a simpler UI.

How I did it

I cross-collaborated with developers with more than 15 years' experience in their industry and incorporated my design thinking process into their development process.


Some Working Sessions Were In Order

Working Sessions are a fancy way of saying, "let's get together and talk about design." During these sessions, the MAPS development team paved the way for my discovery phase and provided me with the basic data to construct an intuitive design.

First, We Started With 3 Important Principles

The below principles acted as a guide as my relationship with the developers changed throughout the project.

cross_collab process@4x.png

Then, I Gathered Requirements

After taking the time to understand the developers' requirements for release, I began sketching out the basic concept for this Ethos connection feature.


Defining the Schema Setup Process

First, this complex process would require me to sketch it out so I could understand the workflow. 

Schema Setup Process.png

These initial sketches revealed a new potential workflow for new users adding fields to their schema, or generated list of variables.

With all requirements addressed, I built interactive prototypes detailing how users would add a schema in the new user workflow.

I was able to present this workflow to the developers, who provided helpful feedback and helped me adjust my designs according to project requirements.

I got the opportunity to build next generation SaaS features with an Agile development team, and loved every moment of it through every iteration. I learned the importance of cross-collaboration and communication.

Like what you see?


Understanding the Problem

Users needed an easier way to add APIs that were not part of the schema, or generated list, of XML code. In order to design an interface that met both development's requirements and user needs, I needed a strategy.


Defining The Problem

To better understand the context, I sketched user workflows, brainstormed new ideas with the team, and used iterative design practices to build a better MAPS.


Prototype & Demo the Solution

Through the process of continuous iteration, I was able to better align with the MAPS Development team and gather enough information to build a product that better served our users.

In Conclusion...

click here to see more stuff I've done.

You can also contact me if you're hiring.

bottom of page