Displays Beta

One block vocabulary for every screen, from a glasses lens to a desktop

Beta. The Device SDK is live for design partners: Dopl issues your project's keys while the developer portal is being built, and @dopl/sdk is available on request. Agents that act for one signed in Dopl user can use the hosted MCP server instead.

Your agent describes a screen as a list of display blocks, and each device renders them within its own limits. The vocabulary is the one Dopl uses on Even Realities G2 glasses today, where agents build screens from blocks with glasses_render through the hosted MCP server. The Device SDK uses it on every device that publishes present.display, and adds images.

Blocks

BlockFieldsLimits
headingtext120 characters
textcontent, optional tone (muted or strong), lines, brightness, border2,000 characters, 1 to 40 lines, brightness 0 to 4
fieldsrows of label and value12 rows
listitems, optional style: number20 items of 200 characters
choiceoptions of label, description, recommended, why2 to 12 options, one choice block per screen
progressvalue from 0 to 1, optional label
tablecolumns and rows2 to 4 columns, 10 rows
divider
spaceroptional lines1 to 4 lines
imageurl (https), alt, optional width and heightalt is required

A screen holds up to 24 blocks, and every block has an id unique on that screen.

Fitting each device

Each device's present.display descriptor states its limits, such as the number of blocks and the bytes of text it can show. The G2 lens, for example, is 576 by 248 pixels, monochrome and holds 12 blocks. When a screen is too large, the profile's overflow applies: with truncate, Dopl keeps the first blocks that fit and cuts the text of heading and text blocks to an exact prefix.

Planned

Saved templates with {{var}} placeholders, a preview of each device's screen in the developer portal, and your own on device renderer, such as an Even Hub plugin under your brand, with Dopl handling transport and auth.

Build a custom display walks through a full example.