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
-
•
Building and maintaining a custom design system often requires a dedicated team and significant overhead, which can be a deal breaker for small teams or agencies.
-
•
Many organizations end up with a Frankenstein design by mixing elements from various popular design systems without cohesion.
-
•
Indigo.Design offers a white-label, customizable starter design system aiming to fit diverse niches and verticals.
-
•
Matching design and developer toolkits in native formats (Sketch, XD, Figma, Angular) creates smoother workflows and reduces handoff friction.
-
•
The Indigo.Design plugin allows real-time theme customization, generating entire color palettes and typography schemes from base inputs.
-
•
The system automatically converts absolute design layouts into responsive flex layouts during handoff to save designers and developers time.
-
•
Cloud-based prototyping enables pixel-perfect sharing, stakeholder feedback, and integrated usability testing with video recording.
-
•
Open-source style hooks and fully accessible source code empower developers to localize and customize UI for different regions and languages.
-
•
A major goal is to eliminate wasteful debates over pixel-level differences by automating fidelity in design-to-code translation.
-
•
Indigo.Design does not seek to replace existing tools like Zeplin or InVision but to complement design and developer toolchains with integrated capabilities.
Notable Quotes
"Design systems has always been a beginning, like a seed, and design ops basically serves as the nurture."
"For a design system to be effective, it should be available to both designers and developers as a matching set and in a format that is native to each discipline."
"Sometimes different teams use different tools, so you may need a design system for Sketch for one team but then for XD for another."
"You end up with something which I call Franken design because it’s kind of a mix and match of many different things, but it’s anything but a real design system."
"We try to provide a lot more patterns because for newbie designers or product owners, patterns help them put together flows quickly."
"With the Indigo.Design plugin, you can profoundly change how the whole design system looks by just tweaking primary or secondary colors."
"Once you use Indigo.Design in Sketch or XD, you’re just a few clicks away from having a running Angular app based on our developer toolkit."
"Our handoff process turns absolute layout into a flex layout structure, so you get responsiveness out of the box without copying screens for each size."
"Final versions often do not look exactly like the original design, so we want to invest our time in process improvement, not arguing over pixels."
"You want designers to use the UI kit like any other UI kit, and developers to modify the code they’re familiar with, all matched perfectly."
Or choose a question:
More Videos
"Researchers must shift from gatekeepers of knowledge to coaches who help others understand what to trust."
Megan Blocker Marieke McCloskey Renee ReidPositioning insight: Structuring teams, roles and careers for a changing research landscape
March 13, 2025
"The style component was developed in two minutes rather than taking a few days to create and document."
Ryan Matthew Alex KurchevBridging Design and Code: AI-Powered Design System Integration
September 11, 2025
"If we are working on something that does not ladder up to our KSPs, then we should not be working on it."
Saara Kamppari-Miller Nicole Bergstrom Shashi JainKey Metrics: Comparing Three Letter Acronym Metrics That Include the Word “Key”
November 13, 2024
"Empathy applies to us too—we needed to understand how our own people were feeling about these layered changes."
Erin HauberDesign is Not the Frosting on the Scaled Agile Layer Cake
October 24, 2019
"Most people’s fears about AI are actually fears about capitalism."
Sheryl Cababa Ethan Marcotte Milena PribicDay 2 Panel
June 5, 2024
"High-performing cross-functional teams self-organize around shared goals even with ambiguous roles."
Matt LeMayYou Don’t “Get” Anyone to Do Anything
December 6, 2022
"The plumbing of government—the unseen systems, processes, people, and policies—are design opportunities too."
Ed MullenDesigning the Unseen: Enabling Institutions to Build Public Trust
November 16, 2022
"Finding the right method for the problem is important; don’t drink the Kool-Aid just because the preacher says to."
Sharbani DharBreathing Room for Delight
January 8, 2024
"Transparency is the basis for trust and respect among employees and leadership."
Iram ShahClosing Keynote: The View from the Top
June 4, 2019
