One shared Angular component library for multiple Siemens feature teams

We built a common Angular UI library for a Siemens project with multiple feature teams: components designed in Figma, documented in Storybook with working examples, and backed by high test coverage.

Design → code

Figma designs become documented, tested Angular components

Every team

Feature teams build on the same components

The Challenge

Multiple feature teams were building within one Siemens project, and without shared components the UI risked drifting apart between them. Siemens wanted a single component set that kept the project consistent. Its requirements were strict: excellent documentation, many working examples, a good user experience and high test coverage.

The Approach

We designed the components in Figma and built them as a reusable Angular library. We documented and showcased every component in Storybook, with working examples teams can copy. We kept test coverage high throughout, so teams can rely on each component. Delivery ran in agile sprints managed in Jira and Confluence.

The Results

Siemens' feature teams now build from one cohesive set of components, which keeps the UI consistent across the project. The documentation and examples make the library easy to adopt and cut development time. With high test coverage behind every component, the teams can now use the library in critical parts of the project with confidence.

Design → code

Figma designs become documented, tested Angular components

Every team

Feature teams build on the same components