Skip to content


The roadmap is a living document, the priorities will likely change, but the list below should give some indication of our plans for the next releases.


MUI is community-drivenβ€”issues that resonate most with the community get the most attention. Please upvote (πŸ‘) on GitHub the issues you are most interested in. Thank you for participating in the developer survey.

Quarterly roadmap

Our GitHub project's roadmap is where you can learn about what features we're working on, what stage they're at, and when we expect to bring them to you:

  • MUI Core. This repository focuses on empowering the creation of great design systems with React, as well as providing two ready to use themes (Material Design so far, another one coming in the near future).
  • MUI X. This repository focuses on providing advanced React components. Some of the features are MIT licensed, others are available under a commercial license.
  • MUI Design kits This repository focuses on providing the components for designers on Figma and other design tools. It's a great place to leave feedback, feature requests, and ask questions.


Here are the top priorities:

  • More components. 🧰 We have to strictly prioritize as developing a fully-fledged component takes a considerable amount of time. We apply the following strategy:
    • Identify frequently needed components. There are many resources we leverage for this: the developer survey answers, GitHub issue upvotes, Algolia search volume, Google search volume, documentation usage, npm downloads, etc.
    • Prioritize the creation of frequently needed components.
    • Encourage the usage of third-party components if they already exist and are well maintained.
  • Design. πŸŽ€ We are relatively up-to-date, but the Material Design guidelines are evolving. So should we. We also plan to implement a second design.
  • Better customization. πŸ’… We want to make component customization intuitive, no matter if you are using global CSS or styled-components:
  • Better documentation. πŸ“š No solution is complete without great documentation.
  • Performance. πŸš€ React abstraction has a cost. The more components you render, the slower your page will be. You will notice stark differences when rendering a large table or list.
  • Bundle size. πŸ“¦ You can follow our progress with report. Please pay special attention to the cost of the individual modules under "Exports Analysis".
  • TypeScript. πŸ“ We are continuously improving the definitions. The codebase is mostly written in JavaScript with manually authored .d.ts definitions. While we do not plan a migration effort as a standalone effort, new modules are written in TypeScript.
  • Accessibility. ♿️ We have relatively few accessibility issues, but we are eager to address them all. We would appreciate the help of accessibility experts.

New components

Here are the components we will work on being supported in the MUI ecosystem:

  • βœ… Released as stable
  • πŸ§ͺ Not too far from becoming stable, already released as unstable
  • πŸ›  Work in progress, will be or already released as unstable
  • ⏳ Planning to build
Name Product Status
Advanced Layout MUI X ⏳
Carousel MUI X ⏳
Charts MUI X πŸ§ͺ
Data Grid MUI X βœ…
Date Picker MUI X βœ…
Time Picker MUI X βœ…
Date Time Picker MUI X βœ…
Date Range Picker MUI X βœ…
Time Range Picker MUI X ⏳
Date Time Range Picker MUI X ⏳
Dropdown MUI Core ⏳
Dropzone MUI X ⏳
File Upload MUI X ⏳
Gantt Chart MUI X ⏳
Gauge MUI X ⏳
Image MUI Core ⏳
Masonry MUI Core πŸ§ͺ
Navbar MUI Core ⏳
Nested Menu MUI X ⏳
NProgress MUI Core ⏳
Numeric Input MUI Core ⏳
Rich Text Editor MUI X ⏳
Scheduler MUI X ⏳
Scrollspy MUI Core ⏳
Sparkline MUI X ⏳
Timeline MUI Core πŸ§ͺ
Tree select MUI X ⏳
Tree View MUI X βœ…
Window Splitter MUI X ⏳