Add Stat component

[oliviertassinari]

• I have searched the issues of this repository and believe that this is not a duplicate.

Summary 💡

Display one number on a dashboard.

Examples 🌈

  <Stat>
    <StatLabel>Avg. Open Rate</StatLabel>
    <StatNumber>58.16%</StatNumber>
    <StatHelperText>
      <StatArrow type="increase" />
      5.4%
    </StatHelperText>
  </Stat>

This is a fictional example, it's not meant to be the final design nor API

Motivation 🔦

Many developers use Material-UI to build dashboards. For such an item, it's very frequent to have to display stats.

Benchmarks

• Public: https://mui-org.notion.site/Stat-component-cbf8ec1d45a34f3fadd6b16f21114487
• For edits: https://www.notion.so/mui-org/Stat-component-cbf8ec1d45a34f3fadd6b16f21114487

[eps1lon]

I don't see this useful in a component library. The domain has a major impact on how this information is relayed and I doubt we'll make meaningful component that covers all these use cases with anything other than a bare component that doesn't actually do anything without proper customization.

Note that your "benchmark" includes a custom <meter> implementation that is a very specific kind of Stat (it's also listed twice). It does not cover your issue which is missing a description anyway. The concept of "statistic" is so generic that I can't imagine an abstract UI for. Last I remember we still follow: No abstraction is better than the wrong abstraction.

As far as I can tell all these components are just styled

<dl>
  <dt>Some stat</dt>
  <dd>The value</dd>
</dl>

This might make sense in Material design but if we go away from Material design to more generic components then this won't be helpful.

[oliviertassinari]

@eps1lon Fair feedback. I'm have a couple of items on Trello that I'm working on bringing to the GitHub issues so we can collect feedback from the community, to get an idea of the traction we can get for each item. This is part of the effort to work on the roadmap.

[eps1lon]

we can collect feedback from the community, to get an idea of the traction we can get for each item. This is part of the effort to work on the roadmap.

The wording of the issue implies nothing of the sorts.[RFC] Stat component with a discussion label seems far more appropriate. Right now people can't vote for a specific feature.