Introducing QZL Design Library: An Open-Source Design System for React and React Native

Explore QZL Design Library, an open-source design system with shared foundations and reusable React and React Native components.

Open Source•~5 min read•November 20, 2026•By QZ-L Editorial
#Open Source#React#React Native#Design System#JavaScript#TypeScript#UI Components
Looking for related guides? Start with the qz-l Learning Center and explore more tutorials in this topic cluster.

Introducing QZL Design Library

We’re excited to announce that QZL Design Library, developed by Q.Z.L Corp, is now open source.

QZL Design Library is a cross-platform design system for building consistent, accessible, and expressive interfaces with React for Web and React Native. It brings shared design foundations together with components designed for each platform.

Instead of letting every product reinvent colors, spacing, interaction states, and common UI patterns, we wanted to create a design language our teams could share—and make those foundations useful to other developers, too. The library is released under the MIT License.

One design system, two platforms

QZL Design Library is published as two component packages:

  • React for Web: reusable components for React web applications.
  • React Native: native components that follow the same interaction intent where platform conventions allow.

The two platforms share design foundations, including color, typography, spacing, shape, motion, and themes. The components are not intended to make a native app look like a website: each package respects its platform’s conventions while helping products maintain a recognizable visual language.

The current catalog includes 51 Web components and 48 React Native components. It spans actions, form controls, navigation, overlays, notifications, data displays, progress and loading states, and content components. Both packages include documented APIs; the web catalog also offers interactive previews.

More than a component catalog

Components are only one part of a design system. QZL Design Library also provides:

  • Shared tokens and themes to establish a consistent starting point for color, type, spacing, shape, and motion.
  • Reusable interface patterns for common application tasks, from buttons and form controls to tables, charts, and feedback.
  • Accessibility guidance to help teams communicate state, provide useful feedback, and make interactions understandable.
  • Security-conscious input patterns that emphasize user control and privacy-aware behavior.
  • Customization examples and API documentation so teams can understand how components work and adapt them to their product.

The intent is to make common interface decisions easier—not to prescribe every product’s visual identity. Teams can start with shared foundations, then customize the experience that makes their product distinct.

First products using the library

We’re using the new design system in our own products. qz-l.com has a refreshed interface built with the library, bringing a more consistent, polished feel to the website.

QZL Compare and Gemini-Guess are among the first products to adopt it. Both now have new interfaces shaped by the shared design foundations, while keeping their own character and purpose.

Putting the library into real products lets us exercise it across different experiences—from a utility for comparing files and text to an interactive guessing game. That feedback helps us keep improving the components and documentation as the design system grows.

Get started with React for Web

Install the package:

npm install @qzlcorp/react

The application should provide React and React DOM 18.3.1 or 19. Import the library stylesheet once from your application root, then use components where you need them:

import "@qzlcorp/react/styles.css";

For example, LinkButton provides link semantics for navigation, while Button is intended for actions:

import { Button, Card, LinkButton } from "@qzlcorp/react";

export function ProjectCard() {
  return (
    <Card variant="featured">
      <Button>Save project</Button>
      <LinkButton href="/projects">Open project</LinkButton>
    </Card>
  );
}

If you use Next.js, LinkButton can render through next/link with its renderAs prop, preserving client-side navigation and prefetching. See the React package guide for the full integration example and component APIs.

Get started with React Native

Install the React Native package and its chart and slider dependencies:

npm install @qzlcorp/react-native @react-native-community/slider react-native-svg

The host application should provide React 19 and React Native 0.78 or later. Some components have platform-specific props and behavior, so use the React Native documentation rather than assuming a Web component’s API is identical.

For the optional Expo QR scanner, install expo-camera and use the package’s separate scanner entry. Camera permission is requested after an explicit scan action, and scanned content is returned to the app for it to validate and display.

See @qzlcorp/react-native on npm and the official documentation for setup details and the component catalog.

A practical way to adopt a design system

You don’t have to redesign an entire application to begin using shared foundations. A gradual rollout can make adoption easier to review:

  1. Start with a repeated pattern. Choose a button, form, card, or other component that appears in several places.
  2. Check the platform guidance. Use the Web or React Native API that matches your target, and review its accessibility and interaction behavior.
  3. Apply the foundations consistently. Use the shared tokens and themes as a baseline, then customize intentionally where your product needs a distinct treatment.
  4. Test real states and screen sizes. Review loading, empty, error, and success states—not just the default appearance—and check the experience on the devices your users rely on.
  5. Expand when the pattern works. Reuse the approach in another part of the product and document any design choices specific to your team.

This keeps a design system practical: it can reduce repeated implementation work and visual drift without forcing every product into the same layout.

Why open source?

At Q.Z.L Corp, we believe useful developer tools should be shared. Developers repeatedly face the work of maintaining consistency, accessible interactions, reusable components, and a coherent experience across platforms. We created QZL Design Library to improve that work in our own products; by open-sourcing it, we hope other teams can use and adapt the same foundations.

The project is available under the MIT License. Explore the code, report issues, share feedback, or contribute through the QZL Design Library repository.

Explore QZL Design Library

We’re proud to share the QZL Design Library with the community. We hope it helps you build interfaces that feel consistent, accessible, and distinctly your own.

Related Posts

Introducing Typed-i18n, a Type-Safe Internationalization for TypeScript Apps

Explore @qzlcorp/typed-i18n — a zero-dependency, TypeScript-first i18n library with module-based organization, compile-time type safety, and scalable code-splitting.

@qzl/typed-i18n — Our Open-Source Typed i18n Library is Gaining Traction

QZ-L.com is proud to announce our open-source typed internationalization library is being adopted by developers worldwide. Thanks for your support!

Introducing the QZ-L Public API — Integrate URL Shortening into Your Applications

Build with qz-l. Create, manage, and track shortened links programmatically with our fully-featured public API. Complete interactive documentation included.