Component libraries and design systems
HSBC Egypt, Solutions by STC, Floward, Across three roles
Building shared component libraries, and integrating design-system packages, across a bank, a SaaS platform and an e-commerce monorepo.
Button states
- SaveDefault
- SaveHover
- SaveFocus
- SaveDisabled
Field states
LabelValue
LabelValueError message beside the field
Context
Reusable components are the thread across my last three roles. At HSBC and Solutions by STC I built shared libraries. At Floward I integrated existing shared components and design-system packages.
Problem
Without a shared system, teams rebuild the same interface patterns and drift apart in consistency and accessibility.
My responsibilities
- HSBC: designed and maintained a shared UI component library reused across internal products.
- Solutions by STC: built a reusable library of accessible UI components from Figma designs, inside a multi-tenant component system.
- Floward: integrated shared UI components and design-system packages into product features, in a project using Storybook.
Technical approach
- Figma designs translated into accessible, reusable components.
- Multiple user roles and white-label configurations supported by the component system at Solutions by STC.
- Standardized design patterns across products at HSBC.
Architecture and tools
- React.js
- TypeScript
- Material UI
- Tailwind CSS
- Storybook
- Figma
Challenges
- Supporting white-label configurations from one component system.
- Applying the same discipline whether building a library or consuming someone else's.
Outcome
- HSBC: standardized design patterns and sped up development across internal products.
- Solutions by STC: improved consistency and maintainability across teams.