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
"When the whole team is trained in design thinking, they are measurably more aligned, more efficient, and more agile."
Doug PowellClosing Keynote: Design at Scale
November 8, 2018
"Kids are not little adults. You can’t just simplify the text and call it for kids."
Mila Kuznetsova Lucy DentonHow Lessons Learned from Our Youngest Users Can Help Us Evolve our Practices
March 9, 2022
"Evan actually spent less than 15 minutes on the essay, and instead of working on homework, he was writing a letter to his significant other back home in Detroit."
Sarah GallimoreInspire Progress with Artifacts from the Future
November 18, 2022
"We can’t complain about not having a seat at the table if we don’t offer one of our own."
Lada Gorlenko Sharbani Dhar Sébastien Malo Rob Mitzel Ivana Ng Michal Anne RogondinoTheme 1: Discussion
January 8, 2024
"The hackathon is a low-commitment way to get people creatively engaged and having fun."
Alnie FigueroaThe Future of Design Operations: Transforming Our Craft
September 10, 2025
"Statistical significance tells you if a change is likely not random, but it does not tell you if the change matters to your business."
Landon BarnesAre My Research Findings Actually Meaningful?
March 10, 2022
"When you’re talking, it’s easier to learn something new, but if you’re shy and don’t talk, you don’t learn anything."
Emily EagleCan't Rewind: Radio and Retail
June 3, 2019
"We neglected our power users during the responsive, one-size-fits-all strategy, and it really hurt us."
Malini RaoLessons Learned from a 4-year Product Re-platforming Journey
June 9, 2021
"Project management was focused on outputs, assuming the correct feature was already defined."
Asia HoePartnering with Product: A Journey from Junior to Senior Design
November 29, 2023
