MUI Toolpad components

[oliviertassinari]

While it's way too early to work on this, in the future where https://github.com/mui/mui-toolpad is a success, I believe that we will get requests for a set of Figma components that are compatible with the components available in Toolpad. Sure, the components in Toolpad will be close to the ones we already provide in MUI Core and MUI X, but there will likely be a higher level.

From a pricing perspective, I wonder if it should either be free or be priced like any other seat of MUI Toolpad. Maybe the former would make more sense?

Benchmark

• https://community.retool.com/t/figma-components-for-retool/10670/2

Context

• https://mui.zendesk.com/agent/tickets/3911

  I am a Design leader at YYY. Our development team has elected to use MUI as the UI Kit for our internal tools. I wanted to know if we wanted to purchase MUI Figma licenses how many we would need. We would have 4 total system’s designers who would have access to edit the MUI Library. We would have 10-20 UX Designers who would be able to pull the MUI library into their files as assets.

cc @prakhargupta1

[prakhargupta1]

The need for components in Figma looks to me like an enterprise requirement as there would be additional work for licensing and component maintenance. It could be in 1st paid tier.

[adrianmanea]

Happy to contribute and design some pre-built components for the Toolpad! Maybe create a label in the Issues section for such requests.

[oliviertassinari]

@adrianmanea We have time, I think 2-3 years before it starts to be really requested. By definition, Toolpad goes after use cases when you don't want to subscribe to the rigorous development process, with a CI, a designer, and so on. I think that we would need to have both market traction and started to be used for less YOLO use cases for the Figma support to be relevant.