Boomi API Visual Interface

1. PROJECT SUMMARY
Provide an API ecosystem (directed to the API Architect persona) to show the relationship of elements, connections, and diagnostics.

2. PROBLEMS
Based on persona research, one of the most frequently referenced pain points is the relationship of elements within an API ecosystem. Boomi Integration relies on a drag and drop interface to build its processes, which we intended to replicate for a unified experience. The difficulty in the API build canvas is the limitations between backend, internet and component shapes.

3. SOLUTIONS
Develop a visual interface showing the navigation, optional elements, and required elements for each ecosystem. Presented as a template to each architect, in a click and drag interface, it will hold to specific containers.

Planning/Research

So what’s the problem really?

Interviews with internal colleagues and with users presented us with a common pattern of responses.

“Challenging to know what is invisible”
“I would probably forget how to use it if I left for 2 months how to do it. Not intuitive enough to learn, need a manual to get it.”
“Architect wants to standardize building across the enterprise and create patterns to scale, that are easy to use.”
“EASY TO GET LOST! Difficult to navigate.”

Design

Through a lot of collaborative sketching and discussion with tech leads, we developed a few iterations of the canvas, before eventually applying the Boomi UI to the final design. Planning to present this to users and continue to iterate before sending to development.