Metric card

Metric card is a Metrics block from Orvain UI, built for React and Vue with a matching Figma frame.

Best for

One headline figure with the months behind it: point at a month and it becomes the figure

Anatomy

Icon chip, title and a 6 or 12 month control · key figure with its change · month, average and highest · tick bars with the latest in the accent · legend and footer link

MCPConnect the MCP server

Monthly spending

$27,496
up 12.4%, worse vs September
  • October 2026
  • Average $23,978
  • Highest Oct 2026

Monthly spending, November 2025 to October 2026
CategorySpending
November 202522,140
December 202525,860
January 202621,370
February 202620,915
March 202623,480
April 202622,760
May 202624,105
June 202623,390
July 202625,720
August 202626,040
September 202624,465
October 202627,496
  • October 2026$27,496
  • 12-month average$23,978

In the Orvain Library

Get Metric card for your product

The block’s code in React and Vue, its frame in the Figma file, and the Orvain MCP so your AI tools build with it. Part of every Library plan, alongside every other block.

  • React
  • Vue
  • Figma frame
  • Orvain MCP

About this block

Part of Metrics

What’s inside

05parts

The pieces it is built from. Keep them all, or drop the ones your product doesn’t need.

  1. Icon chiptitle and a 6 or 12 month control
  2. Key figurewith its change
  3. Month, average and highest
  4. Tick barswith the latest in the accent
  5. Legend and footer link

Responsive behaviour

560 px

Drawn at this width and never stretched past it. Below it, controls, text and spacing step down from the box the block sits in, not the window.

1440pxDesktop · 12 columns

When to use it

Where Metrics earns its place

Reach for Metrics

  • The top row of a dashboard, where each tile answers a single question
  • A report someone scans before deciding whether to open the table underneath
  • Comparing two series across a few categories, with a legend that can switch one off
  • Looking for a pattern across two axes, such as hour against weekday

Reach for something else

  • The reader needs the individual records: a chart shows shape and a table shows rows, so link one to the other rather than asking the chart to do both
  • There are only two or three values to compare; write them as a sentence, because a chart of three bars costs more attention than it returns
  • An operational signal that has to be acted on within seconds: a status page or an alert is the right surface, since a trend chart is read rather than watched

Accessibility

06to keep

What the block ships with. Hold on to these as you make it yours.

  • Named controlsEvery icon-only button keeps a text label, so a screen reader can say what it does.
  • Keyboard firstEvery control is reachable with Tab, and its focus ring stays visible.
  • More than colourA state never rides on colour alone; a mark or a word goes with it.
  • Contrast holdsRetheme freely, but keep text at or above the contrast it ships with.
  • Calm motionFor visitors who ask for reduced motion, things simply appear.
  • Room to hitTargets stay at least 24px, with space between neighbours.

Notes for AI

1 line

Is all your assistant needs. With the Orvain MCP connected, it builds the block from your own tokens and components.

Add the Orvain “Metric card” block to this page: icon chip, title and a 6 or 12 month control, key figure with its change, month, average and highest, tick bars with the latest in the accent, legend and footer link.

Works in
Connect the MCP

Questions about Metric card.

What is the Metric card block?

Metric card is a Metrics block from Orvain UI, built for React and Vue with a matching Figma frame. Best for one headline figure with the months behind it: point at a month and it becomes the figure.

What is the Metric card block made of?

Is the Metric card block responsive?

Is the Metric card block accessible?

How do I add the Metric card block to my project?

When should I not use a Metrics block?

More Metrics blocks

All Metrics

Monthly rows

A short run of months you read down, like a table that draws

Ranked bars

Two series across a few categories: a legend that also switches them off

Day stack

A week of tracked time: what was booked and what was left

Donut breakdown

Where a total went: five parts at most, each named beside its share

Area trend

A running level over a year, with what is forecast set apart

Launch plan

A plan of tasks over weeks: what is done, what is late and where today falls

Hour heatmap

When in the week people show up, hour by hour

Diverging months

Money in against money out, month by month, with the balance

KPI card row

Four headline numbers over the same period, side by side

Figure strip

A few related figures read as one line, each against the period before

This week vs last week

A day-by-day comparison with the week before

Forecast with a target

Whether the year will land on its goal, with the likely range

Latency

A response time against its limit, with the traffic behind it

Noise level

A live reading on a fixed scale, from low to high

Score gauge

A score out of a total that is built from parts

Sign-up funnel

People moving through ordered steps, and who left at each

Service uptime

The health of a few services day by day, with the incidents behind it

The Orvain Dispatch

Premium components, free in your inbox.

Join the Orvain Dispatch and get production-ready components, free to keep: React and Vue code plus the Figma frame, yours to ship.

Just components, never spam. You can unsubscribe anytime.