Skip to content

Latest commit

 

History

History
35 lines (22 loc) · 2.75 KB

uds.md

File metadata and controls

35 lines (22 loc) · 2.75 KB

Universal Design System (UDS)

Why does UDS exist?

The UDS project started as a technology recommendation for facilitating the delivery of omnichannel user experiences across TELUS brands in order to address the breadth of brands, channels, and platforms in which TELUS operates.

What is UDS?

The Universal Design System (UDS) is a family of design systems that was created to support multiple TELUS owned businesses and initiatives. UDS is the foundation for building design systems at TELUS, and supports the development of cross-platform and multi-brand applications.

The benefits of UDS are:

  • Brand-agnostic - It includes the brand-agnostic React Native Base components, palettes and themes for each of the supported TELUS brands (TELUS, Koodo, and Public Mobile, as well as tooling to support validating and building those palettes and themes.
  • Cross-platform - React Native allows UDS Base components to be shared and reused on the Web, as well as in iOS and Android applications.
  • Reusable - The Base component library is a collection of UI elements that can be reused across multiple platforms and brands.
  • Multi-brand - UDS Base components have TELUS's sophisticated theming mechanism which supports usage across multiple TELUS brands. Also components can be customized to support non-TELUS brands.
  • Omni-channel - UDS Base components can vary in appearance according to the context or channel within a brand, allowing further degrees of reuse and flexibility.

Who are the primary users?

The primary users are business teams outside of the TELUS brand, and multi-platform TELUS teams that are building or maintaining a design system or component library for use in the TELUS organization.

When should UDS be used?

  • Multi-platform - Teams building applications that will run on multiple platforms can use some Allium components and all UDS components to support cross-platform components. They may adopt UDS components directly and collaborate with the UDS team to customize them.
  • Multi-brand - Teams building applications that cut across several brands will need to adopt UDS components directly and tailor them as needed.

If you are working with UDS, you can post your questions on #ux-architecture-community.

References