I independently recreated Stripe's Transactions dashboard in Figma, focusing on visual accuracy, consistency and reusable component architecture. The reconstruction brings together common B2B and SaaS interface patterns, including navigation, transaction tables, filters and status indicators.
I selected Stripe's dashboard because it brings together many of the elements found in complex B2B and SaaS applications, including navigation systems, transaction tables, filters, status indicators and data-heavy interfaces.
Beyond achieving a visually accurate recreation, my objective was to construct the interface using reusable components, demonstrating how I approach UI design with scalability, consistency and maintainability in mind.

I began by analysing the original interface, identifying its layout structure, typography, spacing, colours and recurring UI patterns.
I then reconstructed the dashboard in Figma, paying close attention to proportions, alignment, visual hierarchy and consistency between elements.
I also recreated the iconography manually using Figma's vector tools, maintaining consistent stroke weights, proportions and geometry across the icon set.
Throughout the process, I focused on achieving a high level of visual fidelity while ensuring the underlying interface remained structured and editable.
Rather than constructing the dashboard as a collection of static elements, I developed a component system covering navigation, buttons, tabs, filters, status indicators, summary cards and transaction tables.
Each component was designed to support relevant configurations and states while maintaining visual consistency across the interface.
My approach included:
Instance swap properties: Enabling icons to be interchanged without modifying the underlying component structure.
Text properties: Allowing labels, values and other content to be updated across component instances.
Component variants: Supporting different configurations, including active and inactive navigation states, selected cards and primary or secondary buttons.
Auto Layout: Maintaining consistent spacing, alignment and content-driven sizing across components.
Nested components: Combining reusable elements to create more complex interface patterns while retaining control over their individual properties.
By establishing these reusable patterns, I was able to make changes consistently across the interface, minimise duplication and maintain a structured Figma file.

The result is a visually faithful, desktop-focused recreation of Stripe's Transactions dashboard, supported by a reusable component system built in Figma.
The project demonstrates my approach to UI execution, from analysing an established visual language and recreating detailed interface elements to constructing flexible, reusable components.
It also reflects how I approach interface implementation more broadly: prioritising consistency, maintainability and clear component architecture alongside visual quality.
While the original visual direction belongs to Stripe, the reconstruction, component architecture and Figma implementation are my own.
This is an independent, non-commercial recreation of Stripe's interface. I was not involved in designing the original product.
