HomeEducationCode or Design – Which is a Higher Supply of Fact? Get...

Code or Design – Which is a Higher Supply of Fact? Get hold of US

Code or Design – Which is a Higher Supply of Fact? Get hold of US

The worldwide design system’s neighborhood, Into Design Programs, hosted a webinar in July 2023 the place visitor speaker Marcel Bertram talked about “Systematic Design With Code.” Marcel made some attention-grabbing comparisons about designing utilizing vector-based vs. code-based design instruments and the way organizations can use the latter to create a single supply of fact.

Into Design Systems is a digital design methods convention for the worldwide Design and DesignOps neighborhood, together with designers, builders, Design Leads, design managers, DesignOps practitioners, and plenty of others. The community-driven initiative shares information to assist evolve the trade and its members.

Marcel Bertram is a Model Design Specialist main the Design System workforce at a world car producer. He’s additionally the Co-Founder & UX Coach at, a consultancy for UX Design Operations.

This text relies on Marcel’s Into Design Programs stay titled “The Energy of Design, Code & Ai in Design Programs.” We’ve got summarized Marcel’s discuss into its key factors, however you possibly can watch all the 3-hour webinar here.

Key takaways:

  • Vector-based design instruments arose from a necessity to offer scalability and readability throughout totally different resolutions within the digital panorama.
  • The discharge of UXPin’s Merge know-how in 2019 marked a major shift in design paradigms, mixing code parts straight into the design course of for a unified UI library.
  • Recognizing code because the “supply of fact” ensures consistency, effectivity, and a holistic understanding of software mechanics throughout design and improvement groups.
  • German-based software program company dotSource utilized UXPin Merge to bridge the hole between design and improvement, synchronizing code, design, and documentation.
  • UXPin’s Merge know-how advances trendy prototyping, enabling designers to check sensible person interactions and acquire correct insights through the design course of.

Use coded parts as a single supply of fact between designers and builders. Bridge the hole within the course of and launch merchandise quicker. Study extra about it. Uncover UXPin Merge.

Within the early days of digital design, there was a urgent want to duplicate the precision of bodily artwork. As a substitute of setting up photographs from tiny dots, as pixel-based strategies do, vectors use mathematical equations to form graphics. Consequently, these photographs keep sharp and scalable, regardless of the way you alter their dimension.

Conventional graphic design laid the groundwork for vector instruments. The trade adopted instruments like Adobe Illustrator as a result of they persistently delivered crisp visuals throughout platforms and resolutions. As the necessity for adaptable designs surged with the rise of internet sites, functions, and digital adverts, designers naturally gravitated towards vector-based instruments. Their alternative wasn’t simply aesthetic–it addressed the sensible calls for of the digital panorama.

The code-based revolution

Whereas vector-based instruments have helped get us to the place we’re right now, they haven’t advanced to bridge the hole between design and improvement–till the discharge of UXPin’s Merge know-how in 2019

Merge’s code-based method brings code parts into the design course of, so designers can use the identical UI library for prototyping as engineers to develop the ultimate product.

Vector-Based mostly vs. Code-Based mostly Design Programs

Digital product design is slowly shifting from conventional vector-based methods to the progressive code-based method. The mixing of code within the design course of has modified how builders and designers collaborate, streamlining all the product improvement course of. 

Let’s discover this evolution and perceive its implications on design methods and prototyping.

Understanding vector-based methods

What are they?:

  • These are instruments that use mathematical equations to symbolize photographs in pc graphics. Fashionable examples embrace Figma and Adobe Illustrator.


  • Appropriate for static prototyping and visible designs.
  • Intuitive for designers to visualise, draft, and make fast alterations.


  • Lacks the dynamism of real-life functions.
  • Can’t all the time precisely emulate person interactions, transitions, or superior part behaviors.
  • Doesn’t symbolize the intricacies and potentialities of code.

Understanding code-based methods

What are they?:

  • Design instruments that use precise coded parts on the design canvas, like UXPin.


  • Creates a single supply of fact throughout the group with automated updates for designers and builders.
  • Seamless transition between design and improvement phases.
  • Precisely represents the real-life habits of parts for sensible prototyping.
  • Extra significant suggestions from person testing and stakeholders.
  • Much less reliance on engineering groups for advanced prototyping.
  • Built-in accessibility options, semantics, and browser functionalities like password managers.
  • Facilitates exploration primarily based on actual coded UI components.
  • Designers get the advantages of code however nonetheless work with a well-known design software interface.


  • Solely the design system workforce can implement adjustments–which is sweet for governance.

