The roadmap is a living document, and it is likely that priorities will change, but the list below should give some indication of our plans for the next major release, and for the future.
Material-UI 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.
Here are the top priorities:
- 1.0 - More components. 🧰 This is challenging to address, 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.
- 0.5 - Better customization. 💅 We want to make our component customization intuitive, no matter if you are using global CSS or styled-components:
- Use styled-components by default: #6115.
- Allow the use of the Box props in all the core components: #15561.
- Allow the usage of dynamic theme variants and colors: #15573 & #13875.
- Allow the use of the components without any styles: #6218.
- Improve the support of custom breakpoints: #11649
- Explore the integration with theme-specification, by @jxnblk.
- 0.3 - Better documentation. 📚 This is a broad topic. The focus is on the following areas:
- Page documentation rating 🥇🥈🥉. We will integrate a rating module in all our documentation pages. This way, we can collect high-quality data points and prioritize the pages that need the most to be improved.
- Templates. They get people started really quickly, we need more of them!
- Beginner tutorials & Video lessons.
- 0.2 - 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.
Performance is all about doing less work. We can leverage the following:
- Make the core faster.
- Avoid re-rendering. It's the responsibility of the user to prune the React rendering tree efficiently, as most of our APIs are too low level to implement efficient memoization (React.useMemo, React.memo). If you find a good opportunity for it, let us know, and we will be happy to work with you on the problem.
- Avoid rendering. We have documented how to implement virtualization for the Table components. It's important to consider it above 100 items.
- 0.2 - Bundle size. 📦 You can keep track of our progress following bundlephobia.com report. It's a continuous effort – v4 was 18% smaller than v3, while adding new features. We are eager to find new bundle size reduction opportunities. We hope we can leverage these two in the future:
- 0.2 - TypeScript. 📏 There are two dimensions to this problem:
- 0.2 - Accessibility. ♿️ We have relatively few accessibility issues, but we are eager to address them all. We would appreciate the help of accessibility experts.
- 0.2 - Material Design Update. 🎀 We are relatively up-to-date but the material design specification is evolving, so should we.
Here are the components we will work on being supported in the Material-UI ecosystem, no matter if they are part of the community edition (MIT license) or Material-UI X, a paid extension for enterprises:
- 🧪 Close to becoming stable, already released as unstable
- 🛠 Work in progress, will be or already released as unstable
- ⏳ Planning to build
- ⭐️ We will make some of the features available in Material-UI X (non-MIT)
|Date Range Picker||🛠⭐|
|Data Grid - Column pinning||⏳⭐️|
|Data Grid - Nested row||⏳⭐️|
|Tree View - Multiselect||🛠⭐️|
|Tree View - Checkbox||⏳⭐️|
|Tree View - Drag & Drop||⏳⭐️|
|Tree View - Virtualization||⏳⭐️|
|Rich Text Editor||⏳⭐️|
⚠️ Disclaimer: We operate in a dynamic environment, and things are subject to change. The information provided is intended to outline the general framework direction, for informational purposes only. We may decide to add or remove new items at any time, depending on our capability to deliver while meeting our quality standards. The development, releases, and timing of any features or functionality remains at the sole discretion of Material-UI. The roadmap does not represent a commitment, obligation, or promise to deliver at any time.