Summary
A Design system is not only about standardizing the UI or accelerating design. In the big picture, it can streamline collaboration between design and development. With this goal in mind, an effective Design system is available to both designers and developers in a format that is native to each discipline. However, getting to this point takes time. But what if we can skip ahead with a starter Design system containing both design and coded components that are ready for use? Join our activity sessions to see how you can transform your pixel-perfect designs into pixel-perfect code for modern web applications with Indigo.Design. We will also revisit the typical developer handoff by introducing a re-imagined workflow that minimizes rework. In the end, this approach can free up our focus to run Design-Ops better and deliver value sooner. Part 1 (Thursday): Introducing a starter Design system, and Indigo.Design overview Part 2 (Friday): Reimagining developer handoff, and introducing App builder ? Part 3 (Friday): Indigo.Design overview and exploring the developer workflow
Key Insights
-
•
Indigo.Design unifies design and development by creating components that exist both as UI kit symbols in tools like Sketch or XD and as real code components in Angular.
-
•
The system uses heuristics to translate absolute design layouts into responsive web-friendly layouts with relative margins and spacing.
-
•
Developers never have to manually rewrite frontend code; generated apps come as ready-to-run Angular repositories with all routing and styling included.
-
•
Theme changes propagate at the component level automatically, allowing global branding edits with a single click.
-
•
Publishing design changes creates new Git branches and pull requests, enabling controlled and traceable developer updates.
-
•
While Angular is currently the primary code generation target, React and Blazor support are planned, enabling platform choice at code generation time.
-
•
The design-to-code pipeline is one-directional; edits in Indigo.Design push to GitHub but do not sync back to original design tools like Figma or XD.
-
•
Generated components include detailed developer documentation and theming APIs, supporting extensibility and customization.
-
•
The system integrates with existing tools for design documentation and testing, supporting prototypes and user journey recordings in the cloud workspace.
-
•
Accessibility and compliance support is built in but still evolving; government market demands drive strict accessibility features.
Notable Quotes
"We want to leapfrog over individually inspecting things; developers won't have to copy and paste anything."
"One click, I am basically skinning this entire application to apply new brand attributes automatically to every component."
"This is a one-directional link between your design tool and the app builder; design tools don’t get updated by the builder."
"The CSS is only what’s relevant for recreating the layer; components know how to handle theming and styling internally."
"Developers can continue working in their IDEs, just fetching code from GitHub, without leaving their familiar environment."
"Publishing again creates a new branch with changes and a pull request, making collaboration and version control seamless."
"We support Angular first because many early customers use it, but React and Blazor are on our roadmap."
"Accessibility is driven by compliance, especially for government markets with strict keyboard navigation requirements."
"Documentation generation isn’t a core focus yet; we integrate with tools like Storybook and Figma for docs and visuals."
"Your main app stays stable on the main branch, and the app builder changes live on separate branches for safe developer review."
Or choose a question:
More Videos
"Having a well-thought-out data package really helps us see a fuller picture."
Brad Peters Anne MamaghaniShort Take #1: UX/Product Lessons from Your Industry Peers
December 6, 2022
"I like to think of myself as a DJ at a party, amplifying the power of design so more people can dance to the future."
Lona MooreScaling Design Beyond Designers
June 11, 2021
"Typing prompts is not the UX of the future. Integration into the interactive context where you work is better."
Josh Clark Veronika KindredSentient Design, AI, and the Radically Adaptive Experience (1st of 3 seminars)
January 15, 2025
"Stakeholders aren’t ready to write their own briefs or manage recruitment, so it ended up being a hybrid model initially."
Erin May Roberta Dombrowski Laura Oxenfeld Brooke HintonDistributed, Democratized, Decentralized: Finding a Research Model to Support Your Org
March 10, 2022
"If I really just needed only quantitative data from a survey, then I would not go the AI moderated route."
Tara TresselInvestigating qualitative depth of AI-moderated interviews
March 10, 2026
"Code is definitely considered the source of truth; we're working hard to make Figma an extension of that."
Charles Lee Jennie YipBuilding a New Home for the Atlassian Design System
October 22, 2020
"Every student has unique strengths that should be recognized and nurtured."
Kristin SkinnerFive Years of DesignOps
September 29, 2021
"Teams are better at solving problems and coming up with innovative ideas than solo practitioners."
Megan BlockerGetting to the “So What?”: How Management Consulting Practices Can Transform Your Approach to Research
March 26, 2024
"We developed family-facing intake tools to make the service experience more transparent and equitable."
Shanti Mathew Natalie Sims Natalia RadywylCivic Design at Scale: Introducing the Public Policy Layer Cake
December 9, 2021
