The slides to my talk at the Berlin Design Systems Coalition meetup early 2018.
Two years ago ResearchGate established a design system to gain a consistent user experience across their products. But with its introduction it became much more complicated to handoff designs to engineering including all design system relevant information. For existing design handoff tools the design systems abstractions and underlying principles are unknown and can only be interpreted to a certain extend. This keynote will give you insights on ResearchGate’s design system architecture and their solution to create design handoffs that empower a frictionless design to engineering workflow.
2. • UX Frontend Engineer
• Leading the Design Systems and Tooling team
at ResearchGate
• Open science platform with more than 14 million
researcher and scientist signed up
• With a team of five people we’re building a cross-
platform design system called Nova
3. • to fight inconsistency
• enable teams to build products faster
• introduce a common language to bridge the gap
• provide a delightful user experience
No va Design Syst em
4. Han do ffs with a
desi gn system in mind
How a design system almost ruined our workflow
21. • introduce complexity
• blocks the establishment of a
common language
• maintenance costs of design attributes
• translation overhead for engineers to
map bare values on aliases
Issues
29. handoffs without the support for component properties
and compositions are really problematic
30. • impossible to know which components in a
design are actually supported by the design
system
• impossible to tell how a component has to
be set up
• a functional workflow transforms into
an approach of trial and error
Issues
34. • a tailor-made Sketch plugin to create handoffs for
designs that are built with Nova
• interactive and inspectable design handoffs that can
be shared
• translate design attributes from bare values to aliases
• interprets component properties & composites
• … and much more
No va M easure
49. very powerful to fight inconsistency where it is
usually created in the first place
50. • manual adjustment of layer names is error
prone and far from being ideal
• high initialisation and maintenance costs for
design templates
• static design templates easily get out of sync
We’re not done yet
51. • a tailor-made Sketch plugin to render components
directly from code
• establish the code base as the single source of truth
• no outdated design resources, zero maintenance
costs, no errors in designs
No va Sket ch