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.

Section

A card with a small heading for one part of a page or a group of settings; a note is one muted line under the title.

Notifications

Saved to your account

You will hear when someone you follow goes live.

Parts and their tokens

  • panelbackgroundcolor.bg.raisedlinecolor.line.baseradiusradius.md
  • titlecolorcolor.text.mutedsizetype.size.captionweighttype.weight.heavy
  • note optionalcolorcolor.text.mutedsizetype.size.meta

How it behaves

Role
region named by its heading
Props
id title count note * required
States
default
Name
its title
Keys
none of its own
Phone
full width
Computer
in its column

Code

The same component as data: a server sends this, the web renders it with kit.section, 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.section(…)
{
  "type": "section",
  "props": {
    "title": "Notifications",
    "note": "Saved to your account"
  },
  "children": [
    {
      "type": "notice",
      "props": {
        "kind": "info",
        "text": "You will hear when someone you follow goes live."
      }
    }
  ]
}

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