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.
1. Compose the blocks
Build the screen from the block vocabulary. Every block needs an id that is unique on the screen.
[
{
"id": "title",
"type": "heading",
"text": "Flight UA 212"
},
{
"id": "info",
"type": "fields",
"rows": [
{
"label": "Gate",
"value": "B14"
},
{
"label": "Boards",
"value": "9:40"
}
]
},
{
"id": "status",
"type": "progress",
"value": 0.6,
"label": "Boarding"
}
]2. Deliver it
show delivers the blocks with the display intent, so only devices that publish present.display are considered.
await dopl.show("usr_123", { blocks });3. Check the limits
The device's present.display descriptor states how many blocks and how many bytes of text it can show. Read it from the device that the exchange and List connections return. When a screen is too large, Dopl keeps the first blocks that fit and cuts their text to an exact prefix, unless the profile's overflow says otherwise.