Apiture Developer Portal
Designed features for the Developer Portal and created a design system library.
At a glance
- Company
Apiture
2025
- Role
UX Designer
- Team
Product Manager, Design System lead, engineers
- Responsibilities
Design System, UX/UI Design
- Goal
Build out Developer Portal functionality to enable test customers.
- Outcome
Designed features for the Developer portal and established a component design library to improve scalability.
Apiture is a banking platform that small community banks use to power their platform. The Developer Portal lets engineers configure software; unfortunately, it received little attention. Developers used it to experiment with parts of the Apiture banking platform before a new client committed to working with Apiture. The product manager and I worked closely to review research and explore integrating new features. While designing new features, I created a design system for the Developer Portal and worked with the consumer-facing design system to integrate it.
Understanding the Ecosystem
In the beginning, I explored the problem and mapped out the domain. We focused on the dashboard, API Documentation, and "Try It" functionality. I discussed the experience and goals with several engineers to better understand the project's vision. Connecting research with strategy brings a product to life.
Building Test Customers APis
Providing developers with a structure to test ideas was a concept that I workshopped with the Product Manager; I drew while she spoke to understand to ensure we shared the same mental model of what we were building.
Prototyping the experience
Building prototypes and having conversations is a great way to learn along the way. Apiture's ease of communication made sharing work more fun. We often reviewed work and moved toward the details that make a product work.
Designing a Design System Library
When I began working with the files, I realized the Developer Portal would benefit from a resource of components that are part of the visual system. I enjoy documentation and making scalable products. The Developer Portal used a different tech stack than the consumer-facing platform, my design system library noted the differences between the systems for the next iteration of the migration.
Led a Migration of Components
After I documented all the components, the Apiture consumer-facing Design System lead for AUI began discussing migrating the Developer Portal elements into a single system.
“It has been a pleasure working closely with Kiera! She’s incredibly kind, curious, and thoughtful. She took time to understand how we work and dove deep into learning about the Apiture design system. She made a meaningful impact on the Dev Portal team; both by offering smart design solutions and by thoughtfully evaluating how well our design system could support their needs. She brought great insight, positivity, and collaboration to our design team, and we’re all grateful to have spent time working with her.” — J. Richardson, Design System Lead at Apiture
Outcomes
Although the Developer Portal used a different tech stack, the Design System Library made it easier to convert the files we were building to a new system.
Learnings
Apiture had an engaging, smart, and fun design team that I had the pleasure of contributing to. As I prepared documentation for the Developer Portal migration to the AUI Design System, I worked closely with the Design System team to best prepare our efforts.