UI and interaction design: the beginning of a long relationship with builder platforms
2019-20 | Freelance, via PRODUX | In collaboration with Marcelle Kaspi (UX and Strategy)
1. UI design within the IA framework
2. Interaction design: search, navigation, filtering
3. Builder flow: creating contracts and methods
4. Component library for developer handoff
My first builder, and where it all started
OpenLegacy is an enterprise platform that connects legacy backend systems to modern cloud infrastructure. Organizations that cannot replace their core systems use it to expose them as APIs and build new services on top.
The product is a builder: users come in and construct integrations, contracts, and methods from scratch.
Magic happens when all UX rules are kept and the information architecture is crystal clear. That was the challenge here, and it was genuinely satisfying to crack.
I worked alongside Marcelle Kaspi, a master of UX strategy and specification, via PRODUX. Marcelle led the IA and solved the hard structural problems. I handled UI, interaction design, navigation patterns, and the component library for handoff.
This was the first builder-type product I designed. After OpenLegacy came EasySend, then Myop.
The challange
The system has many entity types: Entities, Modules, Projects, Solutions, Contracts, Services. Users need to move between them without feeling lost.
The search, tagging, and filtering systems had to carry a lot of weight.
The builder flows needed to feel structured and learnable, not overwhelming.
My job was to take that structure and make it work at the interaction and UI level.
The process
I learned by doing. I worked within Marcelle's framework, which meant understanding her navigation logic deeply before touching screens.
I designed interaction patterns for search and filtering, navigation between entity types, and the builder flows for creating contracts and mapping methods.
Along the way I learned something that has stayed with me: how to design a system where users build things. How to handle state, steps, empty states, and the moment when something gets created.
I also prepared the full component library in Figma for developer handoff.
The Solution
Navigation and search interactions across a multi-entity system.
Builder flows for creating contracts, adding methods, and mapping inputs and outputs.
Dashboard and list views for projects and modules.
A complete Figma component library for handoff to the development team.
The result
Not because it was my biggest project. It is here because it was the first time I designed a builder.
The first time I had to think about what it means for a user to come into a system and construct something from nothing.
That thinking has shaped every builder project since. OpenLegacy, EasySend, Myop: same core challenge, growing complexity.
OpenLegacy, Legacy systems integration with modern applications
• My first builder project: designing a system where users construct workflows and integrations from scratch • Learning to design complex navigation with many entity types
• Working within a structured IA framework led by a senior UX strategist
• Component library preparation for developer handoff
The challange
The process
The Solution
The result
Final Takeaways
This was the first time I designed a builder. I did not fully understand what that meant until later projects made the pattern visible.
Working within Marcelle's IA framework was the right context for it. She solved the structural problems. I learned to execute at the interaction level, inside a system I did not fully own. That constraint taught me something: before you can design a builder well, you have to understand what it means for a user to construct something from nothing, step by step, in a system that has no single right path through it.
That understanding is what I brought into EasySend. And then into Myop.
Credits: Marcelle Kaspi, UX and Strategy Expert. Engagement facilitated through PRODUX.