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 provides a seamless bridge between designers' UI kits (Sketch, XD, Figma) and developer-ready Angular code.
-
•
The cloud-based app builder enables real-time collaboration between designers and developers on the same components.
-
•
Code generated by Indigo.Design is a full-fledged Angular app with routing, styles, and assets structured for immediate compilation.
-
•
Global theming is supported, allowing developers or designers to change app-wide brand attributes with one click.
-
•
Instead of CSS specs handed off, developers get complete components with built-in styling hooks and documentation.
-
•
Publishing new design versions creates branches and pull requests in GitHub, streamlining developer updates.
-
•
Indigo.Design currently supports Angular 12/13 code generation; React support is on the roadmap.
-
•
Documentation generation is not yet automated but the system supports integration with tools like Storybook and can coexist with external docs.
-
•
The workflow preserves design fidelity so developers run apps that look exactly like the designs without debate.
-
•
Assets like SVGs and images are automatically managed and placed in the app’s assets folder, ensuring consistent inclusion.
Notable Quotes
"Designers create their designs in Sketch or XD and import them into the cloud app builder, where both designers and developers can collaborate."
"We generate professional Angular applications where developers don't need to copy-paste or handwrite frontend layout code."
"With one click, you can skin the entire application and change brand attributes like typography, coloring, or rounding."
"Publishing changes creates a new branch and pull request in GitHub, making it easy for developers to review and merge."
"The CSS is minimal because components absorb style changes from top-level variables; styles are never duplicated per component instance."
"We don't black box anything — you get all the code structured as a real Angular app, ready to run with npm install and npm start."
"Currently, we target Angular first because many customers use it, but React support is coming soon in our roadmap."
"Accessibility compliance is critical especially for government customers and is something we support and continue improving."
"Indigo.Design is compatible with external documentation tools like Storybook or Zeroheight but doesn't generate all documentation automatically yet."
"At the end of the day, the goal is to guarantee that what you design matches exactly what gets produced in code."
Or choose a question:
More Videos
"When teams lose a sense of agency, they act strange, cutting corners and racing to get something out the door."
Standardizing Product Merits for Leaders, Designers, and Everyone
June 15, 2018
"Space has meaning in a map—if you move components around without reason, it’s no longer a map."
Simon WardleyMaps and Topographical Intelligence (Videoconference)
January 31, 2019
"There’s a gap between intentions and impact; humility is needed to close it."
Sandra CamachoCreating More Bias-Proof Designs
January 22, 2025
"It takes at least one team member to choose to set healthy standards for collaboration."
Darian DavisLessons from a Toxic Work Relationship
January 8, 2024
"After each interview, I input the transcript into ChatGPT and ask for three key takeaways that I can quickly share with stakeholders."
Fisayo Osilaja[Demo] The AI edge: From researcher to strategist
June 4, 2024
"There is a common thread in craft: dignity, purpose, utility, and beauty."
Uday GajendarThe Wicked Craft of Enterprise UX
May 13, 2015
"Trust is often underestimated but is critical when designers face public critique and feedback."
Davis Neable Guy SegalHow to Drive a Design Project When you Don’t Have a Design Team
June 10, 2021
"We stopped talking about patterns and consistency and started talking about scalability and speed to connect with stakeholders."
Eniola OluwoleLessons From the DesignOps Journey of the World's Largest Travel Site
October 24, 2019
"Product managers feel design is a black box; they want visibility, transparency, and accountability on timelines."
Aurobinda Pradhan Shashank DeshpandeIntroduction to Collaborative DesignOps using Cubyts
September 9, 2022
