Stat list widget

Up to six label and value rows in one card. Best for compact dashboards — MRR, subscribers, trials — where a chart would say less.

Fields

Field	Type	Notes
`template`	string	Required. Must be `"stat_list"`
`stat_rows`	object[]	Required. Between 1 and 6 rows, drawn in the order you send them. Replaced wholesale on PATCH — re-send the full list (why)
`stat_rows[].label`	string	Required. Non-blank, max 32 characters. The left-hand caption
`stat_rows[].value`	string	Required. Non-blank, max 32 characters. A string, not a number — rendered exactly as sent
`stat_rows[].unit`	string	Rendered after the value. Max 16 characters
`label`, `subtitle`, `icon`, `accent_color`, `background_color`, `text_color`	string	Shared content fields — see the API reference

Example: SaaS dashboard

PATCH /widgets/saas-dashboard

{
  "content": {
    "template": "stat_list",
    "label": "April",
    "icon": "chart.bar.fill",
    "accent_color": "indigo",
    "stat_rows": [
      { "label": "MRR",    "value": "$8 333", "unit": "USD" },
      { "label": "Subs",   "value": "412" },
      { "label": "Trials", "value": "37" },
      { "label": "Churn",  "value": "1.2",    "unit": "%" }
    ]
  }
}

Behavior

Values are strings, so formatting is yours to decide and yours to keep consistent: the currency symbol, the thousands separator, the number of decimals. Nothing is rounded or abbreviated on device, which is the whole reason to choose this template over value — but it also means a long value is a long value, and 32 characters of it will not fit on a small widget.

How many rows actually render depends on the placement. Medium and large Home Screen widgets show all six by default; the small widget shows four, and the Lock Screen rectangular shows three, packing rows two-up to reach six when every value is very short. Users can change this per widget in the PushWard app: Compact packs two columns to surface up to six rows on any size, at the cost of truncated labels on the smaller placements, and Comfortable keeps one column with larger rows and shows fewer of them. Put the row that matters most first — it is the one that survives every placement.

Coming in app version 1.6

This section describes a feature in an app update that's pending App Store review. It unlocks here automatically once the update is live.

Row timers

A row can carry a timer instead of a static trailing value, which turns that row into a live readout — time until a maintenance window, time since the last successful backup — that keeps moving between pushes.

Field	Type	Notes
`stat_rows[].timer.date`	string	Required when `timer` is present. RFC 3339, after 2000-01-01 and no more than 366 days ahead. A past date counts up, a future date counts down
`stat_rows[].timer.style`	string	`timer` (the default) ticks like `01:23:45`; `relative` renders a coarse unit like `2 min`

A backup row that counts up on its own

{
  "content": {
    "template": "stat_list",
    "label": "Backups",
    "stat_rows": [
      { "label": "Last run", "value": "12 min ago", "timer": { "date": "2027-05-10T08:00:00Z", "style": "relative" } },
      { "label": "Repos",    "value": "14" },
      { "label": "Failed",   "value": "0" }
    ]
  }
}

ℹ Info

value stays required on a row that carries a timer, and it stays the static fallback: builds released before 1.6 render it and ignore the timer. Send the text the value had at push time ("12 min ago"), not a placeholder — an older phone shows exactly that string until the next update.