Data source
Where data comes from and which fields update. One source can serve multiple cards.
VAO PUSH / GUIDES
Turn a data source into something worth a daily glance.
Where data comes from and which fields update. One source can serve multiple cards.
How fields are arranged and displayed. Drafts and published designs stay separate.
Lets a device read a published card. Import codes belong to their server.
Create a card in My Cards in the Web console. Use a new data source or choose an existing one.
| Input method | How it works |
|---|---|
| Read JSON / API | Provide a public HTTPS JSON URL, authentication, and field mappings. Your server fetches it periodically. |
| Push data from a tool | A script sends JSON with PUT to the source-specific address, replacing the entire current state. |
{
"fields": {
"progress": {
"type": "percent",
"label": "Progress",
"value": "68"
},
"status": {
"type": "text",
"value": "In progress"
}
}
}This fictional example tracks photo processing. Numeric values use decimal strings; bind the progress field to show completion.
Choose real fields, adjust labels, typography, and layout, and preview different sizes. Use visual controls for common changes, or advanced layout and structured JSON for more complex designs. Cards do not execute arbitrary web code.
Daily data changes need no design republishing. Compatible design updates preserve device-specific tweaks. The App can also create simple templates for recent messages.
Successful data collection does not mean the Home Screen has refreshed. The system schedules widget updates, and offline devices may retain the last valid content.
Card deletion first shows its impact and preserves the data source and other cards. A source can be deleted only when no cards reference it, including unpublished drafts.