Components

One design system, drawn natively everywhere

Every OpenVibe component is described by what it is: its parts, the tokens they wear, its states, and how it reads to a screen reader. The web draws it with the kit; an Android or iOS app draws the same component with its own views, so an app is never a web page in a frame.

Numbers

A strip of real numbers; zero and unknown values are left out. A number with a link makes its whole tile the link.

watching now
1,204
people chatting
48
streams live
12

Parts and their tokens

  • tilebackgroundcolor.bg.raisedlinecolor.line.baseradiusradius.md
  • valuecolorcolor.text.primarysizetype.size.titleweighttype.weight.heavytabular figures
  • labelcolorcolor.text.mutedsizetype.size.caption

How it behaves

Role
description list (label: value)
Props
items* label * required
States
default
Name
each label with its value
Keys
a linked tile is one Tab stop
Target
the tile
Phone
one strip that scrolls sideways
Computer
the same

Code

The same component as data: a server sends this, the web renders it with kit.stats, and a native app with its own view.

// A kit document (JSON). The web renders it with openvibe-shared/components:
//   components.render(doc, kit)  →  kit.stats(…)
{
  "type": "stats",
  "props": {
    "items": [
      [
        1204,
        "watching now"
      ],
      [
        48,
        "people chatting"
      ],
      [
        12,
        "streams live",
        "/components?c=stats"
      ]
    ]
  }
}

Shared interfaces

Web, Android and iOS definitions for the navigation, composer, sheets, settings and motion used across OpenVibe. See the whole registry, or read it as JSON at /api/v1/components.

Kit documents: screens as data

A screen can be sent as a tree of these components, for example { "type": "rail", "children": [{ "type": "card", … }] }. Every OpenVibe client renders the same document with its own views, so a screen can change without an app release (the server-driven UI pattern of Airbnb and DivKit). Documents are checked strictly: known components and props only, typed values, which children each takes, a size limit, and https or same-site links.

The specs as JSON The tokens they wear