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
Parts and their tokens
- tilebackground
color.bg.raisedlinecolor.line.baseradiusradius.md - valuecolor
color.text.primarysizetype.size.titleweighttype.weight.heavytabular figures - labelcolor
color.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
Jetpack Compose, on the theme file from Tokens (Android): Material 3 roles for colour, OvScale for sizes.
// OpenVibe kit for Jetpack Compose: add the theme file from openvibe.design/tokens (Android) and wrap the app in
// MaterialTheme(colorScheme = if (isSystemInDarkTheme()) VibeDarkColorScheme else VibeLightColorScheme) { … }
enum class OvKind { Primary, Quiet, Danger }
enum class OvNoticeKind { Ok, Info, Warn, Error }
@Composable
fun OvStats(items: List<Pair<String, String>>) {
LazyRow(horizontalArrangement = Arrangement.spacedBy(OvScale.SpaceSm), contentPadding = PaddingValues(horizontal = OvScale.SpaceLg)) {
items(items) { (value, label) ->
Surface(shape = RoundedCornerShape(OvScale.RadiusMd), border = BorderStroke(1.dp, MaterialTheme.colorScheme.outlineVariant)) {
Column(Modifier.widthIn(min = 104.dp).padding(horizontal = 14.dp, vertical = 8.dp).semantics(mergeDescendants = true) {}) {
Text(value, fontWeight = FontWeight.ExtraBold, fontSize = OvScale.TypeSizeTitle, style = LocalTextStyle.current.copy(fontFeatureSettings = "tnum"))
Text(label, fontSize = OvScale.TypeSizeCaption, color = MaterialTheme.colorScheme.onSurfaceVariant)
}
}
}
}
}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.