Code because the Supply of Fact

The ultimate digital product is code-based. Builders work with code. The design workforce makes use of a vector-based software, creating a spot between them and the ultimate product. Subsequently, recognizing code because the central reference level or the “supply of fact” is pivotal.

This philosophy ensures:

  1. Consistency and cohesion: Guaranteeing that designers and builders draw parts from the identical repository ensures uniformity throughout the board.
  2. Effectivity: With everybody referencing the identical library and documentation, there’s much less room for miscommunication or discrepancies.
  3. In-depth understanding: Encourages designers to know the core mechanics of how functions perform, fostering a extra holistic design method.

A Single Supply of Fact with UXPin Merge – dotSource’s Case Examine

uxpin merge component sync 1
Code or Design – Which is a Higher Supply of Fact? Get hold of US

Earlier than switching to UXPin Merge, German-based software program improvement company dotSource had an issue:

Selling new patterns and parts to a design system includes many redundant processes. Most design system releases require updating in no less than three locations:

  1. The design system’s codebase (part library)
  2. The design workforce’s UI equipment (design software)
  3. The design system’s documentation

“As a substitute of a ‘single supply of fact’ that offers ‘three single sources of fact’ for each UI part–this appears counterintuitive and will increase errors. If the design system’s replace course of and applied sciences don’t align, the workforce finally ends up with redundant work as a result of a single change requires three updates.”

dotSource discovered the one answer to this downside was to implement a code-based design course of, making a true single supply of fact between design and improvement.

The corporate makes use of Merge know-how to import a product’s design system into UXPin so designers can prototype utilizing code parts.

“We use UXPin’s Storybook integration, which permits designers to make use of our design system’s Storybook parts in UXPin’s design editor. The end result: an ideal synchronization of code, design, and documentation, making it potential for:

  • Designers to take part in QA and assist builders establish bugs
  • Shut collaboration between designers and engineers
  • Higher testing and quicker iterations with high-fidelity interactive parts (component-driven prototyping)”

Trendy Prototyping – Static vs. Interactive

code developer design 3
Code or Design – Which is a Higher Supply of Fact? Get hold of US

Static prototyping

Utilizing vector-based instruments like Figma works properly when the target is to gauge comprehension or aesthetics. It supplies a static visible illustration with out intricate interactive layers.

Designers sometimes transfer from a vector-based software to a prototyping software, which provides prices and operational burdens, they usually nonetheless don’t obtain outcomes similar to code.

Interactive prototyping

Code-based design instruments improve prototyping scope for extra complete performance and person journey exams. Instruments like UXPin can emulate actual interactions, toggle functionalities, enter area behaviors, and extra, providing a practical person expertise.

UXPin’s Merge know-how goes past what you possibly can see into how a prototype feels in a real-world state of affairs. Design groups can use insights from testing to iterate and enhance with higher accuracy. Designers improve usability and might establish extra enterprise alternatives through the design course of, rising their worth to the group.

Transitioning to a Code-Based mostly Design Workflow

prototyping elements components
Code or Design – Which is a Higher Supply of Fact? Get hold of US

The world of digital design is huge and ever-evolving. Whereas vector-based instruments serve their goal in preliminary design phases, embracing the benefits of code-based methods is the way in which ahead. This built-in method reduces inefficiencies and miscommunications whereas guaranteeing a extra genuine person expertise throughout testing.

As designers and builders proceed to collaborate, it’s essential to do not forget that our final objective is to craft user-centric, environment friendly, and aesthetically pleasing functions. Understanding and using the best instruments is a major step in that course.

Growing design system maturity with UXPin Merge

UXPin’s Merge know-how at present leads the code-based design revolution with instruments and options that meet the wants of recent product improvement groups.

It could possibly take years for organizations to achieve full design system maturity–a totally built-in system with designers and builders utilizing the identical UI library and documentation. Most by no means get there, sustaining a number of sources of fact like our pals at dotSource.

UXPin Merge is the bridge to that hole. Organizations can create a totally built-in design system from the beginning, circumventing a few years of wasted sources.

With UXPin Merge, you possibly can:

Prepared to affix the code-based revolution? Go to our Merge web page to discover ways to create a single supply of fact on your design system and develop higher product experiences on your customers.

#Code #Design #Supply #Fact

Continue to the category


Please enter your comment!
Please enter your name here

- Advertisment -spot_img

Most Popular

Recent Comments

Skip to toolbar