index
int64 0
0
| repo_id
stringlengths 16
181
| file_path
stringlengths 28
270
| content
stringlengths 1
11.6M
| __index_level_0__
int64 0
10k
|
|---|---|---|---|---|
0 | petrpan-code/mui/material-ui/docs/pages/base-ui/react-textarea-autosize | petrpan-code/mui/material-ui/docs/pages/base-ui/react-textarea-autosize/[docsTab]/index.js | import * as React from 'react';
import MarkdownDocs from 'docs/src/modules/components/MarkdownDocsV2';
import AppFrame from 'docs/src/modules/components/AppFrame';
import * as pageProps from 'docs/data/base/components/textarea-autosize/textarea-autosize.md?@mui/markdown';
import mapApiPageTranslations from 'docs/src/modules/utils/mapApiPageTranslations';
import TextareaAutosizeApiJsonPageContent from '../../api/textarea-autosize.json';
export default function Page(props) {
const { userLanguage, ...other } = props;
return <MarkdownDocs {...pageProps} {...other} />;
}
Page.getLayout = (page) => {
return <AppFrame>{page}</AppFrame>;
};
export const getStaticPaths = () => {
return {
paths: [{ params: { docsTab: 'components-api' } }, { params: { docsTab: 'hooks-api' } }],
fallback: false, // can also be true or 'blocking'
};
};
export const getStaticProps = () => {
const TextareaAutosizeApiReq = require.context(
'docs/translations/api-docs-base/textarea-autosize',
false,
/textarea-autosize.*.json$/,
);
const TextareaAutosizeApiDescriptions = mapApiPageTranslations(TextareaAutosizeApiReq);
return {
props: {
componentsApiDescriptions: { TextareaAutosize: TextareaAutosizeApiDescriptions },
componentsApiPageContents: { TextareaAutosize: TextareaAutosizeApiJsonPageContent },
hooksApiDescriptions: {},
hooksApiPageContents: {},
},
};
};
| 4,100 |
0 | petrpan-code/mui/material-ui/docs/pages/base-ui | petrpan-code/mui/material-ui/docs/pages/base-ui/react-toggle-button-group/index.js | import * as React from 'react';
import MarkdownDocs from 'docs/src/modules/components/MarkdownDocsV2';
import AppFrame from 'docs/src/modules/components/AppFrame';
import * as pageProps from 'docs/data/base/components/toggle-button-group/toggle-button-group.md?@mui/markdown';
export default function Page(props) {
const { userLanguage, ...other } = props;
return <MarkdownDocs {...pageProps} {...other} />;
}
Page.getLayout = (page) => {
return <AppFrame>{page}</AppFrame>;
};
| 4,101 |
0 | petrpan-code/mui/material-ui/docs/pages/base-ui | petrpan-code/mui/material-ui/docs/pages/base-ui/react-tooltip/index.js | import * as React from 'react';
import MarkdownDocs from 'docs/src/modules/components/MarkdownDocsV2';
import AppFrame from 'docs/src/modules/components/AppFrame';
import * as pageProps from 'docs/data/base/components/tooltip/tooltip.md?@mui/markdown';
export default function Page(props) {
const { userLanguage, ...other } = props;
return <MarkdownDocs {...pageProps} {...other} />;
}
Page.getLayout = (page) => {
return <AppFrame>{page}</AppFrame>;
};
| 4,102 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/blog/2019-developer-survey-results.js | import * as React from 'react';
import TopLayoutBlog from 'docs/src/modules/components/TopLayoutBlog';
import { docs } from './2019-developer-survey-results.md?@mui/markdown';
export default function Page() {
return <TopLayoutBlog docs={docs} />;
}
| 4,103 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/blog/2019-developer-survey-results.md | ---
title: 'The 2019 MUI developer survey: here's what we discovered'
description: Your feedback helps us to build better products. Here's what we learned about your needs in our annual survey.
date: 2019-03-16T00:00:00.000Z
authors: ['oliviertassinari', 'mbrookes']
tags: ['Developer survey']
---
While we are currently working on the upcoming release of MUI v4, we need to prioritize our
roadmap for the coming year. To refine our focus, we launched a developer survey last month,
to which we received 734 contributions. Thank you for your participation!
The survey is now closed and this is a summary of the results.
The survey was broken into three sections, "Introduction", "About you" and "Your product".
## Introduction
Here we asked for the good, the bad and the ugly. Thankfully, it's mostly good, but we can focus
on the things that will make it even better.
### 1. How would you feel if you could no longer use MUI?
<img src="/static/blog/2019-survey/1.png" style="display: block; margin: 0 auto;" alt="Pie chart: 74.7% Very disappointed, 18.9% disappointed, 6.4% not disappointed." />
An overwhelming majority of respondents (over 93%), would be disappointed or very disappointed if
they could no longer use MUI. The benchmark for "very disappointed" is 40%,
so we're on the right track. Don't worry, MUI isn't going away any time soon –
we want to focus on making even more of you "very disappointed", as it were!
Curiously, the 6.4% who said they would _not_ be disappointed if they could no longer use
MUI collectively gave a Net Promoter Score of 68%, which is
[higher than that of all respondents as a whole](#5-how-likely-is-it-that-you-would-recommend-material-ui-to-a-friend-or-colleague),
so we know they love us really. 😘
### 2. Who do you think would most benefit from MUI?
This word cloud was generated with wordclouds.com.
<img src="/static/blog/2019-survey/2.png" style="display: block; margin: 0 auto;" alt="Word cloud of who would benefit most" />
Developers, developers, developers! (And "anyone" and "everyone", apparently! ) This is understandable, given the
[job role demographic](#7-which-of-the-following-best-describes-your-current-job-role)
of the majority of respondents. We'll continue to work on the developer experience, making it
easier to get started with, use, and customize MUI.
### 3. What is the main benefit you receive from MUI?
<img src="/static/blog/2019-survey/3.png" style="display: block; margin: 0 auto;" alt="Word cloud of the main benefit of MUI" />
The responses variously commented on being able to focus on the business logic, time saved,
good looking components, ease of use, design consistency, good documentation.
We'll make sure that we continue to do more of the things that benefit you the most.
### 4. How can we improve MUI for you?
We have grouped the answers into different categories.
The prefix corresponds to the number of times the concern was mentioned.
It's sorted descending, with the most important concerns first:
- 135 **More components:**
- 56 Non-specific
- 21 Date picker
- 10 Autocomplete
- 9 Layout
- 8 Table++
- 5 Carousel
- 5 Slider
- 3 Video
- 2 Calendar
- 2 Menu nesting
- 2 List - draggable
- 1 Tree view
- 1 Color picker
- 1 Dense mode
- 1 For landing pages
- 1 Group avatar
- 1 Image gallery
- 1 Image picker
- 1 Menu - dropdown
- 1 Mobile
- 1 Rating
- 1 Timeline
- 1 Transfer
- 50 **Better customization:**
- 23 Non-specific
- 15 Docs
- 8 Easier
- 3 Theme
- 1 Colors
- 36 **Better documentation:**
- 11 Non-specific
- 7 More examples
- 5 Beginner tutorials
- 4 Video lessons
- 2 API pages
- 2 Icon explorer
- 1 Best practices
- 1 Customization
- 1 Global CSS
- 1 Demo source scroll issue
- 1 Server-side rendering
- 31 **TypeScript:**
- 14 Non-specific
- 13 Migrate more demos
- 3 withStyles -> makeStyles
- 1 Rewrite
- 24 **Performance:**
- 23 Non-specific
- 1 Table
- 19 **Bundle size**
- 17 **Material Design Update**
- 16 **styled-components:**
- 10 Support
- 6 Migration
- 14 **Fewer breaking changes**
- 10 **More page layout examples**
- 9 **Theme:**
- 3 More colors
- 3 Live editor
- 1 Non-material font example
- 2 Responsive typography
- 8 **React.StrictMode support**
- 8 **React Native support**
- 6 **Accessibility:**
- 4 Non specific
- 1 Docs
- 1 SkipNav
- 6 **Hooks at 100%**
- 4 **Animations**
- 4 **Long Term Support**
- 4 **Simplification**
- 3 **Gatsby plugin**
- 3 **i18n**
- 3 **Premium themes**
- 3 **Showcase, design inspiration**
- 2 **Clear Roadmap**
- 2 **Preact support**
- 2 **Simpler: closer to DOM nodes**
- 2 **Styleless components**
- 1 **Web component integration example**
- 1 **Collect user feedback**
- 1 **Non-Material Design theme example**
- 1 **Right to left**
- 1 **Storybook addons**
- 1 **Styles: better docs**
- 1 **Testing**
### 5. How likely is it that you would recommend MUI to a friend or colleague?
<figure style="margin-inline-start: 0;">
<img src="/static/blog/2019-survey/5a.png" style="display: block; margin: 0 auto;" alt="Bar chart of raw data" />
<figcaption style="font-style: italic; text-align: center;">Raw data.</figcaption>
</figure>
<br />
<figure style="margin-inline-start: 0;">
<img style="display: block; margin: 0 auto;" src="/static/blog/2019-survey/5b.png" style="display: block; margin: 0 auto;" alt="Pie chart: 70.6% promoters, 24.8% neutrals, 4.6% detractors" />
<figcaption style="font-style: italic; text-align: center;">Result.</figcaption>
</figure>
Developers gave MUI a [Net Promoter Score](https://en.wikipedia.org/wiki/Net_Promoter)
(promoters less detractors) of 66%. Given the NPS range of -100 to +100, a "positive" score or NPS
above 0 is considered "good", +50 is "Excellent", and above 70 is considered "world class."
## About you
### 6. How did you hear about MUI?
Multiple options were allowed.
| Channel(s) | Number |
| :-------------------------- | -----: |
| Search | 344 |
| Word of mouth | 112 |
| Search, Word of mouth | 47 |
| Search, Social | 25 |
| Social | 22 |
| Blog | 14 |
| Search, Word of mouth, Blog | 11 |
<br /><br />
<img src="/static/blog/2019-survey/6.png" style="display: block; margin: 0 auto;" alt="Bar chart: 74.3% search, 29.6% word of mouth, 8.2% Social, 4.3% blog." />
### 7. Which of the following best describes your current job role?
<img src="/static/blog/2019-survey/7.png" style="display: block; margin: 0 auto;" alt="Bar chart: 358 Full-stack developers, 189 Frontend developers, 103 Entrepreneurs, 31 Beginners, 42 Other" />
No huge surprises here!
### 8. How big is your organization?
<img src="/static/blog/2019-survey/8.png" style="display: block; margin: 0 auto;" alt="Bar chart: 61 Hobby, 98 Self-employed, 181 x 2-10, 167 x 11-50, 126 x 51-500, 89 x 500 +" />
MUI is most popular with small to medium sized organisations,
perhaps because beyond a certain size, organizations have teams building their own design system and framework.
We want to continue to make it easy to use the component logic of MUI while allowing
designers to give it a bespoke look and feel for their organization.
### 9. How long have you been developing with JavaScript
<img src="/static/blog/2019-survey/9.png" style="display: block; margin: 0 auto;" alt="Bar chart: 26 x I'm just getting started!, 43 x 6 months +, 150 x 1 year +, 179 x 3 years +, 155 x 5 years, 82 x 10 years +, 47 x 15 years +" />
A nice bell curve, with the majority of developers having 1 to 5 years experience with JavaScript.
### 10. How long have you been developing with React?
<img src="/static/blog/2019-survey/10.png" style="display: block; margin: 0 auto;" alt="Bar chart: 99 x I'm just getting started!, 77 x 6 months +, 301 x 1 year +, 171 x 3 years +, 32 x 5 years - bleeding edge baby!" />
### 11. How long have you been developing with MUI?
<img src="/static/blog/2019-survey/11.png" style="display: block; margin: 0 auto;" alt="Bar chart: 160 x I'm just getting started!, 147 x 6 months +, 293 x 1 year +, 71 x 3 years +, 11 x Four years + – I'm a pioneer!" />
We missed a trick by not including "2 years +" here, so "1 year +" looks stacked.
The number of users of MUI continues to grow at a steady pace, and once on board, many
developers stick with it.
### 12. What were you primarily using before MUI?
<img src="/static/blog/2019-survey/12.png" style="display: block; margin: 0 auto;" alt="Bar chart: 55% Bootstrap, 18% Custom, 12% Other, 7% Semantic-IU, 6% Materialize, 3% React Toolbox" />
Given its relative popularity, and the move from CSS / HTML / jQuery towards front-end frameworks,
it should come as no big surprise to see that the majority of respondents were previously using Bootstrap.
Custom solutions have also been replaced by MUI as your go-to UI library, along with a
long-tail of other frameworks.
### 13. How many MUI based projects have you built?
<img src="/static/blog/2019-survey/13.png" style="display: block; margin: 0 auto;" alt="Pie chart: 10.7% I'm just getting started, 23.5% 1, 52.5% 2-5, 11.1% 6-10, 2.2% 10+" />
Over three quarters of you have built two or more projects with MUI, with 13.3% having six
or more projects under your belt. The 2.2% with ten or more, we salute you!
## Your product
### 14. What are you building?
Multiple options were allowed.
- Dashboard & admin: 70%
- UI components (design system): 40%
- Business & corporate pages: 35%
- Landing pages (product): 33%
- e-commerce: 14%
- Portfolio & resume: 12%
- Blog: 8%
Dashboards are at the top of the heap, and we've long known that many of you are building internal
systems that can't feature in [the showcase](/material-ui/discover-more/showcase/). Let us know by opening a PR
if you're bucking that trend, and have something sparkly to share! And if you're in the 40% building UI
components, we'd be happy to give you a shout out in the [related projects](/material-ui/discover-more/related-projects/)
section.
### 15. What "delivery mechanism" are you using?
Multiple options were allowed.
- Web app (e.g. create react app): 92%
- Progressive web app (with service worker): 25%
- Server-side rendering 14%
- Static web site, hosted on a CDN (e.g. Gatsby): 13%
- Desktop app (e.g. Electron): 12%
- Native mobile app (e.g. Cordova): 6%
### 16. Who are you building it for?
<img src="/static/blog/2019-survey/16.png" style="display: block; margin: 0 auto;" alt="Pie chart: 54,3% for my company, 24.9% for a client, 15.2% as a side project, 5.6% more than one of these." />
### 17. Which JS framework are you using, if any?
Multiple options were allowed.
- Create React App: 75%
- none: 17%
- Next.js: 12%
- Gatsby: 8%
Server-side rendering isn't yet very popular.
As the React ecosystem matures, we might see a big push of server-side rendering in the coming months.
### 18. What styling system are you using?
Multiple options were allowed.
- @mui/styles: 85%
- Styled components: 30%
- Good old CSS (+sass, less, etc): 24%
- CSS Modules (+sass, less, etc): 16%
- Emotion: 4%
Traditional CSS users are still prevalent (24% + 16%).
The components customization `classes` API was designed for these people.
It's also why we allow the generation of deterministic class names (_MuiButton-root_ instead of _jss113_).
However, styled components is popular. We will work on better supporting it.
## Conclusion
This data is **incredibly valuable** for our team.
Again, thank you for participating!
We want to work on the problems that resonate the most with our users.
[It's clear](#4-how-can-we-improve-mui-for-you) that we should:
1. Support more components
2. Improve the customization
3. Improve the documentation
4. Improve the static typings
5. Reduce the overhead of the library
**We will update [our ROADMAP](/material-ui/discover-more/roadmap/) in the coming days**.
We will run a similar survey next year to keep track of our progress.
If you want to continue to influence our roadmap, please upvote 👍 the issues you are the most interested in on GitHub.
<img src="/static/blog/2019-survey/vote.gif" style="display: block; margin: 0 auto;" alt="How to upvote on GitHub" />
<p class="blog-description">Help us prioritize by upvoting.</p>
| 4,104 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/blog/2019.js | import * as React from 'react';
import TopLayoutBlog from 'docs/src/modules/components/TopLayoutBlog';
import { docs } from './2019.md?@mui/markdown';
export default function Page() {
return <TopLayoutBlog docs={docs} />;
}
| 4,105 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/blog/2019.md | ---
title: 2019 in review and beyond
date: 2020-01-25T00:00:00.000Z
description: 2019 was a great year for MUI. It puts us on an exciting path to solve even greater challenges in the coming years!
authors: ['oliviertassinari']
tags: ['Company']
---
2019 was a great year for MUI.
It puts us on an exciting path to solve even greater challenges in the coming years!
## Growth
It's only with your trust that we could achieve the following outcomes in 2019. Thank you!
- 📦 From 2.2M to [3.2M](https://npm-stat.com/charts.html?package=%40material-ui%2Fcore&from=2018-11-30&to=2019-12-31) downloads per month (from 13% to [14%](https://docs.google.com/spreadsheets/d/1l5j3Xjtvm9XZtmb4ulLiWElQaXSlZlyCWT5ONrQMpBo/edit?usp=sharing) share of the React ecosystem).
- 📈 From 1.6M to 3.1M unique visitors per year on the documentation.
- ⭐️ From 43.1k to 53.3k stars, leave us [yours 🌟](https://github.com/mui/material-ui).
- 👨👩👧👦 From 1,064 to [1,581](https://github.com/mui/material-ui/graphs/contributors) contributors.
- 💰 Grew financial support by 1.76X in 2019, compared to 2018.
- 🏢 From 1.5 to 3 full-time equivalent developers, spread among multiple financially supported [core team members](/about/).
The numbers speak for themselves. 2019 was super exciting and made MUI one of the most advanced open-source, React-based, UI component libraries!
## In review
When we started 2019, we were celebrating the launch of the **first stable release** of the framework and iterating to polish it (looking at the list of breaking changes, v3 is almost identical to v1).
We thought we were almost done, and that we had done the hardest part with the release of the stable version. All we would need to do going forward was to keep up with the Material Design guidelines and fix a couple of bugs.
We soon realized that we could do way more. It was just the beginning :D.
Some of the key factors:
- The results of the [2019 Developer Survey](https://mui.com/blog/2019-developer-survey-results/) have highlighted the immense potential for working on advanced components and features, especially for enterprise users.
Developers are craving for a UI framework that they can learn once (e.g. few breaking changes, only one solution per problem) and use everywhere (e.g. comprehensive, customizable, high-quality).
- Bootstrap had successfully released [a theme store](https://themes.getbootstrap.com/).
Following this approach opened an opportunity to capture a fraction of the value MUI creates for its users, and funnel it back into R&D on the framework.
- The market for paid UI components is in the order of a couple of \$100m/year,
with dozens of companies positioned in this market.
While React is only one technology among many (jQuery, Angular, ASP.NET, Blazor, Vue, WPF, UWP, etc) with which to build a UI, but we believe that Web and React will become the dominant technology in the next 5 years for enterprises. MUI is uniquely positioned to address this market with non-MIT features.
- Building UIs should be simpler, it still too slow and complex.
Designers and developers should benefit from a more integrated experience.
- Every now and then, we witness the appearance of a new React UI component library built from scratch ([UXPin](https://adele.uxpin.com/) keeps track of some of them).
And every time we asked ourselves, "what could have we done differently to empower this library"?
We believe that starting from scratch, while maximizing freedom, is incredibly inefficient.
Most UI libraries need the same features but are implemented with a wide spectrum of accessibility, developer experience, and overall design quality.
We won't rest until we successfully unify these efforts. It's a long term mission and will probably take years. The foundation will be the release of an un-styled version of our components.
## Achievements
- We have released [v4](/blog/material-ui-v4-is-out/).
- We have introduced many new components (some in the core, some in the lab):
- [Autocomplete](/material-ui/react-autocomplete/)
- [Backdrop](/material-ui/react-backdrop/)
- [Breadcrumbs](/material-ui/react-breadcrumbs/)
- [ButtonGroup](/material-ui/react-button-group/)
- [Container](/material-ui/react-container/)
- [Link](/material-ui/react-link/)
- [Rating](/material-ui/react-rating/)
- [Skeleton](/material-ui/react-skeleton/)
- [Slider](/material-ui/react-slider/)
- [TextareaAutosize](/material-ui/react-textarea-autosize/)
- [TreeView](/x/react-tree-view/)
- We have fixed a significant number of [accessibility issues](https://github.com/mui/material-ui/issues?q=is%3Aissue+label%3Aaccessibility+is%3Aclosed).
- We have introduced global class names.
- We have migrated the whole codebase to hooks.
- We migrated all the demos to TypeScript (while also offering transpiled JS demos).
- We introduced [native tree-shaking](/material-ui/guides/minimizing-bundle-size/) support.
- We introduced [built-in localization](/material-ui/guides/localization/).
- We removed a good number of external dependencies and increased the `features/bundle size` density.
- We introduced an [icon search page](/material-ui/material-icons/).
- We released a [store for MUI](https://mui.com/store/).
## Looking at 2020
2019 was great, 2020 is going to be even more exciting!
We will continue in the same direction.
### Survey
The developer survey we ran [last year](/blog/2019-developer-survey-results/) was so insightful that we plan to run it every year.
It's a great opportunity for us to adjust the strategy and to pause to analyze the outcome of the actions we took in the previous year.
### Open source roadmap
Most of the time we work in the open. Here's our [public roadmap](/material-ui/discover-more/roadmap/).
We plan to release a new major around the end of the year (v5).
We will promote components that are in the lab to the core, migrate to styled-components, and more.
### Store
We will increase the depth of content available with more themes and templates.
We have recently released a Sketch design library, and are planning to support Figma, and Adobe XD too.
For Framer, we have made the key components available as a Framer package.
### Enterprise
We plan to release an enterprise class offering, starting with the data grid.
Enterprise features will build on the open source version of the components.
### Hiring
We are looking for a full-time Software Developer to join us!
If you want to help us onboard more full-time developers in the team, [here are a couple of ways](/material-ui/getting-started/faq/#mui-is-awesome-how-can-i-support-the-company).
Spreading the word to other developers that are looking for a great UI framework is also extremely helpful 🙌.
| 4,106 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/blog/2020-developer-survey-results.js | import * as React from 'react';
import TopLayoutBlog from 'docs/src/modules/components/TopLayoutBlog';
import { docs } from './2020-developer-survey-results.md?@mui/markdown';
export default function Page() {
return <TopLayoutBlog docs={docs} />;
}
| 4,107 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/blog/2020-developer-survey-results.md | ---
title: 'The 2020 MUI developer survey: here's what we discovered'
description: Your feedback helps us to build better products. Here's what we learned about your needs in our annual survey.
date: 2020-06-27T00:00:00.000Z
authors: ['mnajdova', 'oliviertassinari', 'mbrookes']
tags: ['Developer survey']
---
Continuing the tradition from last year, we launched a developer survey a few months ago, to which we received 1488 responses. This is twice as many as last year (734), so we thank you all for the participation!
The survey is closed and we can now give a detailed summary of the results.
Like last year, the survey was again broken into three sections: ["Introduction"](#Introduction), ["About you"](#about-you) and ["Your product"](#your-product).
## Introduction
In this section, we wanted to hear what developers think is going well, what we should keep doing, and which areas need improving to make the library even better.
### 1. How would you feel if you could no longer use MUI?
<img src="/static/blog/2020-survey/1.png" style="width: 796px; margin-top: 16px; margin-bottom: 16px;" alt="Pie chart: 73.3% Very disappointed, 21.3% somewhat disappointed, 5.4% not disappointed." />
Similar to last year, over 94% of the respondents would be disappointed if they could no longer use MUI, which is very encouraging. We will keep working hard to hopefully move more of you into the "very disappointed" category!
The number of respondents who would not be disappointed has moved down from 6.5% to 5.4%, which is technically a 17% improvement! 🙂 We'd love to understand more about those who use MUI, but would happily use other solutions, so a follow-up question might be needed next year.
### 2. How likely is it that you would recommend MUI to a friend or colleague?
<img src="/static/blog/2020-survey/2a.png" style="width: 796px; margin-top: 16px; margin-bottom: 8px;" alt="Bar chart: 0.20% - 1, 0% - 2, 0.20% - 3, 0.20% - 4, 1.02% - 5, 1.97% - 6, 8.71% - 7, 22.52% - 8, 20.88% - 9, 44.29% - 10" />
<img src="/static/blog/2020-survey/2b.png" style="width: 796px; margin-top: 16px; margin-bottom: 16px;" alt="Pie chart: 73.3% Very disappointed, 21.3% somewhat disappointed, 5.4% not disappointed." />
As last year, we again calculated the [Net Promoter Score](https://en.wikipedia.org/wiki/Net_Promoter)
(promoters less detractors). This year it is again a pretty high number 61.54%! (As the values for NPS range between -100 and +100, a "positive" score is considered "good", greater than 50 is "excellent", and above 70 is considered "world class").
### 3. Who do you think would most benefit from MUI?
<img src="/static/blog/2020-survey/3.png" style="width: 796px; margin-top: 16px; margin-bottom: 16px;" alt="Word cloud of who would benefit most" />
<p class="blog-description">This word cloud was generated with wordclouds.com.</p>
Developers are again at the center of our universe 🙂 (And "people" and "teams" in general, of course!) This is understandable, given the [job role demographic](#8-which-of-the-following-best-describes-your-current-job-role)
of the majority of respondents. We will push hard on making the experience for you even better over the next year.
### 4. What is the main benefit you receive from MUI?
<img src="/static/blog/2020-survey/4.png" style="width: 796px; margin-top: 16px; margin-bottom: 16px;" alt="Word cloud of the main benefit of MUI" />
The responses to this question are a very clear indicator to us about what we need to continue to do more of. Some of the most common points were: the range of components, ease of use, documentation quality, as well as the design. We will, of course, continue to work on all of these.
### 5. How can we improve MUI for you?
As the answers to these questions were pretty different, we grouped them into different categories and counted the different number of times the concern was mentioned. You can see all of them sorted in descending order:
<style>th { text-align: left; border-bottom: 3px solid !important; }</style>
<table>
<tr><th style="width: 40px;">306</th><th style="width: 700px;">more components</th><tr>
<tr><td>202</td><td>more components - ?</td><tr>
<tr><td>15</td><td>more components - data grid</td><tr>
<tr><td>12</td><td>more components - carousel</td><tr>
<tr><td>12</td><td>more components - charts</td><tr>
<tr><td>10</td><td>more components - lab to core</td><tr>
<tr><td>10</td><td>more components - upload</td><tr>
<tr><td>9</td><td>more components - icons</td><tr>
<tr><td>6</td><td>more components - big calendar</td><tr>
<tr><td>5</td><td>more components - layout</td><tr>
<tr><td>4</td><td>more components - navbar</td><tr>
<tr><td>4</td><td>more components - nested menu</td><tr>
<tr><td>2</td><td>more components - rich text editor</td><tr>
<tr><td>2</td><td>more components - splitter</td><tr>
<tr><td>1</td><td>more components - masonry</td><tr>
<tr><td>1</td><td>more components - nav bar</td><tr>
<tr><td>1</td><td>more components - numberpad</td><tr>
<tr><td>1</td><td>more components - onboarding</td><tr>
<tr><td>1</td><td>more components - prompt</td><tr>
<tr><td>1</td><td>more components - scrollspy</td><tr>
<tr><td>1</td><td>more components - swappable tabs</td><tr>
<tr><td>1</td><td>more components - timeline</td><tr>
<tr><td>1</td><td>more components - video player</td><tr>
<tr><td>1</td><td>more components - virtualization</td><tr>
<tr><td>1</td><td>more components - drag and drop</td><tr>
<tr><td>1</td><td>more components - dropdown</td><tr>
<tr><td>1</td><td>more components - image</td><tr>
<tr><th>189</th><th>customization</th><tr>
<tr><td>85</td><td>customization - easier</td><tr>
<tr><td>22</td><td>customization - docs</td><tr>
<tr><td>16</td><td>customization - dynamic color & variant</td><tr>
<tr><td>15</td><td>customization - improve custom themes</td><tr>
<tr><td>13</td><td>customization - provide more themes (not just Material Design)</td><tr>
<tr><td>11</td><td>customization - ?</td><tr>
<tr><td>9</td><td>customization - unstyled components</td><tr>
<tr><td>8</td><td>customization - support system in all components</td><tr>
<tr><td>8</td><td>customization - theme editor (visual tool)</td><tr>
<tr><td>2</td><td>customization - theme gallery (coming from the community)</td><tr>
<tr><th>155</th><th>docs</th><tr>
<tr><td>46</td><td>docs - ?</td><tr>
<tr><td>45</td><td>docs - more examples</td><tr>
<tr><td>33</td><td>docs - more templates</td><tr>
<tr><td>16</td><td>docs - beginner friendly</td><tr>
<tr><td>8</td><td>docs - smaller demos</td><tr>
<tr><td>8</td><td>docs - tutorials</td><tr>
<tr><td>3</td><td>docs - api integration with components</td><tr>
<tr><td>2</td><td>docs - better search</td><tr>
<tr><td>2</td><td>docs - spanish</td><tr>
<tr><td>1</td><td>docs - chinese</td><tr>
<tr><td>1</td><td>docs - translations</td><tr>
<tr><td>1</td><td>docs - detailed api</td><tr>
<tr><td>1</td><td>docs - easier discoverability of components</td><tr>
<tr><td>1</td><td>docs - generated DOM</td><tr>
<tr><td>1</td><td>docs - japanese</td><tr>
<tr><td>1</td><td>docs - more realistic examples</td><tr>
<tr><td>1</td><td>docs - nested props</td><tr>
<tr><td>1</td><td>docs - plugins</td><tr>
<tr><td>1</td><td>docs - ssr</td><tr>
<tr><th>64</th><th>performance</th><tr>
<tr><td>31</td><td>performance - ?</td><tr>
<tr><td>32</td><td>performance - bundle size</td><tr>
<tr><td>1</td><td>performance - DOM size</td><tr>
<tr><th>56</th><th>styles</th><tr>
<tr><td>19</td><td>styles - styled components</td><tr>
<tr><td>7</td><td>styles - docs</td><tr>
<tr><td>5</td><td>styles - simpler</td><tr>
<tr><td>4</td><td>styles - ?</td><tr>
<tr><td>3</td><td>styles - CSS syntax</td><tr>
<tr><td>3</td><td>styles - better dark/light switch</td><tr>
<tr><td>3</td><td>styles - emotion</td><tr>
<tr><td>3</td><td>styles - performance</td><tr>
<tr><td>2</td><td>styles - agnostic to engine</td><tr>
<tr><td>2</td><td>styles - CSS modules</td><tr>
<tr><td>2</td><td>styles - utility class names</td><tr>
<tr><td>1</td><td>styles - atomic compiled CSS-in-JS</td><tr>
<tr><td>1</td><td>styles - keep jss</td><tr>
<tr><td>1</td><td>styles - remove JSS</td><tr>
<tr><th>25</th><th>typescript</th><tr>
<tr><td>19</td><td>typescript - ?</td><tr>
<tr><td>3</td><td>typescript - docs</td><tr>
<tr><td>3</td><td>typescript - faster check</td><tr>
<tr><th>21</th><th>date picker - improve</th><tr>
<tr><th>19</th><th>react native</th><tr>
<tr><th>13</th><th>form</th><tr>
<tr><th>13</th><th>material design updates</th><tr>
<tr><th>12</th><th>animations</th><tr>
<tr><td>8</td><td>animations - ?</td><tr>
<tr><td>2</td><td>animations - docs</td><tr>
<tr><td>1</td><td>animations - declarative API</td><tr>
<tr><td>1</td><td>animations - SVG</td><tr>
<tr><th>11</th><th>test</th><tr>
<tr><td>4</td><td>test - jest</td><tr>
<tr><td>3</td><td>test - stable snapshot</td><tr>
<tr><td>1</td><td>test - ?</td><tr>
<tr><td>1</td><td>test - docs</td><tr>
<tr><td>1</td><td>test - styles</td><tr>
<tr><td>1</td><td>test - testing library integration</td><tr>
<tr><th>8</th><th>more opinionated</th><tr>
<tr><th>8</th><th>simplify</th><tr>
<tr><th>7</th><th>class components</th><tr>
<tr><th>7</th><th>mobile</th><tr>
<tr><th>7</th><th>fewer breaking changes</th><tr>
<tr><th>7</th><th>designers</th><tr>
<tr><td>2</td><td>designers - bridge design tools and code</td><tr>
<tr><td>2</td><td>designers - Adobe XD material</td><tr>
<tr><td>2</td><td>designers - Figma material</td><tr>
<tr><td>1</td><td>designers - ?</td><tr>
<tr><th>6</th><th>free vs paid balance</th><tr>
<tr><th>6</th><th>tree view - improve</th><tr>
<tr><th>6</th><th>less abstracted components</th><tr>
<tr><th>5</th><th>more abstracted components</th><tr>
<tr><th>4</th><th>accessibility</th><tr>
<tr><td>1</td><td>accessibility - ?</td><tr>
<tr><td>1</td><td>accessibility - auto id</td><tr>
<tr><td>1</td><td>accessibility - full audit</td><tr>
<tr><td>1</td><td>accessibility - more examples</td><tr>
<tr><th>4</th><th>system</th><tr>
<tr><td>1</td><td>system - CSS grid</td><tr>
<tr><td>1</td><td>system - docs</td><tr>
<tr><td>1</td><td>system - performance</td><tr>
<tr><td>1</td><td>system - rework breakpoints</td><tr>
<tr><th>3</th><th>components consistency</th><tr>
<tr><th>3</th><th>grid - improve</th><tr>
</table>
### Comparison with last year
There are a couple of noticeable differences compared to last year.
Some can be explained by our work, others by the evolution of the ecosystem.
Each item is prefixed by the multiplication factor of the pain point for 2020 relative to 2019.
Decreasing pain:
- x0: Slider. No requests. The requirements are mostly met, especially with the introduction of the range feature.
- x0.1: Strict mode. We fixed a lot of strict mode compatibility issues this year. However, since Create React App has made this mode a default, we have seen a lot more requests for it.
- x0.1: Autocomplete. We added a new component, and have resolved a large number of issues opened since. This will be moved from lab to the core in v5.
- x0.2: Fewer breaking changes. Only releasing minor versions under v4 for over a year helps a lot. However, we still need to be careful with CSS changes.
- x0.3: Accessibility. We have been able to leverage GitHub issues opened by a11y experts, often coming from large companies using MUI at scale to improve it a lot this year.
- x0.4: Material Design. We didn't do much for it this year, at least not as much as we could have. Maybe the reduction is because fewer people care? It seems that we start to resonate more with developers building custom design systems.
- x0.4: TypeScript. The continued migration of all the demos to TypeScript and of all the props to IntelliSense is paying off.
- x0.5: Date picker. We did a lot for it this year. We probably still need the range feature, and to move it into the main repository (docs migration, etc.) for consistency.
- x0.7: Performance. We didn't do much this year, so perhaps developers are leveraging React more effectively with virtualization, update pruning, etc?
Growing pains:
- ∞: Forms is a new item. It seems that we should at least work more closely with react-hook-form, formik, and react-final-form.
- ∞: Charts is a new item. Material Design even has a page dedicated to [date visualization](https://m2.material.io/design/communication/data-visualization.html).
- x5: Custom themes.
- x5: Simpler customization. We have improved customizability this year by introducing global class names and reducing the CSS specificity of some selectors. However, it seems that we are now tapping into a new audience. We need to do better.
- x1.5: Animations.
- x1.2: React native. We still have no plans for it. The [market is too small](https://npm-stat.com/charts.html?package=react-dom,react-native) to make it sustainable with our model.
- x1.1: More components. The more we offer, the more developers ask for! We will try to help solve this with the enterprise version, both because it's the best model we have found that can sustain the development of advanced components, and because it allows us to reinvest in the open source components. The first early access will land this year.
### 6. What are your key criteria when choosing a UI library?
<img src="/static/blog/2020-survey/6.png" style="width: 796px; margin-top: 16px; margin-bottom: 8px;" alt="Bar chart: 21.99% The design, look & feel, 21.64% Documentation quality, 16.38% Customizability, 8.42% TypeScript integration, 6.89% Comprehensiveness, 5.35% Enterprise ready, 4.68% Bundle size, 4.92% Popularity, 4.45% Accessibility, 2.62% Documentation quality, 1.88% Offered support & help, 0.12% Performance, 0.67% Other." />
The number of answers was limited to 3.
## About you
### 7. How did you hear about MUI?
<img src="/static/blog/2020-survey/7.png" style="width: 796px; margin-top: 16px; margin-bottom: 8px;" alt="Bar chart: 50.65% Search, 26.18% Word of mouth, 10.76% Social, 5.10% Blog, 7.31% Other." />
### 8. Which of the following best describes your current job role?
<img src="/static/blog/2020-survey/8.png" style="width: 796px; margin-top: 16px; margin-bottom: 8px;" alt="Bar chart: 52.18% Full-stack developer, 27.11% Frontend developer, 11.65% Entrepreneur (I do it all), 3.47% Beginner learning web development, 1.23% Backend Developer, 1.16% UX Designer, 0.34% Student, 0.20% CTO, 2.66% Other." />
This was expected :)
### 9. How big is your organization?
<img src="/static/blog/2020-survey/9.png" style="width: 796px; margin-top: 16px; margin-bottom: 8px;" alt="Bar chart: 12.30% Hobby / side project, 13.40% Self-employed, 35.60% 2-5 people, 16.10% 6-10, 10.30% 11-20, 5.10% 21-50, 2.50% 51-100, 4.60% 100+" />
It seems we are consistently popular with small to medium-sized organizations, so we will keep working on the ease of use of the components, while at the same time, allowing designers to style them to match their organizations' brand.
### 10. How long have you been developing with JavaScript
<img src="/static/blog/2020-survey/10.png" style="width: 796px; margin-top: 16px; margin-bottom: 8px;" alt="Bar chart: 3.60% I'm just getting started!, 7.40% 6 months +, 20.80% 1 year +, 27.80% 3 years +, 24.30% 5 years +, 9.80% 10 years +, 4.10% 15 years +, 2.30% 20 years +" />
We can see the normal distribution of developer experience here, where most have moderate level of experience (between 1 and 5 years).
### 11. How long have you been developing with React?
<img src="/static/blog/2020-survey/11.png" style="width: 796px; margin-top: 16px; margin-bottom: 8px;" alt="Bar chart: 10.70% I'm just getting started!, 15.60% 6 months +, 24.60% 1 year +, 21.40% 2 years +, 23.10% 3 years +, 4.60% Bleeding edge baby! 5 years +" />
### 12. How long have you been developing with MUI?
<img src="/static/blog/2020-survey/12.png" style="width: 796px; margin-top: 16px; margin-bottom: 8px;" alt="Bar chart: 20.50% I'm just getting started!, 24.90% 6 months +, 28% 1 year +, 17.40% 2 years +, 7.50% 3 years +, 1.70% I'm a pioneer! 4 years +" />
### 13. What were you primarily using before MUI?
<img src="/static/blog/2020-survey/13.png" style="width: 796px; margin-top: 16px; margin-bottom: 8px;" alt="Bar chart: 47.08% Bootstrap, 16.04% Custom system, 13.68% Started with MUI, 6.67% Angular Material, 4.44% Semantic-UI, 3.19% Ant Design, 8.89% Other" />
Similar to last year, it seems that most respondents were previously using Bootstrap. We can see also that custom solutions, as well as some other frameworks, were replaced with MUI.
### 14. How many MUI based projects have you built?
<img src="/static/blog/2020-survey/14.png" style="width: 796px; margin-top: 16px; margin-bottom: 8px;" alt="Bar chart: 11.50% 0 (I'm just getting started), 23% 1, 54.80% 2-5, 7.80% 6-10, 2.90% 10+" />
## Your product
### 15. What are you building?
<img src="/static/blog/2020-survey/15.png" style="width: 796px; margin-top: 16px; margin-bottom: 8px;" alt="Bar chart: 23.43% Enterprise application, 20.31% Dashboard admin app, 7.40% A design system, 7.40% A set of UI components, 7.37% playing with tech, 7.34% A prototype, 6.40% Landing page, 5.41% e-commerce site, 4.80% CMS, 3.59% Portfolio or resume, 1.88% Blog, 4.69% Other" />
Enterprises and dashboards are at the top of the heap, and yes, we know that for many of you, the systems you are building are internal, but if you have something that you would like to share as part of [the showcase](/material-ui/discover-more/showcase/), let us know by opening a PR. Also for those of you building UI components, we'd be happy to give you a shout out in the [related projects](/material-ui/discover-more/related-projects/)
section.
### 16. What "delivery mechanism" are you using?
<img src="/static/blog/2020-survey/16.png" style="width: 796px; margin-top: 16px; margin-bottom: 8px;" alt="Bar chart: 68.37% Single page app (Create React App, etc), 18.24% Server-side rendered website (Next.js, Gatsby, etc), 6.22% Desktop app (Electron, etc), 4.65% Native mobile app (Cordova, etc), 0.10% React Native, 2.40% Other" />
### 17. Who are you building it for?
<img src="/static/blog/2020-survey/17.png" style="width: 796px; margin-top: 16px; margin-bottom: 8px;" alt="Pie chart: 55.17% For my company
22.86% For a client, 16.94% Side project, 5.03% More than one of these." />
### 18. Which JS framework are you using, if any?
<img src="/static/blog/2020-survey/18.png" style="width: 796px; margin-top: 16px; margin-bottom: 8px;" alt="Pie chart: 57.34% Create React App, 16.40% Custom webpack, 12.35% Next.js, 5.40% Gatsby, 8.51% Other." />
### 19. What styling system are you using?
<img src="/static/blog/2020-survey/19.png" style="width: 796px; margin-top: 16px; margin-bottom: 8px;" alt="Pie chart: 53.84% MUI styles (JSS), 20.41% Styled components, 13.01% Good plain CSS, 8.31% CSS Modules, 1.96% Emotion, 0.59% scss, 0.59% sass, 0.09% less, 1.19% Other" />
The response seems to be similar to the one from the last year's survey, so we will push with better support for styled components.
### 20. Has your organization ever paid for UI components?
<img src="/static/blog/2020-survey/20.png" style="width: 796px; margin-top: 16px; margin-bottom: 8px;" alt="Pie chart: 89.90% No, 10.10% Yes" />
### 21. What type system are you using?
<img src="/static/blog/2020-survey/21.png" style="width: 796px; margin-top: 16px; margin-bottom: 8px;" alt="Bar chart: 54.08% None
30.87% TypeScript 3.8, 7.31% TypeScript 3.7, 1.90% Flow, 1.55% TypeScript 3.6, 0.98% TypeScript 3.5, 3.31% Other" />
Almost half of the community is using TypeScript. Next year, it might even become more popular than JavaScript.
## Conclusion
This data is **incredibly valuable** for our team.
Thank you again for participating!
We want to work on the problems that resonate the most with our users.
[It's clear](#5-how-can-we-improve-mui-for-you) that we should:
1. Provide more flexibility on the components, unstyled components (pure hooks?).
1. Make the customization easier and implement custom themes with MUI. Maybe provide a theme builder.
1. Provide a second theme, update the current components to better match Material Design, provide more simple components and features (e.g. dropzone, carousel) as well as provide a better DX (there are good ideas from other UI libraries to apply to MUI v5).
1. Improve upon the paid advanced versions of the components (e.g. complex data grid, date range picker, tree view drag & drop, virtualization, etc).
**We will update [our ROADMAP](/material-ui/discover-more/roadmap/) in the coming days**.
We will run a similar survey next year to keep track of our progress.
If you want to continue to influence our roadmap, please upvote 👍 the issues you are the most interested in on GitHub.
<img src="/static/blog/2019-survey/vote.gif" style="width: 550px; margin-bottom: 8px;" alt="How to upvote on GitHub" />
<p class="blog-description">Help us prioritize by upvoting.</p>
| 4,108 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/blog/2020-introducing-sketch.js | import * as React from 'react';
import TopLayoutBlog from 'docs/src/modules/components/TopLayoutBlog';
import { docs } from './2020-introducing-sketch.md?@mui/markdown';
export default function Page() {
return <TopLayoutBlog docs={docs} />;
}
| 4,109 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/blog/2020-introducing-sketch.md | ---
title: Introducing MUI for Sketch
description: Today, we're excited to announce the introduction of official Sketch symbols for MUI.
date: 2020-03-30T00:00:00.000Z
authors: ['oliviertassinari']
tags: ['News']
---
Today, we're excited to introduce the Sketch symbols 💎 for MUI.
[](https://mui.com/store/items/sketch-react/?utm_source=blog&utm_medium=blog&utm_campaign=introducing-sketch)
<p class="blog-description">Available on our <a href="https://mui.com/store/items/sketch-react">store</a></p>
The UI kit contains all the MUI components with states and variations which gives 1,500+ unique elements. All components are designed with the most up to date release.
We dream of a world where designers and developers can share the same tools. We wish to streamline the creation process of great UIs.
This new product brings you one step closer to this long term goal. It enables designers to provide developers close to production "handoffs". It aims to **maximize efficiency and consistency**.
## Why
### Frequent requests
Over the last few months, we have seen a growing number of designers asking for these Sketch symbols.
For instance, there is a [Stack Overflow question](https://stackoverflow.com/questions/38834629/material-ui-sketch-files) with over 4,000 views. It has been a common request on Twitter: [one](https://twitter.com/TimoMajerski/status/1144503789619224578), [two](https://twitter.com/jonminori/status/1141121330156310528), [three](https://twitter.com/ProfessorXavior/status/1196522875706056705), [etc](https://twitter.com/JeffreyKaine/status/1133435042259120132).
### No great alternatives
For a long time, we have ignored the problem. We were recommending users to try alternatives out. However, we realized that it wasn't a great answer. There were no good solutions out there:
- **Sketch** has [some symbols](https://i.stack.imgur.com/vEEAA.png) for Material Design. Unfortunately, they cover <30% of the components available in MUI, use an outdated version of the specification, and focus on mobile (leaving desktop behind).
- **Material Design** had a [Sketch plugin](https://m2.material.io/resources/theme-editor/).
Unfortunately, it was recently retired, was supporting fewer components than MUI, and didn't use the same wording/structure as MUI that made it harder to move from design to implementation.
- Anything else is paid.
### Gain efficiency
No matter what your role, you'll be more efficient with these assets:
**UI / UX Designers 💅**
Save time using this large library of UI components, icons and styles to deliver your work faster. You can customize the kit however you want to match your product's brand.
**Product managers / Entrepreneurs 🧪**
Create MVPs efficiently and save hundreds of hours on UI Design. This is a great place to start if your product or brand needs a design system. Equip your team with this library for Sketch and build consistent products faster.
**Developers 🛠**
Gain in autonomy, design beautiful, consistent and accessible interface without relying on designers. You can preview how it will look before coding it.
The UI kit was created specifically for MUI, a popular React UI library with a comprehensive set of components.
## See it in action
The following video demonstrates how the symbols can be used to design an invoice page.
<iframe style="width: 100%; max-width: 648px;" height="364" src="https://www.youtube.com/embed/DTU6r_VE2C4" frameborder="0" allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
Sketch Cloud preview: https://mui.com/store/previews/sketch-react/.
## More tools
According to a [recent user survey](https://medium.com/google-design/state-of-design-systems-2019-ff5f26ada71) ran by the Material Design Team, Sketch is the most popular tool used by teams to manage design systems. However, it's not the only tool.
<p class="blog-description">Popular tools used to manage Design Systems (n=1762)</p>
We are working on the support of more popular tools.
We have recently released the support of Framer X for MUI.
We plan to release the support of **Figma** in the coming weeks. You can subscribe to the [newsletter of the store](https://mui.com/store/#subscribe) to be notified when available.
## Features
You can learn more about the features available on the [Sketch page details](https://mui.com/store/items/sketch-react/?utm_source=blog&utm_medium=blog&utm_campaign=introducing-sketch) of the symbols.
| 4,110 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/blog/2020-q1-update.js | import * as React from 'react';
import TopLayoutBlog from 'docs/src/modules/components/TopLayoutBlog';
import { docs } from './2020-q1-update.md?@mui/markdown';
export default function Page() {
return <TopLayoutBlog docs={docs} />;
}
| 4,111 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/blog/2020-q1-update.md | ---
title: Q1 2020 Update
description: An update on our mission for Q1 2020.
date: 2020-04-14T00:00:00.000Z
authors: ['oliviertassinari']
tags: ['Company']
---
Welcome to the new format of our mission update. We are moving from monthly to quarterly updates.
## Product
Over the last 3 months, we have focused on making patch releases.
We have done eleven so far. We have optimized for stability.
Here are the most significant improvements since the beginning of the year:
- 🔍 We have polished the [Autocomplete](https://mui.com/material-ui/react-autocomplete/) component (Combo box). We have closed more than [270](https://github.com/mui/material-ui/labels/lab%3A%20Autocomplete) issues and pull requests so far. We will promote the component to the core in the next major (v5).
<p class="blog-description">useAutocomplete <a href="https://mui.com/material-ui/react-autocomplete/#useautocomplete">hook</a> example, 4.5 kB gzipped.</p>
If you wish to make your first contribution to open source, the component has a couple of ["good first issues"](https://github.com/mui/material-ui/labels/lab%3A%20Autocomplete) that can be taken.
If you have TypeScript expertise, the component could [benefit from it](https://github.com/mui/material-ui/issues?q=is%3Aopen+label%3A%22lab%3A+Autocomplete%22+label%3Atypescript).
- 📆 We have made a first [alpha release](https://github.com/mui/material-ui-pickers/releases/tag/v4.0.0-alpha.4) of the date range picker. It's not ready to be used in production but you can start playing. We might release some of the new features of the date picker under the upcoming Enterprise offering.
- ⚠️ We have introduced a new [Alert](https://v4.mui.com/components/alert/) component in the lab. While this component isn't mentioned in the Material Design guidelines, it's a common and well-established pattern. For instance, it can be interested when [combined](https://v4.mui.com/components/snackbars/#notistack) with the Snackbar.
<img src="/static/blog/2020-q1-update/alert.png" alt="alert" style="max-height: 369px; margin-bottom: 24px;" />
- ⏭ We have introduced a new [Pagination](https://v4.mui.com/components/pagination/) component.
<img src="/static/blog/2020-q1-update/pagination.png" alt="pagination" style="max-height: 208px; margin-bottom: 8px;" />
- 🦴 We have added a new "wave" animation to the [Skeleton](https://v4.mui.com/components/skeleton/#animations) component.
<video style="max-height: 95px; margin-bottom: 24px;" autoplay muted loop playsinline>
<source src="/static/blog/2020-q1-update/skeleton.webm" type="video/webm" />
</video>
- ⚛️ We have worked on improving developer experience inside text editors.
- We have migrated prop descriptions from JSDoc to TypeScript for 60% of the components. Back-and-forths with the documentation API will be less frequent:
- The color modules come with new previews:
- We have collaborated with [Andy Edwards](https://github.com/jedwards1211) to provide [snippets](https://marketplace.visualstudio.com/items?itemName=vscodeshift.material-ui-snippets) with Visual Studio Code:
- 💎 We have introduced [Sketch assets](/blog/2020-introducing-sketch/).
<img src="/static/blog/2020-q1-update/sketch.png" alt="sketch" style="max-width: 160px;" />
But this summary is just scratching the surface. We have accepted 572 commits from 214 different contributors.
## Company
We are thrilled to welcome two new full-time developers on MUI:
- [Dmitriy Kovalenko](https://github.com/dmtrKovalenko), the author of @material-ui/pickers.
<img src="https://avatars.githubusercontent.com/u/16926049" alt="dmitriy" style="max-width: 160px; margin: unset; margin-bottom: 24px; border-radius: 2px;" />
- [Damien Tassone](https://github.com/dtassone/), an experienced developer in the finance industry.
<img src="https://avatars.githubusercontent.com/u/936978" alt="damien" style="max-width: 160px; margin: unset; margin-bottom: 24px; border-radius: 2px;" />
### Growth between Q4 2019 and Q1 2020
- 📦 From 3.2M to 4.8M downloads per month on npm.
- ⭐️ From 53.3k to 56.2k stars, leave us yours 🌟.
- 👨👩👧👦 From 1,581 to 1,720 contributors on GitHub.
- 💰 Grew monthly financial support by 47%.
- 🏢 From 3 to 5 full-time equivalent developers, spread among multiple financially supported core team members.
## Our roadmap intent for Q2 2020
We'll do our best, no guarantee!
- 📣 We will analyze and publish the results of the "MUI Developer Survey 2020". If you haven't contributed to it yet, you can follow this link to [fill it in](https://forms.gle/TYWRdvgyZs4AhZNv8), thanks!
- 🎨 We will release Figma assets for MUI.
<img src="/static/blog/2020-q1-update/figma.png" alt="figma" style="max-width: 160px; margin-bottom: 24px;" />
- 🇨🇳 We will translate 100% of the documentation to Chinese. We are collaborating with [Danica Shen](https://github.com/DDDDDanica), a native speaker, to complete the effort. So far, we have translated 73% of the documentation and peer-reviewed 39%. You can help us out on [Crowdin](https://crowdin.com/project/material-ui-docs).
<img src="/static/blog/2020-q1-update/chinese.png" alt="chinese" style="max-width: 134px; margin-bottom: 24px;" />
- 🔥 We will start to work on the [next major: v5](https://github.com/mui/material-ui/issues/20012).
You can expect the following:
- A feature freeze on v4.
- The introduction of deprecation messages in the next v4 minors. These messages will help developers upgrade to v5.
- A progressive bug fixes freeze on v4, with the exception of security issues and important bugs.
- At least 6 months of work on v5 to get to a stable release (probably more). You can follow our progress using our [milestone](https://github.com/mui/material-ui/milestone/35).
- 🧑💻 We will likely look to hire a new full-time member on the core team to help deliver v5 and new features faster.
- ⌗ We announced, back in [October 2019](/blog/september-2019-update/#our-roadmap-intent-for-october), our intention to work on an advanced data grid component. The task was bigger than anticipated, but we are making progress. It might take us 12 months to do it right. Damien is now leading and fully dedicated to this effort. You can follow our early-stage progress on [finui.io](https://finui.io/#/grid) and later, integration into the mono-repository on [#18872](https://github.com/mui/material-ui/pull/18872).
<p class="blog-description">For <a href="https://uxdesign.cc/design-better-data-tables-4ecc99d23356">illustration</a> purposes only.</p>
- 📆 We will polish the date picker. We will work on: providing a comprehensive set of features, to unify the experience with the core package, to improve the overall quality. The objective is to make these components stable in the next major (v5).
- ❓ Please upvote our [GitHub issues](https://github.com/mui/material-ui/issues) if you want something specific. The number of 👍 helps us to prioritize.
| 4,112 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/blog/2020-q2-update.js | import * as React from 'react';
import TopLayoutBlog from 'docs/src/modules/components/TopLayoutBlog';
import { docs } from './2020-q2-update.md?@mui/markdown';
export default function Page() {
return <TopLayoutBlog docs={docs} />;
}
| 4,113 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/blog/2020-q2-update.md | ---
title: Q2 2020 Update
description: An update on our mission for Q2 2020.
date: 2020-07-17T00:00:00.000Z
authors: ['oliviertassinari']
tags: ['Company']
---
This update covers our progress over the last three months, and what we aim to achieve in the coming months.
## Product
Here are the most significant improvements since March 2020:
- 🚧 Work has started on [the next major version: v5](https://github.com/mui/material-ui/issues/20012).<br />
The last 14 months have been spent focusing on improving the library under the v4.x development branch, while not introducing any breaking changes. During this period we have identified several important areas for improvement. While the absence of breaking changes is a significant time-saver for developers, it also limits the scope of the problems that can be solved and the quality of the solutions. We're excited about what comes next!<br /><br />
You can find the documentation for the next version at https://mui.com/. The next 6-8 months will see weekly releases as always, following [the roadmap](https://github.com/mui/material-ui/issues/20012) and [milestone](https://github.com/mui/material-ui/milestone/35).
- 📍 The icons package has been updated with changes made by Google, leading to [200+ new icons](https://mui.com/material-ui/material-icons/).
<img src="/static/blog/2020-q2-update/icons.png" alt="icons" style="width: 615px; margin-bottom: 24px;" />
- 🎨 [Figma assets](https://mui.com/store/items/figma-react/) for MUI extend the support for design tools beyond Sketch.
<a href="https://mui.com/store/items/figma-react/"><img src="/static/blog/2020-q1-update/figma.png" alt="figma" style="width: 160px; margin-bottom: 24px;" /></a>
Adobe XD and Framer support are also up for consideration if they attract a significant audience, but not until we've polished the Sketch and Figma assets.
- 🔄 `LoadingButton` – [a new component in the lab](https://mui.com/material-ui/react-button/#loading-button). This work is influenced by the [concurrent UI patterns](https://17.reactjs.org/docs/concurrent-mode-patterns.html) presented by the React team.
<img src="/static/blog/2020-q2-update/loading.gif" alt="loading" style="margin-bottom: 24px;" />
- ⚛️ We have made **all** component props available in IntelliSense. This is complementary to the `propTypes` and API pages in the documentation.
- ⏰ A new [`Timeline` component](/material-ui/react-timeline/) joins the lab.
<img src="/static/blog/2020-q2-update/timeline.png" alt="timeline" style="width: 244px; margin-bottom: 24px;" />
- 📣 We have analyzed and published the results of the "MUI Developer Survey 2020". If you haven't read it yet, you can follow this link to [read it in detail](/blog/2020-developer-survey-results/). It contains a lot of interesting insights that will shape the future of the library and company. Thanks for the contributions! ❤️
- 🇨🇳🇧🇷 The non-API documentation has been fully translated to Chinese and Brazilian, thanks to the collaboration of [Danica Shen](https://github.com/DDDDDanica), [Yan Lee](https://github.com/AGDholo), and [Jairon Alves Lima](https://github.com/jaironalves), native speakers from the community 🙏.
<img src="/static/blog/2020-q2-update/chinese.png" alt="chinese" style="width: 146px; padding-right: 3px; box-sizing: content-box;" />
<img src="/static/blog/2020-q2-update/brazilian.png" alt="brazilian" style="width: 152px; margin-bottom: 24px;" />
After English, Chinese, and Brazilian, the languages that would benefit the most from translation are **Russian** and **Spanish**.<br />
Feel free to [get stuck into](https://crowdin.com/project/material-ui-docs) if you are a native speaker and able to give a hand with either of these two languages.
- 🗂 A new extension of the Tab API [in the lab](/material-ui/react-tabs/#experimental-api) implements accessible tabs following [WAI-ARIA](https://www.w3.org/WAI/ARIA/apg/patterns/tabs/) authoring practices.
```jsx
<TabContext value={value}>
<TabList onChange={handleChange} aria-label="simple tabs example">
<Tab label="Item One" value="1" />
<Tab label="Item Two" value="2" />
<Tab label="Item Three" value="3" />
</TabList>
<TabPanel value="1">Item One</TabPanel>
<TabPanel value="2">Item Two</TabPanel>
<TabPanel value="3">Item Three</TabPanel>
</TabContext>
```
- 📆 On the [date picker](https://mui.com/x/react-date-pickers/):
- A new `renderInput` API which matches that of the autocomplete component has been added.
- The input mask UX has been improved.
- Support for `value={null}` has been added.
- Desktop vs mobile detection has been improved by using the pointer capabilities instead of the screen dimension.
- Accessibility has been improved.
- Consistency between the date pickers and the other components of the library has been improved.
## Company
### Growth between Q1 2020 and Q2 2020
- 📦 From 4.8M to 5.1M downloads per month on npm.
- ⭐️ From 56.2k to 59.0k stars, leave us yours 🌟.
- 👨👩👧👦 From 1,720 to 1,825 contributors on GitHub.
- 💰 Grew monthly financial support by 46%.
- 🏢 Headcount remains the same.
## Our roadmap intent for Q3 2020
We'll do our best, no guarantee!
- ⚙️ To make significant progress with the v5 roadmap.
- 🌏 Translate the API pages, for instance, the [Alert API](https://mui.com/api/alert/) can only be consumed in English.
- 📆 Migrate the date picker components to the main repository to ensure high consistency with the core components. Keep investing in the component to make it part of the v5 release schedule.
- 👩🎨 We will work with a design agency to do the branding of the company, redo the homepage, do the marketing pages of the enterprise version of the library, improve the documentation, introduce new themes (as alternatives to Material Design).
- ❓ Please upvote [GitHub issues](https://github.com/mui/material-ui/issues) if you want something specific. The number of 👍 helps us to prioritize.
### Company
These are objectives, no guarantees:
- 🏢 We will [hire](/careers/) 3 full-time roles in the team.
- One person on the open-source side to focus on the design system problem (unstyled, theming, styling, etc.): ✅ starting in two months.
- One person on the enterprise side to consolidate the development of the advanced components: 🚧 Work in progress.
- One person on a role yet to defined: 🚧 Work in progress.
- 🏝 We will run a company-wide team retreat if COVID-19 allows it.
- 📈 We will put structures internally to prepare the next step of growth.
### Enterprise components
- ⌗ Make available a first alpha version of our advanced data grid component as part of the enterprise bundle.
You can already play with an early version.
- 📆 Make available a first alpha version of the date range picker as part of the enterprise bundle.
You can already play with an early version.
| 4,114 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/blog/2020-q3-update.js | import * as React from 'react';
import TopLayoutBlog from 'docs/src/modules/components/TopLayoutBlog';
import { docs } from './2020-q3-update.md?@mui/markdown';
export default function Page() {
return <TopLayoutBlog docs={docs} />;
}
| 4,115 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/blog/2020-q3-update.md | ---
title: Q3 2020 Update
description: An update on our mission for Q3 2020.
date: 2020-10-14T00:00:00.000Z
authors: ['oliviertassinari']
card: true
tags: ['Company']
---
This update covers our progress over the last three months, and what we aim to achieve in the coming months.
## Product
Here are the most significant improvements since June 2020. This was a dense quarter!
- 🚧 We have started the quarter with the first pre-release [v5.0.0-alpha.1](https://github.com/mui/material-ui/releases?after=v5.0.0-alpha.1) of the next major iteration of the library.
There have been eleven more pre-releases since then. During the alpha development stage of version 5, we are focusing on making the planned breaking changes, as well as developing new features.
On the breaking changes side, we have made almost half of the changes that we have planned.
- 🧪 We have promoted 7 components from the lab to the core: Alert, Autocomplete, Pagination, Rating, Skeleton, SpeedDial, and ToggleButton.
Thank you for all your feedback on these components.
While we still plan a couple of breaking changes on them, we are confident that they have reached the same level of quality as the other core components.
- 👮 We have introduced a new component in the lab, the [FocusTrap](https://mui.com/base-ui/react-focus-trap/). It manages focus for its descendants. This is useful when implementing overlays such as modal dialogs, which should not allow the focus to escape while open:
<video style="max-height: 416px; margin-bottom: 24px;" autoplay muted loop playsinline>
<source src="/static/blog/2020-q3-update/trap-focus.mp4" type="video/mp4" />
</video>
- ⚛️ We have prepared the support for the upcoming release of [React v17](https://legacy.reactjs.org/blog/2020/08/10/react-v17-rc.html). Most of the work was about better handling events, and updating our test infrastructure to run the whole test suite with the _latest_ and _next_ version of React.<br />We have also improved `StrictMode` support. The last standing issues are being addressed with the work on the style engine. More on that later in the post.
- 💅 We have introduced a new dynamic variant API. This API allows developers to add new variants to MUI components right from the theme, without having to wrap the components. For instance with the Button:
```tsx
// Define the style that should be applied for specific props.
const theme = createMuiTheme({
components: {
MuiButton: {
variants: [
{
props: { variant: 'dashed', color: 'secondary' },
styles: {
border: `4px dashed ${red[500]}`,
},
},
],
},
},
});
// Optionally retain type safety:
declare module '@mui/material/Button' {
interface ButtonPropsVariantOverrides {
dashed: true;
}
}
// Enjoy!
<Button variant="dashed" color="secondary" />;
```
This change is part of a direction to ease the implementation of custom design systems.
Note that the API not only allows to match a single prop, but also a combination of props.
This is especially interesting to resolve the conflict when different variants try to modify the same CSS property.
Hopefully, in the future, we will be able to take advantage of the variant feature [coming in Figma](https://help.figma.com/hc/en-us/articles/360055471353-Prepare-for-Variants) with this API.
- ⚡️ We have released a first alpha version of the [data grid component](/x/react-data-grid/).<br />
We announced our intent to build this component [a year ago](/blog/september-2019-update/#our-roadmap-intent-for-october). While we could have implemented a simple version and release it a month later, it wouldn't have set us in the right direction for the years to follow. We're aiming aim to deliver the best-in-class React data grid.
This objective requires a twin licensing model. The component is available under an MIT license for the features that can be relatively easily implemented, and that can be sustained with an open-source model; as well as a paid commercial license for the more advanced features.
<br />To ensure we could meet this objective, we spent time finding an expert in the field. This led us to open a new job position, and, a few months later, [Damien Tassone](/blog/spotlight-damien-tassone/) joined to lead the work on this component.
<a href="/x/react-data-grid/"><img src="/static/blog/2020-q3-update/data-grid.png" alt="" style="width: 829px; margin-bottom: 8px;" /></a>
<p class="blog-description">100,000 rows</p>
After 6 months of development since the initial commit (March 15th, 2020), you can start using the component! (It targets v4.)
- ⚡️ The data grid effort has led to the introduction of a new repository: [_mui/mui-x_](https://github.com/mui/mui-x). This is the repository that will host all the future commercial components, all the components that we can't sustain with the open-source model. MUI X is our next iteration in scaling MUI, both as a company and as a comprehensive React library of components. While we have an existing sustainability model that can support, in long term, up to 10 people full-time, we are keen to push it by an order of magnitude.
- 🛠 We have migrated parts of the codebase to TypeScript.<br />
We had to work on the code infrastructure of _mui/material-ui_ to prepare to host the date picker components that are written in TypeScript inside the lab (coming from _mui/material-ui-pickers_ that we will archive once we can).
<img src="/static/blog/2020-q3-update/typescript-mui.png" alt="" style="width: 299px; margin-bottom: 8px;" />
<p class="blog-description">MUI's repository</p>
On the other hand, we started using TypeScript from day one for _mui/mui-x_.
<img src="/static/blog/2020-q3-update/typescript-mui-x.png" alt="" style="width: 299px; margin-bottom: 8px;" />
<p class="blog-description">MUI X's repository</p>
- 🐙 We have migrated large parts of the test suite to react-testing-library.<br>
15 months ago, we introduced the very [first test](https://github.com/mui/material-ui/pull/15732) using the library (to replace enzyme). Last month, react-testing-library had [more downloads](https://npm-stat.com/charts.html?package=enzyme&package=%40testing-library%2Freact&from=2019-10-10&to=2020-10-10) than enzyme!
<img src="/static/blog/2020-q3-update/react-testing-library.png" alt="" style="width: 640px; margin-bottom: 40px; margin-top: 24px;" />
- 💅 We have completed the first iteration of the unstyled components for v5.<br />You can find a [new version](/material-ui/react-slider/#unstyled) of the slider in the lab without any styles.
The unstyled component weighs in at [5.2 kB gzipped](https://bundlephobia.com/package/@mui/[email protected]), compared with 26 kB for the styled version (when used standalone). The component is best suited for use when you want to fully customize the look, without reimplementing the JavaScript and accessibility logic.<br />
We're also pushing in this direction to address a concern we hear from large enterprises
that want to be able to go one layer down in the abstraction, in order to gain more control.
```jsx
import SliderUnstyled from '@mui/lab/SliderUnstyled';
```
Note that we have experimented with headless components (hooks only) in the past. For instance, you can leverage the [useAutocomplete](/material-ui/react-autocomplete/#useautocomplete), and [usePagination](/material-ui/react-pagination/#usepagination) hooks. However, we are pushing with unstyled first as a required step for the next item: ⬇️.
- 👩🎨 We have completed the first iteration of the new styling solution of v5.<br />
You can find a [new version](/material-ui/react-slider/) of the slider in the lab powered by [Emotion](https://emotion.sh/docs/introduction).<br />
If you are already using styled-components in your application, you can swap Emotion for styled-components 💅. Check this [CodeSandbox](https://codesandbox.io/s/sliderstyled-with-styled-components-forked-olc27?file=/package.json) or [CRA](https://github.com/mui/material-ui/tree/HEAD/examples/material-ui-cra-styled-components/) for a demo. It relies on aliases to prevent any bundle size overhead.<br />
The new styling solution saves 2kB+ gzipped in the bundle compared to JSS, and about 14 kB gzipped if you were already using styled-components or Emotion.<br />
Last but not least, this change allows us to take advantage of dynamic style props. We will use them for dynamic color props, variant props, and new style props available in the core components.
<img src="/static/blog/2020-q3-update/emotion.png" alt="" style="width: 329px;" />
<p class="blog-description">Slider powered by Emotion</p>
<img src="/static/blog/2020-q3-update/styled-components.png" alt="" style="width: 323px;" />
<p class="blog-description">Slider powered by styled-components</p>
- ♿︎ We have kept investing in accessibility, we have fixed [13 bugs](https://github.com/mui/material-ui/pulls?q=is%3Apr+label%3Aaccessibility+is%3Aclosed+sort%3Aupdated-desc).
- 🗓 We have introduced public quarterly roadmaps, both for [MUI Core](https://github.com/orgs/mui/projects/18/views/1) and [MUI X](https://github.com/mui/mui-x/projects/1).
## Company
We are thrilled to welcome two new full-time developers to MUI:
- [Marija Najdova](https://github.com/mnajdova). Marija joins us from the Fluent-UI React team at Microsoft. She's allowing the community team to move faster. You can learn more about her in the [introduction blog post](/blog/marija-najdova-joining/).
<img src="https://avatars.githubusercontent.com/u/4512430?s=320" alt="marija" style="max-width: 160px; margin: unset; margin-bottom: 24px; border-radius: 2px;" />
- [Danail Hadjiatanasov](https://github.com/DanailH). Danail comes to us from the Fintech industry. He's allowing the enterprise team to move faster, he's helping Damien push the data grid further.
<img src="https://avatars.githubusercontent.com/u/5858539?s=320" alt="marija" style="max-width: 160px; margin: unset; margin-bottom: 24px; border-radius: 2px;" />
### Growth between Q2 2020 and Q3 2020
- 📦 From 5.1M to 6.0M downloads per month on npm.<br />
While React is growing, we are also growing inside its ecosystem.
<img src="/static/blog/2020-q3-update/react-share.png" alt="" style="width: 588px; margin-bottom: 16px;" />
<p class="blog-description">% of download relative to react-dom</p>
- ⭐️ From 59.0k to 61.6k stars, leave us yours [🌟](https://github.com/mui/material-ui).
- 👨👩👧👦 From 1,825 to 1,934 contributors on GitHub. We add on average 1 new contributor every day.
- 🏢 We have welcomed two new full-time developers to MUI.
## Our roadmap intent for Q4 2020
We'll do our best, no guarantee!
### Community
- 🗓 Execute on all the items of the [public roadmap](https://github.com/orgs/mui/projects/18/views/1).
- 👩🎨 Simplify the migration experience from v4 to v5.
- ❓ Please upvote [GitHub issues](https://github.com/mui/material-ui/issues) if you want us to focus on a specific problem. The number of 👍 helps us to prioritize.
### Enterprise
- 👩🎨 Complete the collaboration we started with a design agency last quarter to update the branding of the company, redesign the homepage, and design the marketing pages for the enterprise package.
- 🗓 Execute on all the items in the [public roadmap](https://github.com/mui/mui-x/projects/1).
- ❓ Please upvote [GitHub issues](https://github.com/mui/mui-x/issues) if you want us to focus on a specific problem. The number of 👍 helps us to prioritize.
### Company
These are objectives, no guarantees:
- 🏢 We might hire a full-time designer that has coding skills. One of the objectives would be to solve [#22485](https://github.com/mui/material-ui/issues/22485).
- 🏝 We have put the company-wide team retreat on hold because of the continued risk presented by COVID-19.
Hopefully, we will be able to hold it in Q2 2021.
| 4,116 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/blog/2020.js | import * as React from 'react';
import TopLayoutBlog from 'docs/src/modules/components/TopLayoutBlog';
import { docs } from './2020.md?@mui/markdown';
export default function Page() {
return <TopLayoutBlog docs={docs} />;
}
| 4,117 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/blog/2020.md | ---
title: 2020 in review and beyond
description: 2020 has been another great year, not only for MUI, but also for the ecosystem.
date: 2020-12-31T00:00:00.000Z
authors: ['oliviertassinari', 'mbrookes']
card: true
tags: ['Company']
---
2020 has been another great year, not only for MUI, but also for the ecosystem.
We have taken on ambitious challenges and started to scale the project.
## Growth
It's only with your trust that we could achieve the following outcomes in 2020. Thank you!
- 📦 From 3.2M to [6.4M](https://npm-stat.com/charts.html?package=%40material-ui%2Fcore&from=2019-11-30&to=2020-12-31) downloads per month (from 14% to [18%](https://docs.google.com/spreadsheets/d/1l5j3Xjtvm9XZtmb4ulLiWElQaXSlZlyCWT5ONrQMpBo/edit?usp=sharing) share of the React ecosystem).
- 📈 From 3.1M to 4.6M unique visitors per year on the documentation.
- ⭐️ From 53.3k to 63.8k stars, leave us [yours 🌟](https://github.com/mui/material-ui).
- 👨👩👧👦 From 1,581 to [2,052](https://github.com/mui/material-ui/graphs/contributors) contributors.
- 💰 Grew financial support by 2.1X in 2020, compared to 2019.
- 🏢 From 3 to 6 full-time equivalent developers, spread among multiple financially supported [core team members](/about/).
The numbers speak for themselves. We have reproduced the [traction we got in 2019](/blog/2019/#growth).
## In review
When we started 2020, we were celebrating the launch of many new components.
We were busy building features to match feature parity with Ant Design, and more importantly, acting on the top feedback we got doing the [first user survey](/blog/2019-developer-survey-results/).
We have spent the year continuing in the same direction, polishing past components and introducing new ones. We ran a [second user survey](/blog/2020-developer-survey-results/), 15 months after the first one. It was a great opportunity to evaluate the effectiveness of our past efforts. For instance, we were very pleased to see that the slider component was almost a solved problem, and that the TypeScript definitions significantly improved. We also noticed the emergence of trends:
- The more new components we add, the more developers want new ones. For instance, we rarely heard about the need for providing charts in 2019, it's now one of the top requested. In our last survey, we had 10% more requests for new components, even though, we brought new ones. We were surprised, it was counter-intuitive to us.
- The pain around the customization of the components is growing. We also frequently hear that there is a steep learning curve for using `@mui/styles`. We are reaching a larger audience used to raw CSS without extensive knowledge of specificity.
- The demand for Material Design is stable, no longer growing. At the same time, the request for new ready-to-use themes is up. Our strategy around providing building blocks to build custom designed UI starts to gain traction.
We have started to leverage these trends as opportunities in the next version of the library: v5.
## Achievements
We have achieved most of what we could have hoped for.
- The most important, we have welcome 3 members in the company: [Damien](/blog/spotlight-damien-tassone/), [Marija](/blog/marija-najdova-joining/), and [Danail](/blog/danail-hadjiatanasov-joining/).
- We have made significant progress with [v5](https://mui.com/). We have made half the breaking changes planned. We have migrated our [first component](https://v4.mui.com/components/slider/) to the new style architecture (emotion by default, adapter for styled-components, and unstyled).
- We have introduced new components (some in the core, some in the lab):
- [Alert](https://v4.mui.com/components/alert/)
- [DataGrid](https://v4.mui.com/components/data-grid/)
- [DatePicker](https://v4.mui.com/components/pickers/)
- [LoadingButton](https://mui.com/material-ui/react-button/#loading-button)
- [Timeline](https://v4.mui.com/components/timeline/)
- [FocusTrap](https://mui.com/base-ui/react-focus-trap/)
- We have fixed most of the issues with the [Autocomplete](https://v4.mui.com/components/autocomplete/). We have received an overwhelming interest in the component. It was impressive to see.
- We have completed the work for [strict mode](https://legacy.reactjs.org/docs/strict-mode.html) support.
- We have increased the adoption of TypeScript in the codebase. We don't plan a dedicated migration but to write new code in TypeScript, as we go.
- We have migrated most of the tests from Enzyme to [Testing Library](https://testing-library.com/).
- We have modernized the system, introducing an [`sx` prop](https://mui.com/system/getting-started/the-sx-prop/) to be used in all the core components.
- We have added support for [Figma](/store/items/figma-react/) and [Adobe XD](/store/items/adobe-xd-react/).
- We have released the first Enterprise component in an alpha version: [XGrid](https://v4.mui.com/components/data-grid/#commercial-version).
## Looking at 2021
2020 was great, 2021 is going to be even more exciting!
We will continue in the same direction, it's still **[day one](https://www.sec.gov/Archives/edgar/data/1018724/000119312517120198/d373368dex991.htm)**. Here is a breakdown of our [roadmap](https://v4.mui.com/discover-more/roadmap/).
### Branding
Up until now, we never had a mindful reflection on what the branding of MUI should be. We picked a color from the 2014 Material Design palette, and that's it.
The [mui.com](https://mui.com/) marketing website will soon wear a brand new style! We need to create our own identity, distinct from Material Design.
### MUI X
We started to deliver advanced React components in 2020 with the data grid, including a [commercial version](https://v4.mui.com/components/data-grid/) and the beginning of a [date range picker](https://mui.com/x/react-date-pickers/getting-started/).
We will double down on these existing components as long as necessary to have them find the market.
By the end of 2021, we aim to have released these components as stable, implement all the [features planned](https://v4.mui.com/components/data-grid/getting-started/#feature-comparison), and at least double the size of the team.
### MUI v5
We will release the next major iteration of the library. A highlight of the key improvements coming ✨:
- Polish and promote most of the components that were in the lab in v4 to the core.
- A new style engine. Migrate from JSS to Emotion (default) and styled-components's `styled` API.
- Improve customizability. Add new powers to the theme with dynamic color & [variant](https://mui.com/material-ui/customization/typography/#adding-amp-disabling-variants) support. Add a new [`sx` prop](https://mui.com/system/getting-started/the-sx-prop/) for quick customizations to all the components. Expose global class names. Deprecate the `makeStyles` and `withStyles` API.
- Breaking changes on the API to make it more intuitive.
- Add full support for React strict mode. We recommend to enable it.
- Improve the performance of the system by a x3-x5 [factor](https://github.com/mui/material-ui/issues/21657#issuecomment-707140999).
- Reduce bundle size: split IE11 into a different bundle [-6kB](https://github.com/mui/material-ui/pull/22814#issuecomment-700995216), migrate to Emotion [-5kB](https://github.com/mui/material-ui/pull/23308#issuecomment-718748835), Popper.js v2 upgrade [-700B](https://github.com/mui/material-ui/pull/21761#issuecomment-657135498).
- Improve the documentation website: search shortcut, page rating, fast material icons copy button, etc.
And [much more](https://github.com/mui/material-ui/issues/20012).
### A second theme
While Material Design is a predominant design choice for building rich client-side applications, it's not the only popular design trend. We plan to provide a [second theme](https://github.com/mui/material-ui/issues/22485) to expand the range of use cases for MUI, striking a balance between:
- alignment with the best-looking design trends of hot startups in the US.
- optimization of its usage for rich client-side applications while keeping it good enough for landing pages.
- simplicity of the design for allowing simpler customizations.
- complementarity with Material Design.
It will be built on top of the unstyled components.
### Unstyled
While the completion of the unstyled components was originally part of the v5 milestone,
we will likely finish this effort independently.
Outside of the requirement to introduce breaking changes on the component customization API, e.g. from `PaperProps` to `slotProps`, [RFC #20012](https://github.com/mui/material-ui/issues/21453), we can work on unstyled at the same time we make progress with the second theme. The two efforts should go hand in hand.
### Scale
If we sustain the current growth rate, we should be able to double the size of the team, from 6 to over 10 members in the company without raising. While we will focus on strengthening all the efforts that we have started, it should start to give us room to take on significantly more ambitious problems guided by the following foundations:
- React dominance in the UI development landscape will increase and stay for a very long time.
- Developers are looking to build faster and more appealing UIs.
- Low-code will progressively become mainstream for professional developers and knowledge workers.
If like us, you are excited about bringing joy to developers and enabling more people to build apps, check our positions, [we are hiring](/careers/)!
See you in 2021 🚀
| 4,118 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/blog/2021-developer-survey-results.js | import * as React from 'react';
import TopLayoutBlog from 'docs/src/modules/components/TopLayoutBlog';
import { docs } from './2021-developer-survey-results.md?@mui/markdown';
export default function Page() {
return <TopLayoutBlog docs={docs} />;
}
| 4,119 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/blog/2021-developer-survey-results.md | ---
title: 'The 2021 MUI developer survey: here's what we discovered'
description: Your feedback helps us to build better products. Here's what we learned about your needs in our annual survey.
date: 2022-03-15T00:00:00.000Z
authors: ['danilo-leal', 'samuelsycamore', 'oliviertassinari']
tags: ['Developer survey']
card: true
---
Keeping up with tradition, a few months ago we opened the 2021 MUI Developer Survey.
Your feedback helps us to build better products, and we can't thank you enough for being a part of our community.
1,591 of you responded to this year's survey, and we take your input very seriously.
Here's what we've learned about your needs after poring over the results.
As with the previous iterations, the survey was divided into three sections: ["Your needs"](#your-needs), ["Your product"](#your-product), and ["About you"](#about-you).
## Your needs
### How would you feel if you could no longer use MUI?
Over 93% of you would be disappointed if you could no longer use MUI (a sum of "Very disappointed" and "Somewhat disappointed"). That's in keeping with 94% of you who felt the same way when we asked this question in 2019 and 2020.
<img src="/static/blog/2021-developer-survey-results/1.png" style="width: 796px; margin-top: 16px; margin-bottom: 8px;" alt="Bar chart: 62.7% Very disappointed, 30.4% Somewhat disappointed, 6.9% Not disappointed." />
<p class="blog-description">1567 out of 1589 answered.</p>
Notably, 2021 saw a 10% loss in the "Very disappointed" category, and a comparable gain in those who would only be "Somewhat disappointed." This suggests that some of you may be less enthusiastic about MUI's products when compared with previous years, and that's something we need to evaluate moving forward.
Those who would be "Not disappointed"—a group that grew by 1%—were asked to explain why. Here's what they said:
**The number of available alternatives**
Lately, with each new day a new UI component library appears.
Because they aim to solve the same problems, these libraries often arrive at solutions that are very similar to one another.
The establishment of common industry-wide patterns makes it that much more difficult to stand out from the crowd.
Meanwhile, we're working hard to expand beyond our core products to provide you with experiences that other libraries can't match.
**The introduction of a paid product**
A big challenge with open-source is that maintainers capture very little value.
The MIT licensed model has enabled the growth of a large community of contributors as well as the MUI team itself, but it does have its limitations.
To push the products as forward as we believe it's possible, we needed a way to invest more in them.
[Open-core](https://en.wikipedia.org/wiki/Open-core_model) allows us to still offer an MIT licensed (free) version of the MUI X components while charging for additional features that require more attention (including support).
It's still early days for MUI X, though.
We introduced it at the end of 2020 and have been iterating not only on the components but on the model itself.
We still have a lot more ground to cover — only ~0.1% of our developer community has been convinced to upgrade to the paid Pro plan so far.
Whether or not you've taken the plunge, we'd love to hear your thoughts about this.
And if you want to understand more about our view of the open-source/commercial balance, check our [Stewardship page](https://mui-org.notion.site/Stewardship-542a2226043d4f4a96dfb429d16cf5bd).
**The breaking changes made in v5**
Our most recent release, MUI Core v5, introduced some important breaking changes.
The main problem we wanted to tackle was customizability: unlocking more styling options without compromising on performance.
This new styling solution still has a ways to go in terms of maturity, and there's no denying that it requires a considerable amount of work to migrate from v4.
For our part, we still have a lot of work to do to help you make the most of the new features in v5, and we welcome your feedback.
What can we do to help you succeed? If you have any ideas or suggestions, you're always welcome to share your thoughts by opening an issue on GitHub.
### How likely is it that you would recommend MUI to a friend or colleague?
This year we observed a decrease in Net Promoter Score (NPS): from 62 in 2020 to 46 in 2021.
56.4% of you were Promoters this year, down almost 6 percentage points from last year (62.2%).
We're still in a good place — an NPS score between 30 and 70 is considered great.
But we have much more to do to achieve an excellent score.
<img src="/static/blog/2021-developer-survey-results/2.png" style="width: 796px; margin-top: 16px; margin-bottom: 8px;" alt="Detractors: 10.88%, Neutrals: 32.69%, Promoters: 56.43%, Overall NPS: 46.
Scale: -100 to 0 needs improvements, 0 to 30 is good, 30 to 70 is great, and 70 to 100 is excellent." />
<p class="blog-description">1563 out of 1589 answered.</p>
### What is the main benefit you get from using MUI?
<img src="/static/blog/2021-developer-survey-results/3.png" style="width: 796px; margin-top: 16px; margin-bottom: 8px;" alt="This question results in 2019 - Design: 248; Time: 193; DX: 128; Components: 89; Customizability: 53; Documentation: 25; Accessibility: 5; TypeScript: 5; Community support: 4; This question results in 2021 - Time: 597; Design: 407; Components: 309; DX: 306; Customizability: 181; Documentation: 57; Community support: 26; Accessibility: 24; Performance: 17" />
<p class="blog-description">1422 out of 1589 answered this question in 2021.</p>
Here's what you liked the most about the product in 2021, compared to 2019:
- **Community (2.9x):** While the community itself doubled in size, appreciation for the community grew by 190% over that same time frame.
It looks like we're witnessing a network effect: with twice as many users, developers got three times more value from the community.
- **Accessibility (2.2x):** The community has definitely noticed the work we have put in to make our components more accessible.
Special thanks to Sebastian Silbermann [(@eps1lon)](https://github.com/eps1lon) for his continued help!
- **Customizability (1.6x):** Developers seem to be appreciating the new capabilities introduced in v5.
That said, we recognize that there is still more work to be done here, given the number of requests we've received to better solve this problem.
- **Components (1.6x):** We'll keep adding new components to the library as long as you continue to appreciate them this much!
- Component quality (no change): You know that we set the bar very high for the quality of our components.
This can be challenging as we continue to grow, because we expect nothing but the best from our team.
Thankfully, this result shows that our team of maintainers has done an excellent job, aiming for high standards.
- **Time (1.4x):** Mostly referring to saved time during UI development. This is an interesting one because it's not an issue that we specifically addressed.
Could this just be a result of the growing pressure in the market to build faster? Or because we somehow made this value proposition more noticeable? It could also be related to the next item.
- **Developer experience (1.1x):**
- Consistency (1.75x): We didn't work on this dimension, and yet it grew.
It's reasonable to assume that because we have more components than ever before, developers have started to notice how much more consistent their work is when they use MUI.
- Ease of use (no change): Could it be because ease of use is mostly defined by the React API (hooks), or is it because we haven't made any major API changes to optimize for ease of use? There could be a lot of work here for our new Developer Experience team.
And what has decreased:
- **Design (x0.75):** Material Design hasn't evolved with changing tastes, and our work on a second design system to address this hasn't progressed as quickly we anticipated.
- Material Design (x0.4): Its selling power is clearly fading.
- Look & feel (x1.17): This is surprising.
It seems to be a transfer effect: people who previously cared more about Material Design now care more about the outcome than the specification itself.
<br/>
<details>
<summary>Click to see the breakdown of categories.</summary>
<table>
<tr><th style="width: 40px;">597</th><th style="width: 700px;">time</th><tr>
<tr><th>407</th><th>design</th><tr>
<tr><td>148</td><td>design - look & feel</td><tr>
<tr><td>122</td><td>design - look & feel+</td><tr>
<tr><td>73</td><td>design - consistency</td><tr>
<tr><td>73</td><td>design - Material Design</td><tr>
<tr><td>6</td><td>design - ?</td><tr>
<tr><td>4</td><td>design - easy</td><tr>
<tr><td>2</td><td>design - responsiveness</td><tr>
<tr><td>1</td><td>design - time</td><tr>
<tr><th>309</th><th>components</th><tr>
<tr><td>173</td><td>components - quantity</td><tr>
<tr><td>124</td><td>components - quality</td><tr>
<tr><td>5</td><td>components - advanced</td><tr>
<tr><td>3</td><td>components - data grid</td><tr>
<tr><td>2</td><td>components - ?</td><tr>
<tr><td>1</td><td>components - autocomplete</td><tr>
<tr><td>1</td><td>components - base/unstyled</td><tr>
<tr><th>306</th><th>DX</th><tr>
<tr><td>221</td><td>DX - easy to use</td><tr>
<tr><td>49</td><td>DX - consistency</td><tr>
<tr><td>32</td><td>DX - API</td><tr>
<tr><td>4</td><td>DX - ?</td><tr>
<tr><th>181</th><th>customizability</th><tr>
<tr><th>57</th><th>docs</th><tr>
<tr><td>39</td><td>docs - ?</td><tr>
<tr><td>17</td><td>docs - quality</td><tr>
<tr><td>1</td><td>docs - quantity</td><tr>
<tr><th>26</th><th>community</th><tr>
<tr><th>24</th><th>accessibility</th><tr>
<tr><th>17</th><th>performance</th><tr>
<tr><td>15</td><td>performance - runtime</td><tr>
<tr><td>1</td><td>performance - bundle size</td><tr>
<tr><td>1</td><td>performance - ?</td><tr>
<tr><th>9</th><th>community support</th><tr>
<tr><th>5</th><th>icons</th><tr>
<tr><th>3</th><th>typescript</th><tr>
<tr><th>2</th><th>animations</th><tr>
</table>
</details>
### Please rate how much you agree or disagree with the following statements
<img src="/static/blog/2021-developer-survey-results/4.png" style="width: 796px; margin-top: 16px; margin-bottom: 8px;" alt="I can find most of the components I need (Strongly agree: 45.5%, Agree: 45.9%, Neutral: 6.2%, Disagree: 1.5%, Strongly Disagree 0.8%); I can easily customize the components to match the desired design (Strongly agree: 23.4%, Agree: 46.1%, Neutral: 18.6%, Disagree: 9%, Strongly Disagree 2.9%); I can find the answers to most of my questions in the documentation (Strongly agree: 24.1%, Agree: 50.1%, Neutral: 16.3%, Disagree: 7.6%, Strongly Disagree 1.9%); I find the library's performance to be great (Strongly agree: 26.4%, Agree: 44.3%, Neutral: 22.6%, Disagree: 4.7%, Strongly Disagree 2%); Whenever I needed to get help, I received helpful responses, Stack Overflow or GitHub (Strongly agree: 20.9%, Agree: 36.7%, Neutral: 36%, Disagree: 4.6%, Strongly Disagree 1.8%)" />
<p class="blog-description">1534 out of 1589 answered.</p>
It's a good thing to have a general sense of agreement with most of the statements, however, there's a considerably big gap between "Strongly agree" and "Agree" for all but the first statement. This highlights the need to continue pushing for even more quality in each of these dimensions (customizability, performance, and community support).
### What are your most important criteria for choosing a UI library?
<img src="/static/blog/2021-developer-survey-results/5.png" style="width: 796px; margin-top: 16px; margin-bottom: 8px;" alt="Ranked list: 1. The design - look and feel; 2. Customizability; 3. Documentation quality; 4. Comprehensiveness; 5. Performance; 6. Popularity; 7. Accessibility; 8. Offered support and help; 9. Bundle size" />
<p class="blog-description">1500 out of 1589 answered - Check <a href="https://www.typeform.com/help/a/ranking-question-360052767651/">Typeform's documentation</a> to understand ranking average calculations.</p>
This year we experimented with using Typeform to run the survey, which allows respondents to rank their choices.
This might have given us a richer perspective than we've been able to capture in the past, but in the end the results weren't too different from last year.
Design (look and feel) remains the most important criterion for choosing a UI library, and customization and documentation quality are still there in the top 3.
The notable difference this year seems to be performance climbing its way up, as it has been ranked as the fifth most important aspect.
### What else can we do to improve MUI for you?
<img src="/static/blog/2021-developer-survey-results/6.png" style="width: 796px; margin-top: 16px; margin-bottom: 8px;" alt="Word cloud of what we can do to improve MUI" />
<p class="blog-description">1007 out of 1589 answered this question in 2021.</p>
Here are the most recurring topics for improvement this year:
- **More components:** We continue to see requests for more advanced components such as charts, forms, and calendars, to name a few.
- **More examples:** Many of the existing learning resources are now outdated following the v5 upgrade, so we have a lot of work to do to show you how to make the most of our products.
- **Provide more themes:** Even with the launch of Material v3, Material Design is seen as outdated by many.
That's why we're working on a second design system that will offer the same high standard of quality as Material Design, but with an alternative design direction.
- **Fewer breaking changes:** MUI Core v5 introduced some important breaking changes, especially because of the new styling solution.
Rest assured that we don't expect to release any major updates this year—in fact, we aim to keep majors at least 12 months apart from each other.
- **Improve customization:** Common requests include making customization easier, providing more examples of common use-cases (like font-family and primary/secondary colors), and improving the theme capabilities.
Even with the popularity of Emotion and styled-components, there continues to be an enormous need to facilitate customization.
If you are interested in an analysis of the growing and decreasing pain, you can [head to the appendix](https://mui-org.notion.site/Raw-data-aa374141dcb3453dbfea301dcc437126#30728bf1bc8d4f70a1739fa20f11459a).
<details>
<summary>Click to see the breakdown of categories.</summary>
<table>
<tr><th style="width: 40px;">329</th><th style="width: 700px;">docs</th><tr>
<tr><th>72</th><th>docs - ?</th><tr>
<tr><td>62</td><td>docs - more examples</td><tr>
<tr><td>29</td><td>docs - more templates</td><tr>
<tr><td>28</td><td>docs - beginner friendly</td><tr>
<tr><td>28</td><td>docs - tutorials</td><tr>
<tr><td>19</td><td>docs - API</td><tr>
<tr><td>19</td><td>docs - custom design system</td><tr>
<tr><td>16</td><td>docs - more comprehensive</td><tr>
<tr><td>15</td><td>docs - content quality</td><tr>
<tr><td>9</td><td>docs - organization</td><tr>
<tr><td>8</td><td>docs - smaller demos</td><tr>
<tr><td>6</td><td>docs - content translation</td><tr>
<tr><td>5</td><td>docs - search</td><tr>
<tr><td>4</td><td>docs - slow to navigate</td><tr>
<tr><td>3</td><td>docs - link to source</td><tr>
<tr><td>3</td><td>docs - starter example</td><tr>
<tr><td>3</td><td>docs - integration with third-parties</td><tr>
<tr><td>1</td><td>docs - visual component discovery</td><tr>
<tr><th>300</th><th>more components</th><tr>
<tr><td>145</td><td>more components - ?</td><tr>
<tr><td>26</td><td>more components - form</td><tr>
<tr><td>21</td><td>more components - charts</td><tr>
<tr><td>17</td><td>more components - carousel</td><tr>
<tr><td>12</td><td>more components - lab to core</td><tr>
<tr><td>9</td><td>more components - enterprise apps</td><tr>
<tr><td>8</td><td>more components - upload</td><tr>
<tr><td>7</td><td>more components - big calendar</td><tr>
<tr><td>7</td><td>more components - drag and drop</td><tr>
<tr><td>6</td><td>more components - MUI X Pro</td><tr>
<tr><td>5</td><td>more components - navbar</td><tr>
<tr><td>5</td><td>more components - image</td><tr>
<tr><td>4</td><td>more components - inputs</td><tr>
<tr><td>4</td><td>more components - rich text editor</td><tr>
<tr><td>3</td><td>more components - MUI X</td><tr>
<tr><td>2</td><td>more components - layout</td><tr>
<tr><td>2</td><td>more components - number input</td><tr>
<tr><td>2</td><td>more components - speed to release it</td><tr>
<tr><td>2</td><td>more components - virtualization</td><tr>
<tr><td>1</td><td>more components - color picker</td><tr>
<tr><td>1</td><td>more components - data display</td><tr>
<tr><td>1</td><td>more components - link</td><tr>
<tr><td>1</td><td>more components - loading button</td><tr>
<tr><td>1</td><td>more components - maps</td><tr>
<tr><td>1</td><td>more components - mobile</td><tr>
<tr><td>1</td><td>more components - nested menu</td><tr>
<tr><td>1</td><td>more components - OTP</td><tr>
<tr><td>1</td><td>more components - photo viewer</td><tr>
<tr><td>1</td><td>more components - scrollspy</td><tr>
<tr><td>1</td><td>more components - slider</td><tr>
<tr><td>1</td><td>more components - time picker</td><tr>
<tr><td>1</td><td>more components - tree select</td><tr>
<tr><th>265</th><th>customization</th><tr>
<tr><td>71</td><td>customization - ?</td><tr>
<tr><td>69</td><td>customization - easier</td><tr>
<tr><td>44</td><td>customization - docs</td><tr>
<tr><td>27</td><td>customization - improve custom themes</td><tr>
<tr><td>26</td><td>customization - color</td><tr>
<tr><td>25</td><td>customization - theming</td><tr>
<tr><td>3</td><td>customization - theme gallery (coming from the community)</td><tr>
<tr><th>212</th><th>system</th><tr>
<tr><td>37</td><td>system - ?</td><tr>
<tr><td>36</td><td>system - makeStyles back</td><tr>
<tr><td>20</td><td>system - docs</td><tr>
<tr><td>15</td><td>system - SASS</td><tr>
<tr><td>11</td><td>system - interoperability with Tailwind CSS</td><tr>
<tr><td>14</td><td>system - simplify</td><tr>
<tr><td>8</td><td>system - CSS variables</td><tr>
<tr><td>7</td><td>system - interoperability</td><tr>
<tr><td>7</td><td>system - no CSS-in-JS runtime</td><tr>
<tr><td>6</td><td>system - CSS modules</td><tr>
<tr><td>6</td><td>system - dark mode</td><tr>
<tr><td>6</td><td>system - utility class names</td><tr>
<tr><td>5</td><td>system - verbosity</td><tr>
<tr><td>5</td><td>system - performance</td><tr>
<tr><td>4</td><td>system - CSS API</td><tr>
<tr><td>4</td><td>system - styled-components</td><tr>
<tr><td>3</td><td>system - generated classes</td><tr>
<tr><td>3</td><td>system - variant</td><tr>
<tr><td>3</td><td>system - CSS that can be shared outside of React</td><tr>
<tr><td>3</td><td>system - state customization</td><tr>
<tr><td>3</td><td>system - theme</td><tr>
<tr><td>1</td><td>system - inline styling</td><tr>
<tr><td>1</td><td>system - decide on styling solution</td><tr>
<tr><td>1</td><td>system - duplicate CSS properties</td><tr>
<tr><td>1</td><td>system - transient props</td><tr>
<tr><td>1</td><td>system - typescript intellisense</td><tr>
<tr><td>1</td><td>system - use more sx oversyled</td><tr>
<tr><th>172</th><th>design</th><tr>
<tr><td>51</td><td>design - provide more themes (not just Material Design)</td><tr>
<tr><td>28</td><td>design - make the default theme look & feel better</td><tr>
<tr><td>27</td><td>design - push @mui/base more</td><tr>
<tr><td>24</td><td>design - Material Design v3</td><tr>
<tr><td>13</td><td>design - drop Material Design</td><tr>
<tr><td>10</td><td>design - ?</td><tr>
<tr><td>7</td><td>design - denser UI for enterprise apps</td><tr>
<tr><td>6</td><td>design - block templates</td><tr>
<tr><td>3</td><td>design - responsiveness</td><tr>
<tr><td>2</td><td>design - mobile</td><tr>
<tr><td>1</td><td>design - color gradients</td><tr>
<tr><th>109</th><th>performance</th><tr>
<tr><td>46</td><td>performance - bundle size</td><tr>
<tr><td>36</td><td>performance - ?</td><tr>
<tr><td>16</td><td>performance - runtime</td><tr>
<tr><td>4</td><td>performance - fewer DOM node/React components</td><tr>
<tr><td>2</td><td>performance</td><tr>
<tr><td>2</td><td>performance - docs</td><tr>
<tr><td>1</td><td>performance - animations</td><tr>
<tr><td>1</td><td>performance - in dev mode</td><tr>
<tr><td>1</td><td>performance - unecesseary prefixes</td><tr>
<tr><th>97</th><th>DX</th><tr>
<tr><td>27</td><td>DX - simpler</td><tr>
<tr><td>20</td><td>DX - API</td><tr>
<tr><td>17</td><td>DX - higher-level component API</td><tr>
<tr><td>6</td><td>DX - lower-level component API</td><tr>
<tr><td>5</td><td>DX - import</td><tr>
<tr><td>5</td><td>DX - lightweight</td><tr>
<tr><td>3</td><td>DX - debugging</td><tr>
<tr><td>2</td><td>DX - boilerplate</td><tr>
<tr><td>2</td><td>DX - fewer packages</td><tr>
<tr><td>2</td><td>DX - expose hooks</td><tr>
<tr><td>1</td><td>DX - class names</td><tr>
<tr><td>1</td><td>DX - ?</td><tr>
<tr><td>1</td><td>DX - composability</td><tr>
<tr><td>1</td><td>DX - faster releases</td><tr>
<tr><td>1</td><td>DX - fewer releases</td><tr>
<tr><td>1</td><td>DX - helper functions</td><tr>
<tr><td>1</td><td>DX - versioning</td><tr>
<tr><td>1</td><td>DX - vscode plugin</td><tr>
<tr><th>75</th><th>data grid</th><tr>
<tr><td>62</td><td>data grid - ?</td><tr>
<tr><td>3</td><td>data grid - docs</td><tr>
<tr><td>2</td><td>data grid - excel</td><tr>
<tr><td>1</td><td>data grid - bundle size</td><tr>
<tr><td>1</td><td>data grid - column pinning</td><tr>
<tr><td>1</td><td>data grid - filtering</td><tr>
<tr><td>1</td><td>data grid - full screen</td><tr>
<tr><td>1</td><td>data grid - grouping</td><tr>
<tr><td>1</td><td>data grid - large dataset</td><tr>
<tr><td>1</td><td>data grid - master panel</td><tr>
<tr><td>1</td><td>data grid - nesting - export options</td><tr>
<tr><th>61</th><th>free vs. paid</th><tr>
<tr><td>18</td><td>free vs. paid - all MIT</td><tr>
<tr><td>8</td><td>free vs. paid - cheaper Pro plan</td><tr>
<tr><td>8</td><td>free vs. paid - no existing features going paid</td><tr>
<tr><td>7</td><td>free vs. paid - more MIT</td><tr>
<tr><td>6</td><td>free vs. paid - data grid more MIT</td><tr>
<tr><td>5</td><td>free vs. paid - no Pro plan (premium can stay)</td><tr>
<tr><td>4</td><td>free vs. paid - date picker more MIT</td><tr>
<tr><td>2</td><td>free vs. paid - remove docs ads</td><tr>
<tr><td>1</td><td>free vs. paid - cheaper Premium plan</td><tr>
<tr><td>1</td><td>free vs. paid - design kit more MIT</td><tr>
<tr><td>1</td><td>free vs. paid - use donations</td><tr>
<tr><th>61</th><th>fewer breaking changes</th><tr>
<tr><th>47</th><th>typescript</th><tr>
<tr><td>28</td><td>typescript - ?</td><tr>
<tr><td>11</td><td>typescript - faster check</td><tr>
<tr><td>5</td><td>typescript - docs</td><tr>
<tr><td>2</td><td>typescript - more support</td><tr>
<tr><td>1</td><td>typescript - converter</td><tr>
<tr><td>1</td><td>typescript - intellisense</td><tr>
<tr><th>41</th><th>date picker</th><tr>
<tr><td>18</td><td>date picker - ?</td><tr>
<tr><td>5</td><td>date picker - make stable</td><tr>
<tr><td>3</td><td>date picker - range selection</td><tr>
<tr><td>2</td><td>date picker - bugs</td><tr>
<tr><td>2</td><td>date picker - single range input</td><tr>
<tr><td>2</td><td>date picker - time clock is hideous</td><tr>
<tr><td>2</td><td>date picker - customizability</td><tr>
<tr><td>1</td><td>date picker - dayjs</td><tr>
<tr><td>1</td><td>date picker - add range</td><tr>
<tr><td>1</td><td>date picker - design</td><tr>
<tr><td>1</td><td>date picker - docs</td><tr>
<tr><td>1</td><td>date picker - keyboard</td><tr>
<tr><td>1</td><td>date picker - locales</td><tr>
<tr><td>1</td><td>date picker - rewrite</td><tr>
<tr><th>26</th><th>community</th><tr>
<tr><td>14</td><td>community - nurture</td><tr>
<tr><td>9</td><td>community - support</td><tr>
<tr><td>2</td><td>community - release communication</td><tr>
<tr><td>1</td><td>community - v4 support</td><tr>
<tr><th>20</th><th>icons</th><tr>
<tr><td>12</td><td>icons - more</td><tr>
<tr><td>3</td><td>icons - ?</td><tr>
<tr><td>1</td><td>icons - animation</td><tr>
<tr><td>1</td><td>icons - built-in</td><tr>
<tr><td>1</td><td>icons - dynamic loading</td><tr>
<tr><td>1</td><td>icons - fontawesome</td><tr>
<tr><td>1</td><td>icons - other libraries</td><tr>
<tr><th>19</th><th>accessibility</th><tr>
<tr><td>9</td><td>accessibility - implementation</td><tr>
<tr><td>6</td><td>accessibility - docs</td><tr>
<tr><td>2</td><td>accessibility - ?</td><tr>
<tr><td>2</td><td>accessibility - full audit</td><tr>
<tr><th>15</th><th>react native</th><tr>
<tr><th>10</th><th>low-code</th><tr>
<tr><td>7</td><td>low-code - design system creator</td><tr>
<tr><td>2</td><td>low-code - generate code from design files</td><tr>
<tr><td>1</td><td>low-code - UI builder</td><tr>
<tr><th>10</th><th>more opinionated</th><tr>
<tr><th>9</th><th>animations</th><tr>
<tr><td>6</td><td>animations - new API</td><tr>
<tr><td>1</td><td>animations - Framer Motion</td><tr>
<tr><td>1</td><td>animations - on existing components</td><tr>
<tr><td>1</td><td>animations - performance</td><tr>
<tr><th>7</th><th>fix more bugs</th><tr>
<tr><th>7</th><th>support other frameworkds (e.g. Vue)</th><tr>
<tr><th>5</th><th>autocomplete</th><tr>
<tr><td>3</td><td>autocomplete - ?</td><tr>
<tr><td>1</td><td>autocomplete - abbreviation</td><tr>
<tr><td>1</td><td>autocomplete - consistency with text field</td><tr>
<tr><th>4</th><th>legacy browser support</th><tr>
<tr><th>3</th><th>components consistency</th><tr>
<tr><th>2</th><th>less opinionanted</th><tr>
<tr><th>2</th><th>fix RTL</th><tr>
<tr><th>2</th><th>class components</th><tr>
</table>
</details>
Have ideas for improvements? Please share them with us! Here's how to make sure that your requests get top priority:
- When you create an issue to request features or components in the MUI Core or MUI X repositories, we'll label it as `Waiting for upvotes`.
The more votes your issue receives, the higher a priority it will become—so make sure to structure, research, and justify your request so it resonates with other community members.
- When requesting a new component, make sure to benchmark existing implementations of it in the wild so we can see what works and what we could improve on.
- Try to explain the problem you're having as clearly as possible — it's often the case that we already have a component to solve it.
- If you're requesting easier customization, make sure to demonstrate the desired outcome, and explain where you're having trouble in as much detail as you can.
These requests often highlight opportunities for us to improve our documentation.
## Your product
### What were you primarily using before MUI?
<img src="/static/blog/2021-developer-survey-results/7.png" style="width: 796px; margin-top: 16px; margin-bottom: 8px;" alt="Bootstrap: 40.6%; Started with MUI: 37.4%; Tailwind:: 4.8%; Ant Design: 4.8%; Angular Material: 4%; Semantic-UI: 4%; Other: 3.8%; Chakra UI: 0.7%" />
<p class="blog-description">1389 of 1589 answered.</p>
These results are not too different from last year, with the exception that far more developers reported starting with MUI (13% in 2020, and 37% in 2021).
It's very encouraging to know that so many of you are building your products with MUI right from the start!
### Are you using any of these in addition to MUI?
<img src="/static/blog/2021-developer-survey-results/8.png" style="width: 796px; margin-top: 16px; margin-bottom: 8px;" alt="Nope, just MUI: 70.7%; Tailwind: 10.3%; Bootstrap: 9.8%; Ant Design: 4%; Semantic-UI: 1.7%; Other: 1.6%; Chakra UI: 1.2%; Angular Material: 0.8%" />
<p class="blog-description">1468 out of 1589 answered.</p>
We're glad to see that MUI largely covers all of your needs for a component UI library—this is a major priority for us.
### Who are you building for?
<img src="/static/blog/2021-developer-survey-results/9.png" style="width: 796px; margin-top: 16px; margin-bottom: 8px;" alt="For the company I work at: 65.6%; For my personal side project: 20.8%; For a client: 12.9%; Other: 0.7%" />
<p class="blog-description">1523 out of 1589 answered.</p>
When compared with last year's results, client work and personal projects have swapped places this year.
Maybe v5 got developers interested enough to try it on their own sites and apps? It's interesting to see, in any case.
### Who do you collaborate most with?
<img src="/static/blog/2021-developer-survey-results/10.png" style="width: 796px; margin-top: 16px; margin-bottom: 8px;" alt="Other developers: 67.2%; Designers: 34.3%; Product managers: 29.2%; No one, it's just me: 28.9%; Other: 0.9%" />
<p class="blog-description">1527 out of 1589 answered.</p>
This is a new question in our annual survey, and the results highlight the fact that our documentation is not just for developers.
It's crucial for our docs—and even the code itself—to be easily understood by designers, product managers, and other less technical team members who may be stakeholders in engineering projects.
### How many web applications did you or your team deliver using MUI this year?
<img src="/static/blog/2021-developer-survey-results/11.png" style="width: 796px; margin-top: 16px; margin-bottom: 8px;" alt="0-1: 494; 2-3: 381; 4-5: 122; 6-10: 26; 10+: 28" />
<p class="blog-description">1051 out of 1589 answered.</p>
Roughly half (47%) of those who responded to this question shipped one app or simply maintained an existing app.
Impressively, 5% of respondents delivered six or more apps, and more than half of those surpassed 10!
### Which MUI products do you use in your application?
<img src="/static/blog/2021-developer-survey-results/12.png" style="width: 796px; margin-top: 16px; margin-bottom: 8px;" alt="MUI Core: MIT licensed foundational components, right now available with Material Design: 96.6%; MUI X: collection of advanced components available under MIT and commercial licenses: 14.7%; MIT License: 126 responses; Commercial licenses: 99 responses" />
<p class="blog-description">1551 out of 1589 answered.</p>
It's not surprising to find out that most of our user base is here for MUI Core.
But it is very encouraging for us to see such a high proportion of MUI X users operating with commercial licenses, and we are excited to continue expanding on our paid products for these users.
There are a lot of opportunities in the MUI X space to unpack.
Let's explore a little bit further below.
### Did you know what MUI X was prior to this survey?
<img src="/static/blog/2021-developer-survey-results/13.png" style="width: 796px; margin-top: 16px; margin-bottom: 8px;" alt="Yes: 54.5%; No: 45.5%" />
<p class="blog-description">1312 out of 1589 answered.</p>
A large chunk of you didn't know what MUI X is prior to the survey, which makes it clear that we still have a lot to do to expand its reach.
### Are you currently using any paid UI component library?
<img src="/static/blog/2021-developer-survey-results/14.png" style="width: 796px; margin-top: 16px; margin-bottom: 8px;" alt="Yes: 11.8%; No: 88.2%" />
<p class="blog-description">1584 out of 1589 answered.</p>
The results are not very different from last year, aside from a slight increase of respondents saying yes.
The majority of respondents don't use any paid libraries, but those who do are mostly using MUI X. This demonstrates that some of our assumptions and execution might be correct! Developers' needs appears to not be completely fulfilled by the OSS ecosystem.
### How can we improve the Data Grid for you?
<img src="/static/blog/2021-developer-survey-results/15.png" style="width: 796px; margin-top: 16px; margin-bottom: 8px;" alt="Customizability: 21.9%; Cheaper Pro plan: 17.2%; More features: 12.5%; Fix features: 9.4%; Improve docs: 6.3%; Look & feel: 6.3%; Maintain it: 4.7%; Bugs: 3.1%; DX: MUI Core consistency: 3.1%; Performance: 3.1%; Transition: 3.1%; SSR: 1.6%" />
<p class="blog-description">64 out of 1589 answered.</p>
- **Customizability:** This is a common topic for us, and it comes up often when discussing MUI X.
Your feedback tells us that we need to double down on our efforts to make customization easier.
We also recognize that we are still lacking some important documentation around theming, and headless APIs.
- **Cheaper Pro plan:** We know it can be out of range for a lot of developers, and that's why the free version is already packed with many features.
MUI mainly develops open-source software, and we deeply value the OSS ethos of freely sharing what we build so that others can use it and improve upon it.
- The price of our Pro plan positions it as a product intended for use by teams at professional organizations.
That said, many who left feedback on the price are individuals, so there might be an opportunity to expand our offerings for those not backed by their company.
- **More features & feature fixes:** Collapsible rows, column resizing, and features for ERP apps were some of the features requested.
And regarding features to fix, the most common requests were pagination with REST APIs, backend filtering, and cell editor.
- **Improvements to the documentation:** The data grid docs could certainly use a major overhaul—we're working on it.
- **Improvements to the look and feel:** Data grid builders want more default design options beyond Material.
In terms of UX improvements, many developers mention the filtering experience specifically.
<details>
<summary>Click to see the breakdown of categories.</summary>
<table>
<tr><th style="width: 40px;">14</th><th style="width: 700px;">customizability</th><tr>
<tr><td>9</td><td>customizability - style</td><tr>
<tr><td>3</td><td>customizability - ?</td><tr>
<tr><td>2</td><td>customizability - docs</td><tr>
<tr><th>11</th><th>cheaper Pro plan</th><tr>
<tr><th>8</th><th>more features</th><tr>
<tr><td>3</td><td>more features - ?</td><tr>
<tr><td>2</td><td>more features - master detail</td><tr>
<tr><td>1</td><td>more features - row editing</td><tr>
<tr><td>1</td><td>more features - column pinning</td><tr>
<tr><td>1</td><td>more features - column resizing</td><tr>
<tr><th>6</th><th>fix features</th><tr>
<tr><td>3</td><td>fix features - filtering</td><tr>
<tr><td>1</td><td>fix features - editing</td><tr>
<tr><td>1</td><td>fix features - pagination</td><tr>
<tr><td>1</td><td>fix features - server-side</td><tr>
<tr><th>5</th><th>docs</th><tr>
<tr><td>4</td><td>docs - ?</td><tr>
<tr><td>1</td><td>docs - more examples</td><tr>
<tr><th>4</th><th>look and feel</th><tr>
<tr><th>3</th><th>maintain it</th><tr>
<tr><th>2</th><th>bugs</th><tr>
<tr><th>2</th><th>DX - MUI Core consistency</th><tr>
<tr><th>2</th><th>performance</th><tr>
<tr><th>2</th><th>translation</th><tr>
<tr><th>1</th><th>a11y</th><tr>
<tr><th>1</th><th>easier installation</th><tr>
<tr><th>1</th><th>fewer breaking changes</th><tr>
<tr><th>1</th><th>hook-only API</th><tr>
<tr><th>1</th><th>SSR</th><tr>
</table>
</details>
### How can we improve Data Grid Pro for you?
<img src="/static/blog/2021-developer-survey-results/16.png" style="width: 796px; margin-top: 16px; margin-bottom: 8px;" alt="More features: 39.8%; Customizability: 20.4%; Fix features: 15.1%; Performance: 5.4%; Cheaper Premium plan: 3.2%; Improve docs: 3.2%; DX - API: 2.2%; LGPL license: 2.2%; More components: 2.2%" />
<p class="blog-description">75 out of 1589 answered.</p>
- **More features:** [Grouping](/x/react-data-grid/row-grouping/) was the most requested feature for the Data Grid Pro, followed by [master detail](/x/react-data-grid/master-detail/), aggregation, search, [tree data](/x/react-data-grid/tree-data/), and [column pinning](/x/react-data-grid/column-pinning/).
We've already released some of these in the time it took us to analyze the survey results.
Check the links to see their docs and demos.
Alternatively, you can follow [the public roadmap](https://github.com/mui/mui-x/projects/1) to see when the others will land.
- **Customizability:** The majority of requests about customizability were asking for possibilities to tweak data grid interactions, which we need to delve into more deeply to better understand.
Following next were requests for more style customizability, and more documentation on customization.
- **Fix features:** Filtering got first place as the most requested feature to fix on Data Grid Pro.
Following next were lazy loading and server-side rendering support.
- **Performance:** Requests about performance were mostly spread out between runtime and bundle size.
We must admit that we have put almost no effort into optimizing the bundle size so far.
There is likely some low-hanging fruit there.
<details>
<summary>Click to see the breakdown of categories.</summary>
<table>
<tr><th style="width: 40px;">37</th><th style="width: 700px;">more features</th><tr>
<tr><td>6</td><td>more features - grouping</td><tr>
<tr><td>6</td><td>more features - master detail</td><tr>
<tr><td>6</td><td>more features - roadmap</td><tr>
<tr><td>4</td><td>more features - ?</td><tr>
<tr><td>3</td><td>more features - aggregation</td><tr>
<tr><td>3</td><td>more features - search</td><tr>
<tr><td>3</td><td>more features - tree data</td><tr>
<tr><td>2</td><td>more features - column pinning</td><tr>
<tr><td>2</td><td>more features - pivot</td><tr>
<tr><td>1</td><td>more features - excel</td><tr>
<tr><td>1</td><td>more features - row reordering</td><tr>
<tr><th>19</th><th>customizability</th><tr>
<tr><td>7</td><td>customizability - behavior</td><tr>
<tr><td>5</td><td>customizability - style</td><tr>
<tr><td>4</td><td>customizability - docs</td><tr>
<tr><td>2</td><td>customizability - ?</td><tr>
<tr><td>1</td><td>customizability - charts in cells</td><tr>
<tr><th>14</th><th>fix features</th><tr>
<tr><td>10</td><td>fix features - filtering</td><tr>
<tr><td>2</td><td>fix features - lazy loading</td><tr>
<tr><td>2</td><td>fix features - server-side</td><tr>
<tr><th>5</th><th>performance</th><tr>
<tr><td>3</td><td>performance - ?</td><tr>
<tr><td>1</td><td>performance - bundle size</td><tr>
<tr><td>1</td><td>performance - runtime</td><tr>
<tr><th>4</th><th>docs</th><tr>
<tr><td>3</td><td>docs - ?</td><tr>
<tr><td>1</td><td>docs - more examples</td><tr>
<tr><th>3</th><th>cheaper premium plan</th><tr>
<tr><th>2</th><th>bugs</th><tr>
<tr><th>2</th><th>DX - API</th><tr>
<tr><th>2</th><th>LGPL License</th><tr>
<tr><th>2</th><th>more components - treeview</th><tr>
<tr><th>2</th><th>overflow text</th><tr>
<tr><th>1</th><th>DX - MUI Core consistency</th><tr>
<tr><th>1</th><th>UX</th><tr>
</table>
</details>
### What were you using before the data grid?
<img src="/static/blog/2021-developer-survey-results/17.png" style="width: 796px; margin-top: 16px; margin-bottom: 8px;" alt="In house: 29.9%; MUI Table: 17.9%; Nothing: 7.5%; material-table: 6%; material-datatables: 6%; Sencha: 6%; Kendo UI: 4.5%; react-table: 4.5%; Bootstrap Table: 3%; AG Grid: 3%; datatables.net: 3%; JSP: 1.5%" />
<p class="blog-description">149 out of 1589 answered.</p>
It's interesting to see that a lot of you are building your own in-house data grids.
We'd love to know more about why your team made this choice, especially because we know exactly how much work it can be.
Also, it's refreshing to see that the standard MUI table components are adequate for many of you.
### What are you building?
<img src="/static/blog/2021-developer-survey-results/18.png" style="width: 796px; margin-top: 16px; margin-bottom: 16px;" alt="Dashboard admin applications: 26.3%; Enterprise applications: 25.9%; A custom design system: 9.7%; Landing page: 8.1%; E-commerce application: 7.8%; Personal website/portfolio: 6.9%; CMS: 6.1%; Just playing with tech: 4.6%; Blog: 2.8%; Other: 1.4%" />
Enterprise, dashboard applications, and design systems continue to be in the top 3, similar to last year.
What's changed is that developers are now using MUI more to build e-commerce apps and portfolios, which is pretty cool.
We'd love to see them! Feel free to share in the ["Who's using Material UI?" issue](https://github.com/mui/material-ui/issues/22426).
### What delivery mechanisms are you using?
<img src="/static/blog/2021-developer-survey-results/19.png" style="width: 796px; margin-top: 16px; margin-bottom: 8px;" alt="Single-page app (Create React App, etc): 74.7%; Server-side rendered website (Next.js, Gastby, etc): 20.8%; Desktop app (Electron, etc): 3.5%; Native mobile app (Cordova, etc): 0.6%; Other: 0.4%" />
<p class="blog-description">1509 out of 1589 answered.</p>
### What type system are you using?
<img src="/static/blog/2021-developer-survey-results/20.png" style="width: 796px; margin-top: 16px; margin-bottom: 8px;" alt="TypeScript: 63.8%; None: 18%; prop-types: 16.6%; Flow: 1.4%; Other: 0.2%" />
<p class="blog-description">1501 out of 1589 answered.</p>
These results are very different from last year—TypeScript took off, and it's now the primary type system used out there.
### Which framework are you using, if any?
<img src="/static/blog/2021-developer-survey-results/21.png" style="width: 796px; margin-top: 16px; margin-bottom: 8px;" alt="Create React App: 62.4%; Next.js: 21.9%; Custom webpack: 10.7%; None: 2.6%; Gatsby: 0.9%; Other: 1.5%" />
<p class="blog-description">1497 out of 1589 answered.</p>
This year we saw a considerable bump the use of Next.js (compared with 12.4% in 2020), which is not surprising due to its increasing popularity and the advancements it gained in 2021.
### What styling solution are you using?
<img src="/static/blog/2021-developer-survey-results/22.png" style="width: 796px; margin-top: 16px; margin-bottom: 8px;" alt="MUI Core v4 (JSS): 45%; Styled components: 37.9%; Emotion: 30.2%; SASS: 20.8%; CSS modules: 18.9%; Vanilla CSS: 17.6%; Tailwind CSS: 9.1%; Stitches: 0.4%; Other: 1.2%" />
<p class="blog-description">1492 out of 1589 answered.</p>
As the MUI Core v5 release is relatively recent, we expect to see many developers still using JSS, and there will probably always be some of you who prefer it.
But the growth of Emotion and styled-components here is noteworthy, because they are what our new styling solution is based on.
This year we'll be focusing on expanding and refining [MUI System](/system/getting-started/the-sx-prop/) to further improve upon this new styling solution.
### Did you recently migrate to MUI Core v5?
<img src="/static/blog/2021-developer-survey-results/23.png" style="width: 796px; margin-top: 16px; margin-bottom: 8px;" alt="Yes: 63.3%; No: 36.7%" />
<p class="blog-description">1546 out of 1589 answered.</p>
Though many of you who answered the survey have already migrated, we still have many more to convince to come along with us.
For the year ahead we'll focus strongly on refining the documentation, and improving automation tools.
### What's the statement that most defines your migration experience?
<img src="/static/blog/2021-developer-survey-results/24.png" style="width: 796px; margin-top: 16px; margin-bottom: 8px;" alt="It was tricky but MUI's documentation and resources helped me to get it right: 43%; It was smooth and it is now working fine: 38.5%; It wasn't good, I had many problems and it took me a long time to finish: 14.3%; It was bad and I ended up regretting it: 2.8%; Other: 1.4%" />
<p class="blog-description">930 out of 1589 answered.</p>
### What could MUI do to improve the migration experience?
<img src="/static/blog/2021-developer-survey-results/25.png" style="width: 796px; margin-top: 16px; margin-bottom: 8px;" alt="General documentation improvements: 43.2%; Automation: 20.7%: Fewer breaking changes: 15.6%; Fewer styling solution breaking changes: 8.5%; More tutorials: 5.4%; More styling solution migration tutorial: 4.4%; Migrate Core and X together: 1%" />
<p class="blog-description">472 out of 1589 answered.</p>
- **General documentation improvement:** Documentation plays a huge part in defining the developer experience.
We definitely need to refine our writing, provide more examples, and offer more beginner-friendly resources.
- **Automation:** We prepared codemods to help with the v5 migration, given the number of changes.
This has been met with positive feedback, which is encouraging since it's our first time providing comprehensive tools to automate the migration process.
However, it is becoming clear how and when the codemods weren't too effective, so we'll make sure to refine it more.
### Could you share the reason why you haven't migrated yet?
<img src="/static/blog/2021-developer-survey-results/26.png" style="width: 796px; margin-top: 16px; margin-bottom: 8px;" alt="No bandwidth: 28.4%; Started in v5: 14.6%; Afraid of amount of breaking changes: 12.3%; Already planned but haven't started: 9.5%; Missing incentive: 8.5%; Not a priority: 7.3%; Don't like new styling solution: 4%; Blocked by 3rd party dependencies: 3.3%; Didn't know about it: 3.3%; Migration is in process: 3.3%; Had regressions, therefore came back to v4: 1.3%; Waiting to become stable: 1.3%" />
<p class="blog-description">441 out of 1589 answered.</p>
- **No bandwidth / not a priority / blocked by third-party dependencies:** These reasons can all be lumped together as "forces beyond your control." That's to be expected, but we'll continue to do what we can to persuade your team to migrate, and to make the migration as smooth as possible when you're ready.
- **Afraid of the amount of breaking changes:** That fear is understandable, and we still have a great deal of work to do with documentation, automation, and other resources to help minimize the friction involved in migrating.
- **Don't like the new styling solution:** We believe that's totally fair.
Not everyone will buy every move.
However, as with any open-source project, you always have the opportunity to weigh in and leave your thoughts about any given endeavor we're considering.
[The issue discussing the chosen styling solution](https://github.com/mui/material-ui/issues/22342) was a big one, and every contribution made a difference in the ultimate decision.
Please don't hesitate to participate in these open discussions—especially if you see something you disagree with.
- **Didn't know about it:** That's something we really need to work on! We'll be exploring new ways to engage with our community in the coming months.
- **Regressions - had to go back to v4:** If this happens to you, please open an issue regarding the problems you're facing and we'll be happy to guide you.
### Have you, or anyone from your team, used any low-code tools for helping with the development of your product?
<img src="/static/blog/2021-developer-survey-results/27.png" style="width: 796px; margin-top: 16px; margin-bottom: 8px;" alt="Yes: 16.1%; No: 83.9%" />
<p class="blog-description">1542 out of 1589 answered.</p>
We see a lot of potential in low-code tools to reach a much wider audience beyond developers, for better collaboration and faster development.
Since our existing users are quite tech-literate people, it shouldn't be surprising that over 80% of you are not using low-code tools.
But for the 16% who said yes, we had the following questions.
### What did it help you build?
<img src="/static/blog/2021-developer-survey-results/28.png" style="width: 796px; margin-top: 16px; margin-bottom: 8px;" alt="An internal tool: 22.5%; Landing pages: 22.1%; Analytics dashboard: 17.6%; A design system: 15.6%; E-commerce storefront: 8.6%; A simple customer-facing mobile app: 6.6%; Other: 7%" />
<p class="blog-description">244 out of 1589 answered.</p>
MUI users are mainly working with low-code tools to build internal tools, landing pages, and analytics dashboards.
These findings align with what the rest of our users are building as well.
But it is great to see that there are low-code tools in the market that developers trust.
### If MUI considered building a low-code tool, what primary use-case would match your needs?
<img src="/static/blog/2021-developer-survey-results/29.png" style="width: 796px; margin-top: 16px; margin-bottom: 8px;" alt="Deliver a React design system: 22.2%; Generate high-quality React codebase after visual building: 19.2%; Building dashboards for rapid data visualization: 18.3%; Higher fidelity prototyping and demoing for accurate design handoff: 13.6%; Building internal apps when pro-code is overkill: 11.4%; Shipping landing pages with my existing React design system: 7.3%; Shipping production simple apps before moving to pro-code: 6.2%; Other: 1.8%" />
<p class="blog-description">1200 out of 1589 answered.</p>
Developers are mostly interested in React design systems, codebase generators, tools for internal needs, data visualization, and prototyping.
These needs are both for internal and customer-facing use-cases.
## About you
### How did you first hear about MUI?
<img src="/static/blog/2021-developer-survey-results/30.png" style="width: 796px; margin-top: 16px; margin-bottom: 8px;" alt="Organic search: 57.8%; Word of mouth: 25.8%; Social media: 8.4%; Blog: 4.4%; Other: 3.5%" />
<p class="blog-description">1417 out of 1589 answered.</p>
### Which of the following best describes your current job role?
<img src="/static/blog/2021-developer-survey-results/31.png" style="width: 796px; margin-top: 16px; margin-bottom: 8px;" alt="Full-stack developer: 52.6%; Front-end developer: 30.5%; Entrepreneur (I do it all!): 7.5%; Beginner learning web development: 2.6%; Engineering Manager: 2.6%; Back-end developer: 1.1%; Designer: 1%; Product Manager: 0.7%; Other: 1.3%" />
<p class="blog-description">1497 out of 1589 answered.</p>
### How many total employees work at your current place of employment?
<img src="/static/blog/2021-developer-survey-results/32.png" style="width: 796px; margin-top: 16px; margin-bottom: 8px;" alt="0-1: 187; 2-10: 358; 11-20: 136; 21-50: 139; 51-100: 97; 100+: 305" />
<p class="blog-description">1222 out of 1589 answered.</p>
### How long have you been developing with JavaScript?
<img src="/static/blog/2021-developer-survey-results/33.png" style="width: 796px; margin-top: 16px; margin-bottom: 8px;" alt="Just getting started: 4.8%; 1 year +: 22.2%; 3 years +: 27.9%; 5 years +: 28.2%; 10 years +: 11.1%; 15 years +: 5.9%" />
<p class="blog-description">1520 out of 1589 answered.</p>
### How long have you been developing with React?
<img src="/static/blog/2021-developer-survey-results/34.png" style="width: 796px; margin-top: 16px; margin-bottom: 8px;" alt="Just getting started: 7%; 6 months +: 11%; 1 year +: 20.6%; 2 years +: 21.2%; 3 years +: 27.1%; 5 years +: 11.5%; Bleeding edge baby! 6 years +: 1.6%" />
<p class="blog-description">1523 out of 1589 answered.</p>
### How long have you been developing with MUI?
<img src="/static/blog/2021-developer-survey-results/35.png" style="width: 796px; margin-top: 16px; margin-bottom: 8px;" alt="Just getting started: 16.6%; 6 months +: 19.4%; 1 year +: 24.4%; 2 years +: 21.2%; 3 years +: 15.6%; I'm a pioneer! 5 years +: 2.8%" />
<p class="blog-description">1519 out of 1589 answered.</p>
## Conclusion
The annual survey is one of the most important resources we have for deciding on our next steps.
We appreciate all the time you invested in answering our questions, and we can't stress enough how much we value your input.
In 2021, we released the largest update that MUI has ever seen.
We also began investing in complementary products, such as [MUI X](/x/), our [design kits](/design-kits/), and [premium templates](/templates/).
Your feedback from this survey helped us to better understand the areas where we need to improve:
- **Documentation:** You've asked for more examples, more tutorials, more learning materials, and more comprehensive docs.
Most third-party content about Material UI became outdated with the release of v5, so we have much work to do to pick up the slack.
- **Customization:** A new styling tool was an important step in the right direction for more customizability.
We recognize that there are still many more opportunities to improve the experience of customizing MUI components.
- **Design quality:** Design continues to be the main driving aspect that guides a decision towards a given component library.
A growing number of developers are moving away from MUI because of Material Design being the only design direction provided out-of-the-box, and that's a huge warning sign for us to explore other roads.
- **Breaking changes:** The need for fewer breaking changes does highlight one very positive point: numerous applications depend on MUI as their component library of choice.
To continue supporting your products, we'll look for ways to minimize the number of breaking changes in future updates.
We'll also continue exploring automation tools to ease the pain of any breaking changes that do come up.
- **Commercial vs.
MIT balance:** MUI will always be an OSS project first and foremost, but we are getting a lot of positive feedback from our paid products and support services, which tells us that we're heading in the right direction.
We are rapidly expanding our team to better address the needs of all of our users, and we look forward to making both our MIT-licensed and commercial offerings even more robust and compelling. If you want to understand more about our view of the MIT/open-source balance, check our [Stewardship page](https://mui-org.notion.site/Stewardship-542a2226043d4f4a96dfb429d16cf5bd).
- **Performance:** We're still looking for the most effective ways to optimize performance.
TypeScript has potential, and MUI System's speed needs work.
This is especially [important for mobile experiences](https://www.youtube.com/watch?v=mLjxXPHuIJo&t=76s).
We welcome your suggestions!
If you want to continue to influence our roadmap, you can visit the [MUI Core](https://github.com/mui/material-ui) and [MUI X](https://github.com/mui/mui-x) repositories, open issues, upvote the ones you're most interested in, or leave your thoughts about anything else you want to be improved. We'd love to hear from you.
Thanks again and until the next survey!
### Read more
Here is some additional content related to the topics covered throughout this post:
- [How to migrate from v4 to v5](/material-ui/migration/migration-v4/)
- [Style library interoperability](/material-ui/guides/interoperability/)
- [Approaches to customizing Material UI components](/material-ui/customization/how-to-customize/)
Lastly, check out the last two iterations on the MUI Developer Survey:
- [2020 edition](/blog/2020-developer-survey-results/)
- [2019 edition](/blog/2019-developer-survey-results/)
| 4,120 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/blog/2021-q1-update.js | import * as React from 'react';
import TopLayoutBlog from 'docs/src/modules/components/TopLayoutBlog';
import { docs } from './2021-q1-update.md?@mui/markdown';
export default function Page() {
return <TopLayoutBlog docs={docs} />;
}
| 4,121 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/blog/2021-q1-update.md | ---
title: Q1 2021 Update
description: An update on our mission for Q1 2021.
date: 2021-04-12T00:00:00.000Z
authors: ['oliviertassinari']
card: true
tags: ['Company']
---
This update covers our progress over the last three months, and what we aim to achieve in the months ahead.
## Product
Here are the most significant improvements since December 2020.
### Core components
- 👩🎤 We have worked on rolling out and scaling the new **styling engine** to all the components.
At this point, we have migrated 129 out of 167 components to emotion/styled-components.
Most of the components left to be migrated are in the lab.
We are almost done! You can subscribe to [material-ui#24405](https://github.com/mui/material-ui/issues/24405) to be notified once finished.
The community has provided invaluable assistance.
- 📚 To complement the migration of the components, we have worked on the migration of the code examples in the documentation,
favoring the `sx` prop where possible.
When a component needs to render styles based on the provided props, we have used the `styled` API.
Effectively, `makeStyle` and `withStyles` have been removed from the demos (we will deprecate these modules later on).
You can subscribe to [material-ui#16947](https://github.com/mui/material-ui/issues/16947) to be notified once finished.
- 📚 We have used the update of the documentation as an opportunity to break down the demos into smaller **single-focus** ones, with inline previews.
For instance:
<img src="/static/blog/2021-q1-update/docs-before.png" alt="" style="width: 526px; margin-top: 16px;" />
<p class="blog-description">Before</p>
was turned into multiple chunks, among them:
<img src="/static/blog/2021-q1-update/docs-after.png" alt="" style="width: 525px; margin-top: 16px;" />
<p class="blog-description">After</p>
- 🥞 We have introduced a new `<Stack>` component.
It handles one-dimensional layouts.
It allows working around the lack of browser support for the flexbox `gap` CSS property ([no support](https://caniuse.com/flexbox-gap) in Safari).
<img src="/static/blog/2021-q1-update/stack.png" alt="" style="width: 502px; margin-bottom: 16px;" />
You can find [more details](https://mui.com/material-ui/react-stack/) in the documentation.
- 🎨 We have improved the support for custom colors and variants.
This is [one](https://github.com/mui/material-ui/issues/13875) of the most upvoted issues in the GitHub issue tracker.
The migration to the new style engine allows us to fully rely on dynamic styles.
Developers can now do the following:
```jsx
import { createMuiTheme, Button } from '@mui/material';
// 1. Extend the theme.
const theme = createMuiTheme({
palette: {
neutral: {
main: '#5c6ac4',
},
},
});
// 2. Notify TypeScript about the new color in the palette
declare module '@mui/material/styles' {
interface Palette {
neutral: Palette['primary'];
}
interface PaletteOptions {
neutral: PaletteOptions['primary'];
}
}
// 3. Profit
<Button color="neutral" />
```
This new feature removes the need to create a wrapper component.
- 📍 We have synchronized the icons with the latest update of the Material Design icons.<br />
Google has moved its icons to a new location: https://fonts.google.com/icons.
At the same time, they have increased the number of provided icons from 6,500 to 8,500.
You can find all these icons under the `@mui/icons-material` package.
- 🦴 We have migrated a couple of components to the `@mui/base` package.
The aim of the package is to host the unstyled and headless (hooks) components.
So far, you can only find:
- Backdrop
- Badge
- Focus trap
- Modal
- Slider
We are synchronizing the development of the Base package with the creation of the second theme (and not v5).
- 🛠 We added a subset of the system as flattened props to the CSS utility components (Box, Typography, Stack, and Grid).
We initially didn't plan to do so but reversed on hearing the feedback from the community.
In addition to using the `sx` prop, you can now do, for example:
```jsx
<Box display="grid" />
<Typography p={2} color="text.secondary" />
<Stack mt={1} />
<Grid color="success.main" />
```
Note that with the other components, only the `sx` prop is available.
- ⚓️ We have introduced a new release line: `v4.x.x-deprecations.x`.
This release line is kept in sync with the latest version of v4 and includes actionable deprecations to ease the migration to v5.
### Advanced components
We have primarily focused on the data grid components, fixing a lot of bugs, but also delivering new features.
#### Date Picker
The date picker is at the border between the advanced components and the design system realms.
- 📚 We have fixed the generation of the API pages.
We now document all the props supported by the public pickers components, e.g. [DatePicker](https://mui.com/api/date-picker/).
- ⚙️ We have mostly focused on addressing the technical debt present in the picker components (ported from `@materal-ui/pickers`).
#### Data Grid
- 🔄 We have started to bring support for [lazy-loading](/x/react-data-grid/row-updates/#infinite-loading).
- ⬇️ We have introduced support for [CSV export](/x/react-data-grid/export/#csv-export).
<img src="/static/blog/2021-q1-update/csv-export.png" alt="" style="width: 523px; margin-bottom: 16px;" />
- ♿️ We have fixed a couple of accessibility issues (more in progress).
- 🌏 We have introduced support for [custom locales](/x/react-data-grid/localization/).
- 🚨 We have started to work on breaking changes to reach a stable state.
- 💾 We have extended the support of @mui/material to handle v4 and v5 at the same time.
In the future, we might desynchronize the release version of _mui/material-ui_ and _mui/mui-x_.
For MUI X, we will likely need to release breaking changes at a higher frequency: every six months.
- 🎛 We have added a column selector.
<img src="/static/blog/2021-q1-update/column-selector.png" alt="" style="width: 518px; margin-bottom: 16px;" />
### Design kits
#### Figma
We have migrated all the components to leverage the [Figma variants feature](https://help.figma.com/hc/en-us/articles/360056440594-Create-and-use-variants).
We have also taken this as an opportunity to polish the components:
- Improve the use of auto-layout
- Fix theme design token usage
- Add the Autocomplete component
#### Adobe XD
We have made Adobe XD available with a first release.
#### Sketch
We have redesigned most of the components from scratch to make sure all components show their CSS properties using inspection tools such as [Sketch Cloud Inspect tool](https://www.sketch.com/blog/2020/01/29/introducing-cloud-inspector-free-developer-handoff-in-the-browser/).
## Company
### Handbook
The most important change inside the organization is the introduction of a company Handbook.
The company is distributed and operates across different time zones.
Per the nature of our operation, and at the pace we are growing, we needed an effective and efficient way to share the organizational processes and culture.
Per our transparency value, all the sections of the Handbook that don't contain sensitive information are [publicly available](https://mui-org.notion.site/Handbook-f086d47e10794d5e839aef9dc67f324b).
This Handbook is the single **source of truth**. It's meant to be updated by any team member, to stay in sync with how we do things.
### Growth between Q4 2020 and Q1 2021
- 📦 From 6.4M to 8.6M downloads per month on npm.<br />
It seems that React keeps taking market share in the frontend ecosystem;
it's growing faster than Vue or Angular.
Most indicators point to it: [Stack Overflow questions](https://insights.stackoverflow.com/trends?tags=vue.js%2Creactjs%2Cangular), [stars](https://bestofjs.org/projects?sort=monthly), [downloads](https://npm-stat.com/charts.html?package=react-dom,@angular/core,vue), [Traffic on the documentation](https://www.similarweb.com/website/reactjs.org/?competitors=vuejs.org).
Our strategy to focus on React only seems to be paying off.
- ⭐️ From 63.8k to 67.2k stars, leave us yours [🌟](https://github.com/mui/material-ui).
We have seen a significant influx of stars this quarter.
- 👨👩👧👦 From 2,052 to 2,141 contributors on GitHub. We add on average one new contributor every day.
- 💰 Grew gross revenue at +4%/week on average during the period.
- 🏢 We have welcomed one new member to MUI: [Matheus](/blog/matheus-wichman-joining/).
## Our roadmap intent for Q2 2021
We'll do our best, no guarantee!
### Company
We have almost signed with **four** new people to join the team this quarter (waiting for their notice period).
We will welcome our first designer and a frontend developer to collaborate with him on a second theme.
The two others will strengthen 1. the core components and 2. the advanced components teams.
We will cross the ten-person milestone in the coming weeks (11).
We have the following objectives:
- Finish the implementation of the rebranding. A preview, the [about](/about/) and [pricing](/pricing/) pages.
- Onboard the new members and scale our processes as we double the size of the organization this quarter.
### Core components
- 🚀 Get v5-beta (no more breaking changes) out! The development of this new version started almost a year ago. It's time to aim for the stable release.
- 📅 Start handling the issues with the date picker reported by developers.
- 🗓 Execute on all the items of the [public roadmap](https://github.com/orgs/mui/projects/18/views/1).
- ❓ Please upvote [GitHub issues](https://github.com/mui/material-ui/issues?q=is%3Aissue+is%3Aopen+sort%3Areactions-%2B1-desc) if you want us to focus on a specific problem. The number of 👍 helps us to prioritize.
### Advanced components
- ✍️ Release the Data Grid cell edit feature we have been working on for the last two months. [A preview](https://deploy-preview-1287--material-ui-x.netlify.app/components/data-grid/editing/).
- 📅 Start dedicating time to the date range picker.
- 🗓 Execute on all the items in the [public roadmap](https://github.com/mui/mui-x/projects/1).
- ❓ Please upvote [GitHub issues](https://github.com/mui/mui-x/issues?q=is%3Aissue+is%3Aopen+sort%3Areactions-%2B1-desc) if you want us to focus on a specific problem. The number of 👍 helps us to prioritize.
### Design kits
- Release an update with the new Material Design icons on Figma, Adobe XD, Sketch.
- Figma, continue to polish the kit as our most important one.
- Adobe XD, improve the performance of the kit.
- Collect more users' feedback to identify the biggest improvement opportunities.
| 4,122 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/blog/2021-q2-update.js | import * as React from 'react';
import TopLayoutBlog from 'docs/src/modules/components/TopLayoutBlog';
import { docs } from './2021-q2-update.md?@mui/markdown';
export default function Page() {
return <TopLayoutBlog docs={docs} />;
}
| 4,123 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/blog/2021-q2-update.md | ---
title: Q2 2021 Update
description: An update on our mission for Q2 2021.
date: 2021-07-12T00:00:00.000Z
authors: ['oliviertassinari', 'mbrookes']
card: true
tags: ['Company']
---
This update covers our progress over the last three months.
It also covers what we aim to achieve in the months ahead.
## Overview
- [Product](#product)
- [Core components](#core-components)
- [Advanced components](#advanced-components)
- [Design kits](#design-kits)
- [Company](#company)
- [Our roadmap intent for Q3 2021](#our-roadmap-intent-for-q3-2021)
## Product
Here are the most significant improvements since March 2021.
### Core components
- 🔥 We've made enough progress to ship [v5.0.0-beta.0](https://github.com/mui/material-ui/releases/tag/v5.0.0-beta.0). Here are a few statistics to give an idea of the effort that went into it:
- [12 months](/blog/2020-q2-update/#product) of dedicated focus.
We stopped work on v4 early on to fully dedicate to v5.
- 3,475 pull requests.
- 5,092 commits (the extra commits came from the merge of [material-ui-pickers](https://github.com/mui/material-ui-pickers))
- 398 new contributors.
- The equivalent of four full-time developers working on it on average (core team + community).
- 38 alpha releases, we release once a week.
- 👩🎤 We have rolled out the new **style engine** to all the components.
The community provided invaluable assistance in completing this effort.
In v5, we have standardized on the `styled()` API as the styling foundation we build on top of, and introduced the [the `sx` prop](https://mui.com/system/getting-started/the-sx-prop/) for one-off customizations.
The `styled()` API is loved by the community, and implemented by a number of styling libraries: styled-components, emotion, stitches, goober, etc. It allows us to support them all with [adapters](https://mui.com/material-ui/guides/styled-components/).
- ⚒️ We added a [codemod CLI](https://github.com/mui/material-ui/tree/HEAD/packages/mui-codemod) and 17 transformations (so far) to automatically migrate codebases from v4 to v5.
If you're not familiar with what a codemod is, check out [Effective Refactoring with Codemods by Edd Yerburgh](https://www.youtube.com/watch?v=H9qtLutnT_g).
- 💄 We have [updated the style of the Slider](https://mui.com/material-ui/react-slider/#sizes) to better match the Material Design guidelines, and kept a similar style as before under `size="small"`:
<a href="https://mui.com/material-ui/react-slider/#sizes"><img loading="lazy" src="/static/blog/2021-q2-update/slider.png" alt="" style="width: 838px; margin-bottom: 16px;" /></a>
- ✨ The new style engine has unlocked problems on the `Grid` component that we couldn't solve before with JSS:
We have added support for [row & column](https://mui.com/material-ui/react-grid/#row-amp-column-spacing) spacing:
```jsx
<Grid container rowSpacing={1} columnSpacing={2} />
```
We have added support for [responsive values](https://mui.com/material-ui/react-grid/#responsive-values) on all the props:
```jsx
<Grid container spacing={{ xs: 2, md: 3 }} />
```
We have added support for a different [number of columns](https://mui.com/material-ui/react-grid/#columns) than 12:
```jsx
<Grid container columns={16}>
```
We have added an alternative implementation that uses [CSS grid](https://mui.com/material-ui/react-grid/#css-grid-layout):
```jsx
<Box display="grid" gridTemplateColumns="repeat(12, 1fr)" gap={2}>
<Box gridColumn="span 8">
<Item>xs=8</Item>
</Box>
<Box gridColumn="span 4">
<Item>xs=4</Item>
</Box>
<Box gridColumn="span 4">
<Item>xs=4</Item>
</Box>
<Box gridColumn="span 8">
<Item>xs=8</Item>
</Box>
</Box>
```
- 💄 We have improved the accessibility of the Link component:
<a href="https://mui.com/material-ui/react-link/">
<img loading="lazy" src="/static/blog/2021-q2-update/link.png" alt="" style="width: 129px; margin-bottom: 16px;" />
</a>
<p class="blog-description">The underline helps to differentiate links in sentences.</p>
### Advanced components
We have primarily focused on the data grid components, fixing a lot of bugs.
#### Date Picker
The date picker is at the border between the core component and advanced components realms.
- 🐛 We have fixed a couple of straightforward problems: visual bugs, use of the `components` prop for customizability, etc.
- ⚙️ We have continued to focus on addressing technical debt present in the picker components.
#### Data Grid
- 🚨 We have continued to work on breaking changes to reach a stable version.
We think that the component is good enough for use in production (and many developers already are using it), but we want to get the public API right before committing to a stable release.
- ✍️ We have added support for the [cell edit mode](https://mui.com/x/react-data-grid/editing/).
<img loading="lazy" src="/static/blog/2021-q2-update/cell-edit.gif" alt="" style="width: 842px; margin-bottom: 16px;" />
- 🐛 We have focused on fixing bugs and regressions to ensure early users have a great experience with the component.
This was done instead of taking on ambitious new features.
We want our users to be able to adopt new features as fast as we build them.
- 🔘 We have added support for a built-in [single select](/x/react-data-grid/column-definition/#column-types) column type:
<img loading="lazy" src="/static/blog/2021-q2-update/single-select.png" alt="" style="width: 481px; margin-bottom: 16px;" />
<p class="blog-description">the <a href="https://codesandbox.io/s/material-demo-forked-iuyo5?file=/demo.js">codesandbox</a></p>
and the **boolean** column type.
- 🚀 We have improved the performance.
Client-side sorting and filtering are 2-3x faster on large data sets.
We have improved the UX when scrolling.
We have added memo logic on the render cell's parent, and worked on its effectiveness to reduce the re-rendering of custom cells.
We have identified more opportunities to improve the performance that we will prioritize later.
- 📚 We have worked on providing more reference documentation. We are semi-automatically generating it from the TypeScript source definitions, with the descriptions.
For instance, you can now find all the [properties available](/x/api/data-grid/grid-col-def/) of the `GridColDef`.
- ⚡️ We have fixed support for components that use portals, like Select and Autocomplete, in the cell editing mode.
- 🌏 We have accepted many new built-in locales (+15) from the community, after the introduction of [the feature](/x/react-data-grid/localization/#supported-locales) in Q1.
### Design kits
#### Figma
Designers have a great sense of detail.
We have polished the kit, using all the feedback that we could get.
We have also introduced support for a [dark mode](https://www.figma.com/file/7M8OmZIv6WigOjbSV7Xxlg/2021-q2-update?node-id=4230%3A724)! We have worked on making the design kit close to the React components.
This reduces miscommunications between designers and developers.
#### Adobe XD
We have fixed performance issues and polished the kit.
#### Sketch
We have added support of a dark mode and polished the kit.
## Company
### OKRs
In the first quarter, we focused on introducing a [handbook](https://mui.com/blog/2021-q1-update/#handbook) to share our culture and to help solve the N(N-1)/2 communication channels problem that comes with a larger team.
This quarter, we took on a new initiative to help us solve three problems:
- create alignment on the goals
- improve how we measure success
- create space to take on larger initiatives, away from the day-to-day PR and issue management
After considering [different](https://basecamp.com/shapeup) [alternatives](https://coda.io/@shishir/rituals-for-hypergrowth-an-inside-look-at-how-youtube-scaled), we are going with the [OKR methodology](https://www.whatmatters.com/resources/google-okr-playbook/).
### Growth between Q1 2021 and Q2 2021
- 📦 From 8.6M to 9.1M downloads per month on npm. We have 21.03% of market share inside the React ecosystem, up from 6.68%, 5 years ago.
- ⭐️ From 67.2k to 69.1k stars. [Leave us yours 🌟](https://github.com/mui/material-ui)!
- 👨👩👧👦 From 2,141 to 2,223 contributors on GitHub. We add on average one new contributor every day.
### New members
We have welcomed four new members to the company 🏢:
- [Jun](/blog/siriwat-kunaporn-joining/), leads the implementation of a [second design system](https://github.com/mui/material-ui/issues/22485).
<img loading="lazy" src="/static/blog/2021-q2-update/jun.jpg" alt="jun" style="width: 160px; height: 160px; margin: unset; margin-bottom: 24px; border-radius: 2px;" />
- [Michał](/blog/michal-dudak-joining/) leads the initiative around the [unstyled components](https://github.com/mui/material-ui/issues/6218).
<img loading="lazy" src="/static/blog/2021-q2-update/michal.jpg" alt="michal" style="width: 160px; height: 160px; margin: unset; margin-bottom: 24px; border-radius: 2px;" />
- [Danilo](https://daniloleal.co/), a Lead Designer to raise our design game.
<img loading="lazy" src="/static/blog/2021-q2-update/danilo.jpg" alt="danilo" style="width: 160px; height: 160px; margin: unset; margin-bottom: 24px; border-radius: 2px;" />
- [Flavien](https://github.com/flaviendelangle), an engineer with previous experience building [design systems](https://habx.github.io/ui-core/) and a complex 2D JavaScript rendering engine. He's helping us take on bolder problems on the advanced components (X team), starting with the data grid.
<img loading="lazy" src="/static/blog/2021-q2-update/flavien.jpg" alt="flavien" style="width: 160px; height: 160px; margin: unset; margin-bottom: 24px; border-radius: 2px;" />
We are also **hiring** for various roles! If you're interested in joining us, check out our [jobs page](/careers/#open-roles).
## Our roadmap intent for Q3 2021
We'll do our best, no guarantee!
### Company
We have the following objectives:
- Continue to refine our processes and responsibilities to make sure we function well with over ten people in the company.
- Rebrand. We started this effort one year ago but, failed to execute on it.
With [Danilo](https://github.com/danilo-leal) (design) and [Jun](https://github.com/siriwatknp) (code) in the team to own the effort, we can finally make it happen.
We will take a step to distinguish ourselves from a strong association with Material Design.
- Open and fill [4 roles](/careers/#open-roles). We need to strengthen the X team (advanced components)
We also want to initiate the development of a bold new product vertical.
### Core components
- 🚀 Get v5 stable out! At this point, v5-alpha has about [1%](https://npm-stat.com/charts.html?package=%40material-ui%2Fstyled-engine&package=%40material-ui%2Fcore&from=2020-06-22&to=2021-06-22) of the downloads of v4.
It has a lot of accumulated value not being realized. We're aiming for 25% of the community to have migrated by the end of the quarter.
- ♨️ Fix the friction the community has during the upgrade to v5.
We want to make the upgrade feel painless.
- ⚛️ Support [React 18](https://legacy.reactjs.org/blog/2021/06/08/the-plan-for-react-18.html). [Sebastian](https://github.com/eps1lon) is part of the React [Working Group](https://github.com/reactwg/react-18/discussions), focusing on making us ready ahead of time.
We want our most demanding users to feel empowered by MUI, not slowed down by a third-party.
- 🦴 Migrate more components to `@mui/base`. [Michał](https://github.com/michaldudak) has recently added support for the [Switch](https://mui.com/base-ui/react-switch/).
You can follow our progress in the [umbrella issue](https://github.com/mui/material-ui/issues/27170).
- 🌈 Do a proof of concept on supporting a second design system.
Some of our users (and potential users) dislike Material Design. We will try to make the second design system one that they love!
- 🗓 Execute on all of the items in the [public roadmap](https://github.com/orgs/mui/projects/18/views/1).
- ❓ Please upvote [GitHub issues](https://github.com/mui/material-ui/issues?q=is%3Aissue+is%3Aopen+sort%3Areactions-%2B1-desc) if you want us to focus on a specific problem. The number of 👍 helps us to prioritize.
### Advanced components
- 🚀 Release the first stable version of the Data Grid.
- ✨ Resume work on the [key features](https://github.com/mui/mui-x/issues?q=is%3Aopen+label%3A%22linked+in+docs%22+sort%3Areactions-%2B1-desc), after a quarter focused on stability.
It seems that the audience is adopting the data grid as fast as we can build it.
For instance, we have one issue with over [1,000 upvotes](https://github.com/mui/mui-x/issues/204) 👍.
- 🗓 Execute on all of the items in the [public roadmap](https://github.com/mui/mui-x/projects/1).
- ❓ Please upvote [GitHub issues](https://github.com/mui/mui-x/issues?q=is%3Aissue+is%3Aopen+sort%3Areactions-%2B1-desc) if you want us to focus on a specific problem. The number of 👍 helps us to prioritize.
### Design kits
- Handle designers' pain and bug reports to polish the products.
- Run a survey on thousands of customers to identify important improvement opportunities. Should we build plugins to more easily switch the token variables between design and code? Should we add more in context examples? Should we focus on inconsistencies? etc.
| 4,124 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/blog/2021-q3-update.js | import * as React from 'react';
import TopLayoutBlog from 'docs/src/modules/components/TopLayoutBlog';
import { docs } from './2021-q3-update.md?@mui/markdown';
export default function Page() {
return <TopLayoutBlog docs={docs} />;
}
| 4,125 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/blog/2021-q3-update.md | ---
title: Q3 2021 Update
description: An update on our mission for Q3 2021.
date: 2021-10-26T00:00:00.000Z
authors: ['oliviertassinari']
card: true
tags: ['Company']
---
This update covers our progress over the last three months.
It also covers what we aim to achieve in the months ahead.
## Overview
- [Product](#product)
- [MUI Core](#mui-core)
- [MUI X](#mui-x)
- [Design kits](#design-kits)
- [Company](#company)
- [Our roadmap intent for Q4 2021](#our-roadmap-intent-for-q4-2021)
## Product
Here are the most significant improvements since early July 2021.
### MUI Core
- 🔥 In September we released a new major version: [v5.0.0](https://github.com/mui/material-ui/releases/tag/v5.0.0) (you might have noticed! 😄 ).
We're excited about what it means for the future of the library, and we hope you are going to enjoy the simplified customization, the extra flexibility, new components, and more.
It took us over a year to pull off, with an almost exclusive focus on v5 over v4.
You can read more about it in the [release blog post](/blog/mui-core-v5/).
- ✨ We also introduced a brand new [product page](/core/) this quarter to better present what the Core is about.
- 🔎 We've reworked the search experience in the docs:
- The component pages now rank before the API pages.
- Instead of only displaying up to 5 results, you can scroll for more results.
- An icon illustrates the nature of the match; either a page, a header, or a paragraph.
- Your most recent searches are saved in local storage.
<img loading="lazy" src="/static/blog/2021-q3-update/old-search.png" alt="" style="width: 596px;" />
<p class="blog-description">Before</p>
<img loading="lazy" src="/static/blog/2021-q3-update/new-search.png" alt="" style="width: 600px; margin-top: 32px;" />
<p class="blog-description">After</p>
- [Masonry](/material-ui/react-masonry/). We introduced a new component for use when the `Grid` component leads to wasted space. It's frequently used in dashboards.
<a href="/material-ui/react-masonry/"><img loading="lazy" src="/static/blog/2021-q3-update/masonry.png" style="width: 700px; margin-bottom: 16px;" /></a>
- We introduced a new [package of components without styles](https://www.npmjs.com/package/@mui/base), laying the foundations for supporting multiple design systems with headless components.
While it was tough to balance the time between working on v5 stable and developing the unstyled components, we still managed to introduce the first few:
- [Autocomplete](/material-ui/react-autocomplete/#useautocomplete)
```jsx
import { useAutocomplete } from '@mui/base/AutocompleteUnstyled';
```
- [Button](/material-ui/react-button/#unstyled)
```jsx
import { useButton } from '@mui/base/ButtonUnstyled';
```
- [Modal](/material-ui/react-modal/#unstyled)
```jsx
import { ModalUnstyled } from '@mui/base/ModalUnstyled';
```
- [Slider](/material-ui/react-slider/#unstyled)
```jsx
import { SliderUnstyled } from '@mui/base/SliderUnstyled';
```
- [Switch](/material-ui/react-switch/#unstyled)
```jsx
import { useSwitch } from '@mui/base/SwitchUnstyled';
```
- [Portal](/material-ui/react-portal/#unstyled)
```jsx
import { Portal } from '@mui/base/Portal';
```
- [FocusTrap](/base-ui/react-focus-trap/)
```jsx
import { FocusTrap } from '@mui/base/FocusTrap';
```
### MUI X
Last quarter we focused on the data grid components, working towards a stable release.
We also introduced a brand new [product page](/x/) this quarter to better present what MUI X is about.
#### Date Picker
The date picker sits at the border between the core component and advanced components.
- ❌ A few updates but no major ones worth sharing.
With the release of v5 stable and our focus on the data grid, nobody in the team had the bandwidth to work on it.
#### Data Grid
- 🎉 We released the first stable version: [v4.0.0](https://github.com/mui/mui-x/releases/tag/v4.0.0)!
We also released the first v5-beta, to support MUI Core v5,
and will be working almost exclusively on the v5 release line going forward.
- 🔎 We also added a [quick-filter demo](/x/react-data-grid/filtering/quick-filter/) to illustrate how it can be implemented,
and will add a [built-in](https://github.com/mui/mui-x/issues/202) solution later on.
<a href="/x/react-data-grid/filtering/quick-filter/"><img loading="lazy" src="/static/blog/2021-q3-update/quick-filter.png" style="width: 700px; margin-bottom: 16px;" /></a>
- 🐛 We fixed several non-idiomatic React patterns, for instance we were not handling controllable props by the book, and as we do in MUI Core.
- 🚀 We introduced the [row editing](/x/react-data-grid/editing/#row-editing) feature.
<img src="/static/blog/2021-q3-update/row-edit.gif" width="851" />
- 🦺 We added a [`disableVirtualization`](/x/react-data-grid/virtualization/#disable-virtualization) prop to make it easier to test the data grid without a real browser environment, for example in jsdom with Jest.
- 🚛 We have added an `onViewportRowsChange` prop as a first step toward being able to lazy load a large dataset.
- Last but not least, we have resumed the work on [key missing features](https://github.com/mui/mui-x/issues?q=is%3Aopen+label%3A%22linked+in+docs%22+sort%3Areactions-%2B1-desc).
Print export and tree data are in the pipeline.
### Design kits
We introduced a brand new [product page](/design-kits/) this quarter to better present the design kits.
#### Figma
The kit is now up-to-date with MUI Core v5,
and also includes the MUI X components. And, as always, we have been refining it in small areas for issues raised by our users in the support channel.
#### Adobe XD
No updates.
#### Sketch
No updates.
## Company
### Retreat
We held our first company retreat 🏝 in Lisbon, Portugal 🇵🇹 ,
for members of the team that were not prevented by COVID-19 related travel restrictions, and who felt safe enough to travel.
Less than half the company made it, but it was still fun!
We spent half the time doing a [Hackathon](https://twitter.com/olivtassinari/status/1441773885259583491) and the other half on activities (surfing, biking, winery tour, and sightseeing).
<img loading="lazy" src="/static/blog/2021-q3-update/retreat.jpeg" alt="" style="width: 596px; margin-bottom: 8px" />
<p class="blog-description">Sightseeing in Lisbon</p>
### Growth between Q2 2021 and Q3 2021
- 📦 From 9.1M to 9.9M downloads per month on npm. We have 22.4% market share of the React ecosystem as a proportion of `react-dom` downloads.
- ⭐️ From 69.1k to 72.1k stars. [Leave us yours 🌟](https://github.com/mui/material-ui)!
- 👨👩👧👦 From 2,223 to 2,316 contributors on GitHub. On average, one new contributor joins every day.
- 💰 Grew financial support by 2.99X [year over year](/blog/2020-q3-update/).
### New member
We welcomed one new member to the company this quarter 🏢:
- Benny was our first intern, and is now the first junior developer on the MUI Core team.
<img loading="lazy" src="/static/blog/2021-q3-update/benny.jpg" alt="Benny" style="width: 160px; height: 160px; margin: unset; margin-bottom: 24px; border-radius: 2px;" />
We are now 11 passionate builders empowering the next generation of UI creators.
### A new brand
Alongside the release of v5, we launched our [new brand](/blog/material-ui-is-now-mui/)!
We're excited about our new shorter name, **MUI**.
We were already using it in the class names (`.MuiButton-root`), which embodies our next step beyond Material Design.
This is something we have been considering for some time,
and we did a couple of early design studies with an outside agency,
but it was only after we secured [mui.com](https://mui.com/), the GitHub [`@mui`](https://www.npmjs.com/org/mui) org, and the npm [@mui](https://www.npmjs.com/org/mui) scope that we knew the new name would work.
## Our roadmap intent for Q4 2021
We'll do our best, no guarantee!
### MUI Core
- 🚀 We will double down on v5 before starting to solve new large problems, e.g. a revamp of the select.
We have made bold changes in this version since v4, but until recently, only a small percentage of the community was using v5.
In the last few weeks, we have seen a strong influx of feedback from the community.
We need to make the most of this feedback to solve regressions, improve the documentation for the new APIs, adjust the tradeoffs we took in the light of more information, and more.
[15%](https://npm-stat.com/charts.html?package=%40material-ui%2Fcore&package=%40mui%2Fmaterial&from=2020-10-25&to=2021-10-15) of the community has migrated, so far.
- 🦴 Migrate more components to `@mui/base`. [Michał](https://github.com/michaldudak) has recently added support for the [Button](https://mui.com/base-ui/react-button/).
You can follow our progress in the [umbrella issue](https://github.com/mui/material-ui/issues/27170).
- 🎨 We are [exploring](https://github.com/mui/material-ui/discussions/29024) the introduction of CSS variables.
Since v5, MUI is no longer actively supporting IE 11. Dropping this browser requirement unlocks new capabilities of the web platform.
- 🌈 Resume work on the second design system.
Some users (and potential users) dislike Material Design. We'll try to make the second design system one that they love! You can check our [first RFC](https://github.com/mui/material-ui/discussions/29024).
- 🗓 Execute on all of the items in the [public roadmap](https://github.com/orgs/mui/projects/18/views/1).
- ❓ Please upvote [GitHub issues](https://github.com/mui/material-ui/issues?q=is%3Aissue+is%3Aopen+sort%3Areactions-%2B1-desc) if you want us to focus on a specific problem. The number of 👍 helps us to prioritize.
### MUI X
#### Data Grid
We have planned to:
- ✨ Release the print export feature.
- ✨ Release the tree data feature.
- ✨ Revamp the virtualization to yield better rendering performance and fix bugs.
It unlocks new features like column pinning and lazy loading.
- 🗓 Execute on all of the items in the [public roadmap](https://github.com/mui/mui-x/projects/1).
- ❓ Please upvote [GitHub issues](https://github.com/mui/mui-x/issues?q=is%3Aissue+is%3Aopen+sort%3Areactions-%2B1-desc) if you want us to focus on a specific problem. The number of 👍 helps us to prioritize.
#### Date Picker
No plans. We probably won't progress its development this quarter.
However, we are growing the team.
We plan to resume work on it in Q1 2022, starting with the equivalent of one full-time developer.
### Design kits
We will release a v5 for Sketch and Adobe XD, as we have already done for Figma.
While the visual difference between MUI Core v4 and v5 is not major, we still need to sync the design components.
### Company
We have the following objectives:
- 📊 Run a new edition of the Developer Survey. The last one was done [15 months ago](https://mui.com/blog/2020-developer-survey-results/). Now that v5 is released, it's time for the 2021 edition!
- 👪 Hire for two new roles: a Product Manager to focus on low-code and our first Developer Advocate.
- 💫 Create a great onboarding experience for the 6-7 new hires of Q4.
| 4,126 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/blog/2021.js | import * as React from 'react';
import TopLayoutBlog from 'docs/src/modules/components/TopLayoutBlog';
import { docs } from './2021.md?@mui/markdown';
export default function Page() {
return <TopLayoutBlog docs={docs} />;
}
| 4,127 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/blog/2021.md | ---
title: 2021 in review and beyond
description: 2021 has been another great year, not only for MUI but also for the ecosystem.
date: 2021-12-31T00:00:00.000Z
authors: ['oliviertassinari']
card: true
tags: ['Company']
---
<img src="/static/blog/2021/card.png" alt="" style="width: 100%; margin-bottom: 16px;" />
Happy New Year from MUI!
2021 has been another amazing year, not only for MUI but also for the React ecosystem and our users.
The digitalization of the economy is accelerating, pushed by COVID-19.
Developers and designers have been, more than ever, busy creating apps.
We spent our year making it faster and easier for you to build great UIs and to delight your users with amazing UI experiences.
Thank you for being part of this journey!
## Growth
It's only with your trust that we could achieve the following outcomes in 2021. Thank you!
- 📦 From 6.4M to [10.8M](https://npm-stat.com/charts.html?package=%40material-ui%2Fcore&from=2019-11-30&to=2020-12-31) downloads per month (from 18% to [23%](https://docs.google.com/spreadsheets/d/1l5j3Xjtvm9XZtmb4ulLiWElQaXSlZlyCWT5ONrQMpBo/edit?usp=sharing) share of the React ecosystem).
- 📈 From 4.6M to 6.0M unique visitors per year on the documentation.
- ⭐️ From 63.8 to 74.0k stars, leave us [yours 🌟](https://github.com/mui/material-ui).
- 👨👩👧👦 From 2,052 to [2,396](https://github.com/mui/material-ui/graphs/contributors) contributors.
- 💰 Grew financial support by 2.9X in 2021, compared to 2020.
- 🏢 From 6 to 14 full-time equivalent [team members](/about/).
The numbers speak for themselves. We have reproduced the [traction we got in 2020](/blog/2020/#growth).
## In review
When we started 2021, we had recently released the first version of the MUI X data grid and were in the middle of the release of MUI v5.
We had committed ourselves to fully execute these two major efforts:
- On MUI Core, major releases have historically been efforts that span over a dozen months.
v5 was no different as great work takes time.
At the beginning of 2021, we had solved the most important aspect of v5, we had a new style engine to unlock a better styling and customization experience for developers.
But we still had most of the work ahead of us, we had to roll out the improvements to all our users.
With a large code and user base like MUI has, we knew it would take time.
For example, we might have had migrated a few components to the new style engine and fix all the issues that we could find, going to production is unforgiving.
Developers tend to surface all the cases that are overlooked in the first iteration with GitHub issues.
- On MUI X, we had successfully sold our first Pro plan licenses and reached 100k downloads/month on the MIT version.
We had early signs from the community of a market fit for the product and that the [open core license model](https://en.m.wikipedia.org/wiki/Open-core_model) was the right one to execute our mission.
We were determined to solely focus on the data grid component, and demonstrate that our model was viable to build the best React data grid in the space.
What might have been the biggest change in 2021 is the implications of a larger team for the organization structure.
We have reached an inflection point at around 10 people.
I could no longer look at all the GitHub issues and PRs.
At that point, it was requiring >70h/week to do it correctly.
It was not scaling to have one individual aware of all PRs and GitHub issues.
Continuing in this direction would prevent us to grow the team, and more importantly, it was distracting me from the core CEO responsibilities (people, vision, funding).
So we have broken down the responsibilities
We have introduced our first layers of management and defined more clearly the purpose of each role.
## Achievements
We have achieved most of what we could have hoped for.
### Company
- The most important, we have welcomed 10 [members](/about/) in the company: Matheus, Michał, Jun, Danilo, Flavien, Benny, Alexandre, Jan, Bharat, Prakhar.
- We have introduced a [public handbook](https://mui-org.notion.site/Handbook-f086d47e10794d5e839aef9dc67f324b) on how we run the company.
For example, we are using the OKRs work methodology to prioritize our efforts.
- We held our first company [retreat](/blog/2021-q3-update/#retreat) 🏝 in Lisbon, Portugal 🇵🇹 , for members of the team that were not prevented by COVID-19 related travel restrictions, and who felt safe enough to travel.
- We have [rebranded](/blog/material-ui-is-now-mui/) the company to a clean 3 letters acronym: mui.com. This move was key for us to grow beyond Material Design.
### MUI Core
- We have released [v5](/blog/mui-core-v5/), 21% of the npm downloads are on this major version now.
- We have broken down the demos into smaller and focus on one aspect at a time.
- We have polished and promoted most of the components that were in the lab to `@mui/material`.
- We have introduced many new components:
- [Masonry](/material-ui/react-masonry/)
- [Stack](/material-ui/react-stack/)
- [Trap Focus](/base-ui/react-focus-trap/)
- [Unstyled Button](/base-ui/react-button/)
- [Unstyled Slider](/base-ui/react-slider/)
- [Unstyled Modal](/base-ui/react-modal/)
- [Unstyled Slider](/base-ui/react-switch/)
- [Unstyled Tabs](/base-ui/react-tabs/)
### MUI X
- We have released [v5](/blog/mui-x-v5/), 42% of the npm downloads are on this major version now.
- We have introduced support for [custom locales](/x/react-data-grid/localization/).
- We have introduced many new features while consolidating the existing ones:
- [Row editing](/x/react-data-grid/editing/#row-editing)
- [Cell editing](/x/react-data-grid/editing/)
- [Column pinning](/x/react-data-grid/column-pinning/)
- [Tree data](/x/react-data-grid/tree-data/)
- [CSV export](/x/react-data-grid/export/#csv-export)
- [Print](/x/react-data-grid/export/#print)
- We have grown the MIT downloads on npm and the number of licenses sold per month by a factor of x10 in 2021 compared to 2020.
- We have grown the size of the team from 2 to 4 people (6 in January).
## Looking at 2022
I have been involved on MUI for 7 years and almost 3 years full-time now.
It's amazing to see the progress the library has done [since then](https://v0.mui.com/#/components/app-bar).
But at the same time, I'm astonished by how far we can still push the mission forward.
My experience has been that the more we improve the library, the more we envision future ways to do it better.
It's still **[day 1](https://www.sec.gov/Archives/edgar/data/1018724/000119312517120198/d373368dex991.htm)**.
What's our mission? To empower as many people as possible to build great UIs, faster.
2021 was great, 2022 is going to be even more exciting!
We will continue in the same direction.
Here is a breakdown of our [roadmap](/material-ui/discover-more/roadmap/).
### MUI Core
The release of v5 has introduced a significant API churn in the community.
While our [versioning frequency](/versions/#release-frequency) aims for one major per year, we hope we can iterate on v5 during the whole year of 2022 without any breaking changes, e.g. taking full advantage of the new style engine.
#### Base UI
To continue improving the customization experience, we will double down on the version of the components without styles: `@mui/base`.
These components and hooks contain the main functionalities and accessibility, without being opinionated about how styles are applied or what styles.
We still have work to do to have a full set of unstyled components.
You can read more about them in [the docs](/base-ui/getting-started/) and keep track of our progress in [#27170](https://github.com/mui/material-ui/issues/27170).
Our high-level plan is to use the unstyled components and hooks as the basis of the Material Design components and our second design system.
#### System
There a number of improvements that we can bring to the system (the npm package `@mui/system` used to create the styled components).
Hopefully, we will bring native support for CSS variables, improve DX, and improve performance.
#### Material UI
Google is rolling out [Material Design 3](https://m3.material.io/), we have to determine how to respond to it.
Should we implement it later on for v6? Should we ignore it? Should we implement Google's UI that looks cleaner instead?
In the meantime, we will keep improving the components, increasingly relying on `@mui/base`.
#### Joy UI
We will continue [in the direction of 2021](/blog/2020/#a-second-theme).
While Material Design is a predominant design choice for building rich client-side applications, it's not the only popular design trend.
We plan to provide a [second design system](https://github.com/mui/material-ui/issues/22485) to expand the range of use cases for MUI, striking a balance between:
- alignment with the best-looking design trends of hot startups in the US.
- optimization of its usage for rich client-side applications while keeping it good enough for landing pages.
- simplicity of the design for allowing simpler customizations.
- complementarity with Material Design.
It will be built on top of the unstyled components: Base UI and our styling library: MUI System.
### MUI X
The recent data grid product initiative is working, it's time to scale MUI X by growing the team and the product scope.
#### Data Grid
We will keep the data grid as our primary effort, there are [many features left to be built 🚧](/x/react-data-grid/getting-started/#feature-comparison).
Our efforts will include: doubling down on the documentation, releasing the Premium features, and working on a hook-only API.
#### Date Picker
MUI Core had not enough bandwidth to work on the pickers components.
So we will expand the scope of MUI X to the date picker components, taking ownership and resuming where the work was left.
### Low-code
Pro-code (writing code in a regular programming language) has been an incredibly effective way to deliver on our mission so far.
The two main benefits reported by developers in our 2021 survey for using MUI are "moving faster" and "ease of use".
However, the data points we can find suggest that the demand for developers in the next 5-10 years is growing a lot faster than the growth of the workforce.
The importance of these two benefits is only going to increase, it's critical for MUI to keep pushing the envelope of what development speed and ease of use look like for developers.
Entering low-code, we have a small team that will continue explore in 2022 how MUI can empower developers and knowledge workers to build apps more visually, up to x10 faster, with no advanced SQL or JavaScript knowledge.
The goal is to write fewer lines of code, while still empowering developers to extend it with custom logic.
### Scale
If we sustain the current growth rate in 2022, we should be able to grow the team from 14 to 40 members in the company by the end of the year (based on the self bootstrap revenues).
The primary purpose will be to strengthen all the efforts that we have started, not starting any new ones until we reach a great level of execution on all the above.
At a high level we are guided by the following rock beliefs:
- React dominance in the UI development landscape will continue to increase in the next 5 years.
- Developers will always be looking to build faster, more appealing UIs, and with less specific knowledge.
- Low-code will progressively become mainstream for professional developers and knowledge workers.
If like us, you are excited about bringing joy to developers and enabling more people to build beautiful apps faster, check our positions, there are 8 open roles as of now, [we are hiring](/careers/)!
You can help us shape these new packages by taking part in discussions.
[RFCs](https://github.com/mui/material-ui/issues?q=is%3Aopen+label%3Adiscussion+%5BRFC%5D) are waiting for your feedback.
Don't hesitate to let us know what you think!
See you in 2022, thank for being part of this journey 🚀
| 4,128 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/blog/2022-tenerife-retreat.js | import * as React from 'react';
import TopLayoutBlog from 'docs/src/modules/components/TopLayoutBlog';
import { docs } from './2022-tenerife-retreat.md?@mui/markdown';
export default function Page() {
return <TopLayoutBlog docs={docs} />;
}
| 4,129 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/blog/2022-tenerife-retreat.md | ---
title: MUI's company retreat in Tenerife: a recap
description: Our internationally distributed startup gathered on a remote island to get to know each other better. Here's what happened!
date: 2022-07-28T00:00:00.000Z
authors: ['samuelsycamore']
card: true
tags: ['Company']
---
One of the toughest challenges to overcome as a fully remote team is fostering a supportive and inclusive company culture.
How do you build trust, comradery, and—dare I say it?—_friendships_, when there are so few opportunities for spontaneous social interactions in our daily work routines?
At MUI, we've chosen to prioritize in-person company retreats as a way to grow together and cultivate the culture that informs how we operate.
<img alt="Photo of the MUI team in front of the pool at our accommodations in Tenerife" src="/static/blog/2022-tenerife-retreat/group-photo.jpeg" style="width: 692px; aspect-ratio: 4/3;" />
<p class="blog-description">The MUI team poses next to the pool during the company retreat.</p>
In late June 2022, sixteen of us gathered at a remote private residence on the island of Tenerife.
This was MUI's second company retreat, the first being in Portugal in 2021 when the team was just a fraction of the size it is today.
We had a ton of fun getting to know each other better over oceanic activities, poolside conversations, and incredible catered meals—not to mention a steady supply of local wine. 🥂
Oh, and I guess we got some work done along the way, too? 😅
## Destination
<img alt="Satellite image of Tenerife" src="/static/blog/2022-tenerife-retreat/tenerife.jpeg" style="aspect-ratio: 4/3;" loading="lazy" />
<p class="blog-description">Satellite photo of Tenerife, via <a href="https://en.wikipedia.org/wiki/Tenerife">Wikipedia</a>.</p>
Tenerife is a volcanic island off the coast of western Africa that's part of the Canary Islands (Spanish: _Canarias_).
It is the most populous island in the archipelago, and one of the most visited tourist destinations in the world.
Its central defining feature is Mount Teide, the third largest volcano in the world when measured from its base, which rises 7,500 m (24,600 ft) from the bottom of the ocean floor, and 3,715m (12,188 ft) above sea level.
With an average temperature ranging from about 18-25 °C (68-77 °F) year-round, it's hard to pick a bad time to visit!
## Accommodation
<img alt="Photo of the pool in the evening at Symbiosis Living" src="/static/blog/2022-tenerife-retreat/pool-evening.jpeg" style="aspect-ratio: 4/3;" loading="lazy" />
<p class="blog-description">A view of the pool at Symbiosis Living as dusk approaches.</p>
[Symbiosis Living](https://www.symbiosisliving.com/) is a sustainable retreat venue nestled deep in the hills on the western side of the island.
The venue is a venerable oasis of lush green flora amid the stark and barren volcanic rock that surrounds it, hosting breezy guest houses adorned with rustic, regionally sourced furniture.
<img alt="Photo of the outdoor kitchen at Symbiosis Living" src="/static/blog/2022-tenerife-retreat/outdoor-kitchen.jpeg" style="aspect-ratio: 4/3;" loading="lazy" />
<p class="blog-description">The outdoor kitchen at Symbiosis Living.</p>
The owners were exceptionally accommodating and supportive for the entirety of our stay.
Almost all of our meals were cooked fresh by the hosts in their fabulous outdoor kitchen.
I don't think I've ever eaten that many incredible home-cooked meals in a single week. 😋
And somehow each one was even better than the last!
<img alt="MUI X colleagues José and Andrew bond over a bottle of wine at dinner one night during the retreat." src="/static/blog/2022-tenerife-retreat/jose-andrew-wine.jpeg" style="aspect-ratio: 4/3;" loading="lazy" />
<p class="blog-description">MUI X colleagues José and Andrew bond through the tradition of a brüderschaft (German: <em>brotherhood</em>) toast.</p>
## Activities
Throughout our stay in Tenerife, we arranged group activities to make the most of what the island has to offer.
### Whale and dolphin watching
<img alt="Danail from the MUI X team snaps a selfie on the bow of the whale-watching boat, with coworkers in the background." src="/static/blog/2022-tenerife-retreat/whale-watching-danail.jpeg" style="aspect-ratio: 4/3;" loading="lazy" />
<p class="blog-description">Danail snaps a selfie on the whale-watching boat.</p>
Our first full day together saw us venture out into the Atlantic Ocean in search of dolphins and whales.
The waters surrounding the Canary Islands are a biodiversity hotspot, and feeding grounds for many different species of marine mammals.
We spotted several [pilot whales](https://whalewatchtenerife.org/pilot-whales/) and what I believe were [bottlenose dolphins](https://whalewatchtenerife.org/bottlenose-dolphin/), though I'll be the first to admit that I'm no expert. 😅
Several of us (myself included) made a critical mistake by skipping the sunscreen because it was a cloudy day.
We got burned to a crisp!
And on the first day of the retreat, no less! 😭
Don't be like us.
Wear sunscreen.
### Scuba diving lessons
<img alt="MUI team members and their diving instructors pose in scuba gear before a successful scuba diving lesson." src="/static/blog/2022-tenerife-retreat/scuba-gear.jpeg" style="aspect-ratio: 4/3;" loading="lazy" />
<p class="blog-description">MUI team members and their diving instructors pose in scuba gear before a successful scuba diving lesson.</p>
On day two we split up into smaller groups to get individualized lessons in scuba diving at the beach in Playa San Juan.
To be honest I was pretty intimidated, especially after I put on all the gear and tried breathing from the tank for the first time.
But once I got into the groove, the time underwater went by so quickly!
The main highlights for me were spotting a [ray](https://aqua-marina.com/rays/) swimming by, and accidentally disturbing a [cuttlefish](https://www.paradisedivers.co.uk/blog/cuttlefish/) who was not pleased by our presence–and put on a great show as a result!
Sorry, bud!
<img alt="Overhead view of MUI team members learning how to scuba dive underwater." src="/static/blog/2022-tenerife-retreat/scuba-1.jpeg" style="aspect-ratio: 4/3;" loading="lazy" />
<p class="blog-description">MUI team members learn how to dive off the coast of Tenerife.</p>
### Volcanic hike at sunset
<img alt="A group photo of the MUI crew posing near the base of Mount Teide at the start of the hike." src="/static/blog/2022-tenerife-retreat/teide-group.jpeg" loading="lazy" />
<p class="blog-description">The group poses at the start of the trail toward Teide.</p>
The third and final full day of the retreat took us up to Teide National Park for a guided interpretive hike around some of the lower peaks that surround Mount Teide as the sun was going down.
This was my personal favorite out of all the activities.
We learned a lot about the natural history of the island from our guide, who led us to one of the best sunset views I've ever seen in my life.
Photos don't even begin to do it justice.
I completely understand why Teide is one of Europe's most visited parks.
<img alt="The sun setting above the clouds as seen near the top of Teide." src="/static/blog/2022-tenerife-retreat/teide-sunset.jpeg" loading="lazy" />
<p class="blog-description">The Tenerife sunset as seen from Teide, above the clouds.</p>
## And also work
Believe it or not, we actually did manage to squeeze in some productive work time between all the fun!
### Roadmap to v6
<img alt="MUI Core team members Marija, Jun, and Sam discuss the product roadmap." src="/static/blog/2022-tenerife-retreat/focus-group.jpeg" loading="lazy" />
<p class="blog-description">MUI Core team discusses the product roadmap.</p>
One of the key goals of the retreat was to outline mid- to long-term goals for our products, and begin to estimate timelines to get where we want to go from here.
We had some great conversations about what we hope to accomplish over the next several months on the way to our next major release: MUI v6.
It's still hard to say when that release day might come, but we're optimistic that we could see it in mid to late 2023.
[@RemindMe_OfThis](https://twitter.com/RemindMe_OfThis) September 2023 🙃
<img alt="The product teams are seen spread out around a large indoor/outdoor workspace" src="/static/blog/2022-tenerife-retreat/focus-groups.jpeg" loading="lazy" />
<p class="blog-description">Product teams spread out throughout the breezy indoor/outdoor workspace.</p>
In any case, we now have a better idea of what v6 could look like, and we defined quite a few initiatives to move forward with while we're still in the world of v5.
Keep an eye out!
### Focus groups
<img alt="An impromptu focus group gathered next to the pool with laptops to discuss cross-team marketing strategies." src="/static/blog/2022-tenerife-retreat/outdoor-focus-group.jpeg" loading="lazy" />
<p class="blog-description">A focus group gathers to talk about developer marketing and outreach.</p>
Before the retreat, we were all invited to propose topics to cover in smaller groups for those who were interested.
This gave us a great opportunity for some cross-team collaboration that isn't usually part of our standard workflow.
I participated in sessions on copywriting, marketing, and developer outreach that I found particularly exciting—but I'm kind of a nerd like that. 🤓
Others discussed optimizing TypeScript performance, implementing editable demos in the docs, and supporting [Joy UI](/blog/first-look-at-joy/) with MUI X components, among other things.
### Our feline colleague 🐈
All throughout our working sessions, we were accompanied by a very friendly young kitty (name unknown) who consistently offered critical support when we needed it the most.
We can't thank her enough for her contributions to the company roadmap.
<img alt="Collage of several photos of the MUI team members cuddling with the neighborhood cat during our work sessions." src="/static/blog/2022-tenerife-retreat/cat-collage.jpeg" loading="lazy" />
<p class="blog-description">The cat was responsible for all of the cutest moments during the retreat.</p>
### In sync with the async team
It was honestly kind of odd to have (almost) all of my coworkers in the same as room as me.
This was the first time that the majority of us had ever met anyone else from the company in person—myself included.
But once we broke the ice and settled into a rhythm together, I felt that we established some common bonds and yes, friendships, that we will carry with us long after the sunburns have faded.
I'm really grateful to have had the opportunity to connect with some of the best and brightest colleagues I've ever had, and in such an idyllic location.
I think we're all already daydreaming about the next time we'll get to do this!
Speaking of which…
## Will you be at the next retreat?
We're hiring!
MUI is on track to grow from roughly 20 people to 40 or more by the time we get to our next company retreat in late Q1 2023.
We are constantly interviewing React developers from all around the world, and we are also increasingly looking to hire for non-technical roles such as [People Operations Manager](/careers/people-operations-manager/) in which you could have a huge impact steering the direction of the company's nascent HR department.
Check out [our open roles](/careers/) so you can join us before the next retreat!
The way I see it, we have two options—since it'll be the dead of winter for the Northern Hemisphere, we can either:
1. lean into the winter fun, maybe go skiing in the Alps? ⛷
2. escape the cold by heading to some Equatorial beaches 🏝
If you have a strong opinion one way or the other, then you better join the team sooner rather than later!
I look forward to meeting new colleagues—as well as reconnecting with the Tenerife crew—in 2023.
<img alt="The path leading down the hill from the sunset view, with Teide glowing red in the background." src="/static/blog/2022-tenerife-retreat/teide-hike.jpeg" loading="lazy" />
<p class="blog-description">One final view of Teide glowing red in the sunset.</p>
| 4,130 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/blog/2023-chamonix-retreat.js | import * as React from 'react';
import TopLayoutBlog from 'docs/src/modules/components/TopLayoutBlog';
import { docs } from './2023-chamonix-retreat.md?@mui/markdown';
export default function Page() {
return <TopLayoutBlog docs={docs} />;
}
| 4,131 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/blog/2023-chamonix-retreat.md | ---
title: MUI's team retreat in Chamonix
description: The MUI team spent five days in the French Alps team-building, problem-solving, and brainstorming. Read all about it!
date: 2023-03-16T00:00:00.000Z
authors: ['mikailaread']
card: true
tags: ['Company']
---
## Why the Chamonix gathering?
Being a distributed team means everyone at MUI works asynchronously.
We celebrate having the freedom to deeply focus on what we're delivering, and being able to fit work around life instead of life around work. 😀
But this way of working can also mean some team members experience very little overlap in their online hours, which can make it more challenging to connect personally or collaborate.
So, what do we do?
MUI is extremely intentional about bridging gaps by bringing our people together every ~8 months (as a minimum).
_Our team retreats are about providing everyone a more tangible opportunity to feel part of the MUI community and to learn more about each other outside of work._
It's a time to focus more on who we are as individuals, which creates a wonderful ripple effect on the ways we work together as a team.
## Where did we go?
Photo of the Heliopic Hotel & Spa exterior, via [Assas Hotels](https://www.assas-hotels.com/en/hotel-heliopic-sweet-spa/).
<img alt="Wooden architecture exterior of the Heliopic Hotel and Spa" src="/static/blog/2023-chamonix-retreat/hotel-exterior.jpeg" style="margin-bottom: 16px;" loading="lazy" width="2154" height="1212" />
Chamonix is a world capital for outdoor activities, such as mountaineering, skiing, snowboarding, paragliding, hiking, climbing, and so much more!
The Chamonix Mont Blanc valley offers unmatched alpine views, plus a whole host of stunning protected flora and fauna.
With a bustling city center full of quaint shops and restaurants — there's something for everyone to enjoy.
We stayed in the beautiful Helopic Hotel & Spa, which fit our needs perfectly. With fully-equipped conference rooms, a cozy lobby bar, a table-service restaurant, and a luxury spa — everything we needed was on-site. (The food was delicious, too!)
<img alt="A plated apple dessert with three scoops of ice cream." src="/static/blog/2023-chamonix-retreat/dessert.jpeg" loading="lazy" width="4032" height="3024" />
## What did we do?
We kicked off the week with several unique team-building activities, including a mini Winter Olympics, a competitive team biathlon, and even axe-throwing. 🎯🪓
Engaging in new experiences together gave us an opportunity to learn about each other's strengths and weaknesses, and to develop a better understanding of how our differences influence the ways we might communicate and work together.
It also provided room for team members to share past experiences with one another and gain new perspectives.
<img alt="Members of the MUI team standing in a line with their arms extended on each others' shoulders." src="/static/blog/2023-chamonix-retreat/caterpillar-game.jpeg" style="margin-bottom: 16px;" loading="lazy" width="2048" height="1536" />
<img alt="MUI team members cross-country skiing." src="/static/blog/2023-chamonix-retreat/biathlon-skiers.jpeg" style="margin-bottom: 16px;" loading="lazy" width="2048" height="1536" />
<img alt="MUI team members standing in a line shooting air rifles as part of a biathlon competition." src="/static/blog/2023-chamonix-retreat/biathlon-shooters.jpeg" style="margin-bottom: 16px;" loading="lazy" width="2048" height="1536" />
On the work-front, we hosted our monthly team meeting and offered a spread of different topic-based sessions for a "choose your own adventure" feel.
People could opt into the sessions they felt most passionate or excited about, which really helped to sustain energy and result in fruitful discussions.
Solving challenges and sparking new ideas takes on such a different feel when you're all in the same time and place!
Our team walked away with a number of actionable changes and commitments for the near and far future.
<img alt="MUI team members sit in a half-U shape as Co-Founder Olivier Tassinari presents the monthly meeting slides." src="/static/blog/2023-chamonix-retreat/monthly-meeting.jpeg" style="margin-bottom: 16px;" loading="lazy" width="4032" height="3024" />
Following our very productive sessions, it was time to relax and refresh ourselves.
We decided to increase the amount of downtime on our final day together and leave space for serendipitous fun to unfold.
And guess what: _**it worked!**_
One of the most-loved parts of our retreat in team feedback surveys turned out to be a completely unplanned game night.
Despite tiring return journeys ahead, an exhausted group of us set up camp in the hotel lobby to play cards and board games into the wee hours of the morning.
Special bonds formed over some very colorful rounds of Saboteur and terribly-executed magic tricks. 🙃🎩
It was just what we needed to close out the retreat with some moments of real connection.
## What's next?
If you can believe it, we're already busy planning our next meet-up. Although we haven't decided on an exact location just yet, the team has agreed this much loud and clear: somewhere warm! ☀️😅
<img alt="Two members of the MUI team and skiing instructor smiling with a mountain vista in the background." src="/static/blog/2023-chamonix-retreat/mountaineers.jpeg" style="margin-bottom: 16px;" loading="lazy" width="4032" height="3024" />
<img alt="MUI team members standing lined-up in the snow with their skigear." src="/static/blog/2023-chamonix-retreat/skiers.jpeg" loading="lazy" width="4096" height="3072" />
## Join the team
MUI is on track to double in size by the end of this year with lots of open roles in engineering, design, and product teams.
Our target date for the next company retreat is November 2023.
To have your say in where we go and what we do, join us now.
[Visit our careers page!](/careers/) 🏃💨
<img alt="Members of the MUI team sitting around a large wooden dining table." src="/static/blog/2023-chamonix-retreat/team-dinner.jpeg" loading="lazy" width="4032" height="3024" />
| 4,132 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/blog/2023-mui-values.js | import * as React from 'react';
import TopLayoutBlog from 'docs/src/modules/components/TopLayoutBlog';
import { docs } from './2023-mui-values.md?@mui/markdown';
export default function Page() {
return <TopLayoutBlog docs={docs} />;
}
| 4,133 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/blog/2023-mui-values.md | ---
title: Evolving MUI's core values and behaviors
description: After significant growth, we united as a team to rediscover the values that underpin our shared success.
date: 2023-09-26T00:00:00.000Z
authors: ['mikailaread']
card: true
tags: ['Company']
---
## Why we chose to revise our core values
MUI was founded in 2014 to grow and serve a community—from developers to designers, our core mission has always been to enable others to create incredible user experiences with unrivaled speed and ease.
Along the way, we embraced certain core principles that guided our ways of working—how we think, act, and innovate have always been grounded in fulfilling the best interests of our community.
In 2019, these became formalized in our first-ever company values: user obsession, excellence, transparency, freedom, and autonomy.
Needless to say, we've seen significant growth since then: both for the company and its products, as well as the broader community surrounding us.
That's why we wanted to take a moment to honor the values that led us to where we are today, and share how we've reshaped them to be an even more powerful force behind MUI's next phase of growth. 🚀
## How we approached our values revision
Company values show up in some facet of all our roles every day, whether we're evaluating different ideas, making tough decisions, or determining the biggest priorities.
That's why it's so critical to ensure company values are actionable and authentic—that they are easily understood and truly shared by every MUIer.
To make that happen, we decided to engage the whole company in a series of discovery and reflection exercises. 🔍
This way, any changes to the company values—along with the language used to express them—would accurately reflect the values shared by our team. Here's how we did it! 👇
<img alt="A collage of slides from the values discovery exercise kickoff." src="/static/blog/2023-mui-values/good-values.png" width="1200" height="840" loading="lazy" />
## Stage one: discovery questions
Kicking off, everyone was invited to answer 10 questions via an asynchronous survey.
The purpose of this portion was to get a picture of how the existing values were being perceived and actioned throughout the company from day to day.
It was also to give people an opportunity to express what they felt may be _missing_ and important to include for our future success.
We asked people to reflect on how accurately they felt each value described our internal culture; what they felt our company cared deeply about and why; what is utterly unique about us as a team; and more. 🤔💭
<img alt="A screenshot of the intro page to our discovery survey." src="/static/blog/2023-mui-values/values-survey.png" width="1200" height="1170" loading="lazy" style="margin-bottom: 16px;" />
Then, using keyword and sentiment analysis, we captured clear themes in experience and common language used to describe our culture.
I presented this back to the team via recorded video presentation, inviting reactions and further dialogue in the open of our Slack workspace.
<img alt="A screenshot of a video message in our internal Slack revealing themes from the survey." src="/static/blog/2023-mui-values/themes-video.png" width="1200" height="750" loading="lazy" />
## Stage two: workshop
At the next stage, folks came together for a synchronous workshop.
(This was completely voluntary, but I'm proud to say we had major representation from all different corners and levels of the company!)
The purpose of this workshop was to pinpoint the _most_ critical mindsets and behaviors that we felt underpinned the company's success at scale.
Broadly speaking, everyone was asked to consider:
1. what mindsets and behaviors we should actively preserve and encourage as we scale—these are our superpowers and biggest differentiators. They're the stuff that makes us "us." 💚
2. what mindsets and behaviors should we actively discourage, even punish—these are the biggest threats to our desired culture. They're the things we would never tolerate, maybe even at the cost of a customer. 🛑
We used a shared FigJam board to brainstorm together against a timer, and repeated the process for different core questions.
Once we'd generated a wonderfully full board, we took a pause to review the contributions.
We upvoted cards that really stood out and resonated with us as individuals.
Finally, we organized all of these cards into little clusters based on relatedness, and started to identify their underlying values and themes.
We came up with a list of words that we felt best encapsulated each cluster. This became our values "shortlist."
<img alt="description" src="/static/blog/2023-mui-values/figjam-board.png" width="1200" height="500" loading="lazy" />
## Stage three: transforming the shortlist
36.
That's how many words surfaced in our workshop as potential values—or at least, as words to inspire the copywriting process.
Narrowing down the shortlist gave us a chance to both find _and_ stress-test the strongest recurring themes. 🧪
To do this, we immediately eliminated [what Patrick Lencioni calls "permission-to-play" values](https://www.youtube.com/watch?v=bNRn6FimzoU).
These are the things as basic as showing respect, which might be _valuable_ to a great team culture and performance, but aren't exactly _exciting_ or _measurable_.
They're simply the minimum required standard of behavior to work together.
We also started striking out anything that could not clearly be expressed _as an action._
It's [what Simon Sinek was talking about](https://www.youtube.com/watch?v=IQuYzXWXDqI) when he said "honesty is not a value."
If there was not a clear and natural way to transform something into an action or provide examples of how it would be lived in our specific workplace, it was out. 🙅
Success!
We narrowed the list down from 36 to _just six._
Now it was time to transform these six words into actionable phrases to inspire the very actions we want to see championed on a daily basis.
## Stage four: pitching the 'PACT'
All of the above and more influenced what's now referred to as our team "pact." (You'll see why.)
But before we get there, I want to share a few examples of phrases that didn't wind up being a part of the pitch and why.
Finding the right phraseology started with carefully reviewing _all_ team inputs.
As I had a unique vantage point of all those inputs, I began to jot down phrases that effectively pulled from them _all_ and led with _action verbs._ 🕸️💪
Things like "build in the open" made an appearance, but felt too limited.
There was so much more we wanted to capture in the enduring theme of transparency, why it matters to us, and how we show it.
Other phrases included "own your impact" and "maximize flexibility," but these, again, felt too limited and also generic.
In short, they weren't right.
Fortunately, this helped us find the ones that **\***are.**\*** 👏
I presented a video presentation to our team, pitching this set of values and providing another opportunity for feedback and shaping.
You can <a href="https://www.notion.so/mui-org/Values-behaviors-d3a1e1c60e2a4c0782f770cceada54bd?pvs=4#09dc19a420504a3090dc4fbe6a68a543">watch the "reveal" video for yourself here</a>! 🎬👀
## Stage five: revising and finalizing
Since we work asynchronously at MUI, we like to leave a good window of time for peers to properly review, digest, and offer thoughtful feedback.
Since we place such a high value on quality and accuracy, we didn't want to rush this process, and so we extended our deadline for delivery.
As we approached the finish line, I collaborated closely with our CEO and co-founder, Olivier. 🙋
Our goal was to ensure that the final values not only reflected our team and company culture but, most importantly, that they could be integrated effectively into our company's operations and performance expectations.
And we believe we've achieved just that! Here they come... 🥁
## What are MUI's core values today?
Our core four are:
**P** — Put community first. "We never lose sight of who we're serving and why." 💙
**A** — Avoid bureaucracy. "We're so not corporate—and we like it that way." 🚫
**C** — Chase better. "We're driven by an unending desire to improve." 🌱
**T** — Trust and deliver together. "We cultivate unity as the core of achievement." 🚀
To delve deeper into the meaning of each value and what it looks like in practice, you can also check out our handbook: <a href="https://www.notion.so/mui-org/Values-behaviors-d3a1e1c60e2a4c0782f770cceada54bd?pvs=4">Values & Behaviors.</a>
In it, we offer concrete examples of each core value and explicitly address tensions folks may encounter in trying to live them out.
<img alt="description" src="/static/blog/2023-mui-values/notion-values-page.png" width="1200" height="1170" loading="lazy" />
## What do they mean?
### Put community first
Put community first underscores our unwavering commitment to anchoring every decision in the best interests of the collective.
By "community", we refer to both the user base that we serve and the team that propels us forward.
The litmus test for any decision at MUI begins with a simple yet profound query: How does this contribute to our community's progress? We prioritize the needs and feedback of the community, and invest our efforts toward what will bring the greatest benefit to the greatest number of people.
Putting community first means also that we consciously forge connections.
We recognize that deeper mutual understanding fuels collective progress.
By investing in relationships, we enhance collaboration, foster productive teamwork, and create a work environment that's as enjoyable as it is efficient.
### Avoid bureaucracy
Avoid bureaucracy is all about staying lean, open, and people-first.
One of the core beliefs we hold at MUI is that people are the best experts on when, where, and how they will do their best work.
We actively champion this principle by fostering an environment of unparalleled flexibility and autonomy, which serves as a bedrock for sustained excellence.
Our dedication to shunning bureaucracy manifests in tangible ways—for instance, most of our communications and work are in the open.
We default to transparency as much as possible.
We don't over-structure, or add processes or hierarchies where they aren't needed.
To introduce a process, we need to clearly show how it makes things 10x better than the current approach.
We don't have lengthy approvals processes or a formalized chain of command; instead we collaborate as a tight-knit network where anyone can ask about and contribute to anything.
### Chase "better"
Chase "better" is all about consistently improving and developing in all aspects of our work as well as raising the bar for quality.
It addresses our attitude to risk, feedback, and setbacks too.
Genuine innovation demands a fearless embrace of the uncharted, even if it entails a touch of chaos.
We want to create the exceptional—not the "good enough."
So we tend to prioritize quality over speed.
This doesn't mean we wait for things to be perfect before releasing them.
On the contrary, "chase better" encourages us all to make small changes and incremental improvements again and again.
It also encourages us to venture into unfamiliar territory and get out of our comfort zones in the name of growth.
### Trust and deliver together
Trust and deliver together is all about building trust, alignment, and shared responsibility.
It reflects our commitment to following through and working as one force to solve problems and create value.
In practice, this looks like: doing what we say we will; proactively communicating progress; adapting swiftly to changing circumstances and demands to guarantee success; and readily offering or seeking help when necessary.
It's also about strategic collaboration, and being able to recognize and enlist one another for our unique strengths toward shared goals.
"Trust and deliver together" reflects our firm belief that together, our combined efforts are stronger and more impactful than what we can achieve individually.
## How do we reinforce values across the org?
Articulating company values and operationalizing them are two different things.
To ensure values don't become mere writing on the wall at MUI, we've purposefully woven them into internal processes and programs.
We surface them often and stay attuned to how people are perceiving and connecting to them through different initiatives. 🌠🔦
For example, before you even join MUI, you'll answer carefully chosen questions in your interviews.
This helps us understand how well you align with our company values and how you might contribute to enhancing them and our culture. 📝
On a day-to-day level, values show up everywhere.
They're referenced in discussions and deliberations related to our work.
We explicitly state how they directly influence our strategies and plans within our documents.
Exemplifying core values is also a condition for promotion here and therefore a topic in performance and development conversations. 🆙
As a fun way to reinforce values and show team gratitude, we've also created #Thanks-And-Praise Thursdays—a dedicated Slack channel that prompts us every Thursday to think about who we could recognize for championing core values and behaviors.
Our design team even created custom illustrations and Slack emojis to make highlighting values-driven moments as simple as just a few clicks.
(Thank you Gerda, Victor, and Danilo!) 🙏
<img alt="Custom-designed illustrations for each MUI company value." src="/static/blog/2023-mui-values/values-illustrations.png" width="1200" height="500" loading="lazy" />
## When might the values change again?
MUI's first values were set forth by our founders during the earliest stages of the company, with the recognition that they would evolve alongside our company's growth.
Those values remain foundational to the ways we work and engage.
It's quite evident how these have been represented in new ways within the core four.
But we don't expect these to last forever, either.
As we continue to progress through new stages of development in the coming years, we intentionally plan to review our values and continue cultivating a values-driven culture.
## Join the team
Do these values resonate with you? Perhaps you'd like to be a part of shaping the future of MUI.
[Visit our careers page now!](/careers/) 🏃💨
| 4,134 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/blog/2023-toolpad-beta-announcement.js | import * as React from 'react';
import TopLayoutBlog from 'docs/src/modules/components/TopLayoutBlog';
import { docs } from './2023-toolpad-beta-announcement.md?@mui/markdown';
export default function Page() {
return <TopLayoutBlog docs={docs} />;
}
| 4,135 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/blog/2023-toolpad-beta-announcement.md | ---
title: Introducing Toolpad: MUI's low-code admin builder
description: Assemble admin panels and internal tools faster than ever before with Toolpad—now in beta.
date: 2023-07-24T00:00:00.000Z
authors: ['prakhargupta']
card: true
tags: ['Product', 'News']
---
It's been over a year since we released the first version of Toolpad. Today, we're excited to take the next step on that journey with the release of Toolpad Beta. If you aren't familiar with Toolpad yet, it's an admin panel builder catering to the internal tooling needs of an organization, designed for developers who want to build a functional application quickly. It harnesses the speed of a UI builder for the front-end and closely integrates into your back-end. If this excites you, then read on!
<a href="https://mui.com/toolpad/examples/basic-crud-app/">
<img alt="Introducing Toolpad" src="/static/blog/2023-toolpad-beta-announcement/intro.png" loading="lazy" width="2400" height="1200" />
</a>
## Why did we decide to build Toolpad?
Toolpad was created to meet the needs of the MUI community. As a result of surveys we conducted, and market research we undertook, we decided to develop an internal tool builder because the idea resonates with MUI's mission of empowering developers to build apps faster and more efficiently.
Internal tools are software applications that are developed and used within an organization itself. They can automate tasks, manage data, and help foster collaboration. Internal tools are a valuable asset for businesses of all sizes, as they help to improve efficiency, productivity, and communication.
We've all had our fair share of wrestling with lousy internal tools that we hoped we'd never have to use more than once. A sub-optimal tool means a waste of time and effort for everyone. Maintaining them distracts developers from solving actual business problems. In recent years, customer-facing software has moved quickly and is now flashy and sleek. It's time for internal tools to get this same upgrade.
## What is Toolpad exactly?
Toolpad is an open-source, low-code, drag-and-drop admin builder. The primary purpose of Toolpad is to create data-intensive React apps faster. Toolpad simplifies building UI, writing back-end logic, connecting to a data source, querying and mutating data. It can quickly convert an API, script, or SQL query into a web UI.
Toolpad is not ideal for building static web pages, mobile apps, or customer-facing custom-designed front-ends. It's for building admin applications, CRUD interfaces, custom internal tools, and analytics dashboards.
<a href="https://mui.com/toolpad/examples/npm-stats/">
<img alt="Building an application on Toolpad" src="/static/blog/2023-toolpad-beta-announcement/toolpad.png" loading="lazy" width="2400" height="1394" />
</a>
## Who is Toolpad for?
Before the arrival of Toolpad, MUI primarily catered to the front-end needs of the development process. Our products were mostly useful for React engineers or designers, but we saw many full-stack engineers use our advanced components for data-intensive apps. These highly customizable components are well-suited for complex apps, but not all apps require the same level of customization: for example, internal tools just need basic theming.
<img alt="Toolpad personas" src="/static/blog/2023-toolpad-beta-announcement/personas.png" loading="lazy" width="2076" height="900" style="margin-bottom:24px;" />
Toolpad is for you if you're a full-stack or back-end developers who builds, manages, and integrate data pipelines, server-side logic, databases, microservices, and APIs—and knows the most about them. Sharing these endpoints with and maintaining the internal documentation for the front-end teams is a hassle that lasts forever. Toolpad empowers you to take the next step and build the UI you need using our drag-and-drop editor, without losing any part of your normal development workflow.
## What are the main features available today?
### 1. Drag-and-drop UI builder
Easily create user interfaces by dragging and dropping pre-built components onto the canvas. Utilize constraints to speed up the building process.
<a href="https://mui.com/toolpad/examples/basic-crud-app/">
<img alt="Dragging components to the canvas" src="/static/blog/2023-toolpad-beta-announcement/drag.png" loading="lazy" width="2400" height="1394" />
</a>
### 2. Query builder UI
A Postman-like query builder allows you to integrate any REST API quickly. A binding editor, which supports JavaScript, allows you to wire query response directly to the components.
<a href="https://mui.com/toolpad/examples/npm-stats/">
<img alt="Building an application on Toolpad" src="/static/blog/2023-toolpad-beta-announcement/uiquery.png" loading="lazy" width="2400" height="1394" />
</a>
### 3. Bring your own components
Toolpad can import [external React components](https://mui.com/toolpad/concepts/custom-components/), ready to be used in its visual designer. Your past effort shouldn't go to waste and you shouldn't be limited by the stock component suite.
### 4. Bring your own back-end
Directly integrate with your Node.js back-end and have your data available on the page without writing any REST endpoints or fetch logic. Need that prisma model on the page? Expose it through a serverless function and Toolpad does the rest.
### 5. Own your code
Toolpad runs completely locally. You're not stuck with an online code editor or a suboptimal GitHub integration. All configuration is stored in local files which you can version-control, edit, and deploy in any way you want.
<a href="https://mui.com/toolpad/examples/basic-crud-app/">
<img alt="Building an application on Toolpad" src="/static/blog/2023-toolpad-beta-announcement/code.png" loading="lazy" width="2400" height="1394" />
</a>
### 6. A catalogue of components powered by Material UI
Material UI provides production-ready React components; a chosen few are currently available inside Toolpad, and we're adding more all the time.
<a href="https://mui.com/toolpad/examples/npm-stats/">
<img alt="Building an application on Toolpad" src="/static/blog/2023-toolpad-beta-announcement/library.png" loading="lazy" width="2400" height="1394" />
</a>
## How is Toolpad different from similar products on the market?
In this domain, there are two categories of products:
1. **Visual first**: Retool, Appsmith, Budibase and the likes. While these are great tools, they don't integrate with the developer's local IDE nor offer a good git version control mechanism. Providing features that could have been hand-coded on a need basis makes the application heavy, and reports of slowness at runtime are common.
2. **Code first**: Airplane.dev, Interval and others. They also allow building internal tools but don't support a drag-and-drop UI builder. The components must be coded using their APIs, which comes with some learning curve.
Toolpad is solely focused on professional developers. As much as we are low-code, we are equally code-friendly. Providing the basic functionality that you expect from an open-source tool is non-negotiable for us—we will always prioritize your best interests over all else. With nearly a decade of experience building developer tools, we understand the long-term benefits of cultivating a close relationship with our community of users.
Lastly, Toolpad is the only product that offers a drag-and-drop UI builder closely integrated with your favorite IDE, such as VSCode. It's the best of both the worlds!
## How can I use Toolpad?
Toolpad is available as an NPM package. Follow the [Installation guide](https://mui.com/toolpad/getting-started/installation/) in the docs to get started. You can learn more about Toolpad by visiting the [home page](https://mui.com/toolpad/).
<img alt="Toolpad documentation and instructions on how to use it" src="/static/blog/2023-toolpad-beta-announcement/docs.png" loading="lazy" width="2400" height="1394" />
## What's next?
We plan to continue to iterate on our vision of helping you as a developer to increase the speed and efficiency of your workflow. We want to optimize for the biggest pains that you face when building admin apps. Your input is crucial to helping us shape the roadmap from here.
The best places to stay up-to-date about what we're currently working on are [GitHub issues](https://github.com/mui/mui-toolpad) and our [public roadmap](https://github.com/orgs/mui/projects/9/views/1).
If you have any questions or would like to share feedback, you can directly contact the team at [email protected] or reach us on [Twitter](https://twitter.com/MUI_Toolpad). You can also engage in conversation in our [Discord](https://mui.com/r/discord/) server.
If you'd like an in-depth demo and to discuss your use case, please feel free to [schedule a meeting with me on Calendly](https://calendly.com/prakhar-mui).
| 4,136 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/blog/aggregation-functions.js | import * as React from 'react';
import TopLayoutBlog from 'docs/src/modules/components/TopLayoutBlog';
import { docs } from './aggregation-functions.md?@mui/markdown';
export default function Page() {
return <TopLayoutBlog docs={docs} />;
}
| 4,137 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/blog/aggregation-functions.md | ---
title: Aggregate data like in Excel, but easier!
description: Aggregation functions and summary rows are now available in the MUI X Premium Data Grid.
date: 2022-08-01T00:00:00.000Z
authors: ['josefreitas', 'flaviendelangle', 'cherniavskii']
tags: ['MUI X', 'News']
card: false
---
If you've ever worked with a data-heavy grid, then you understand how important it is for the end user to be able to set different perspectives on the data to gather the information they're looking for.
Basic functions like filtering and sorting barely scratch the surface of their needs.
The Premium Data Grid is all about enabling and empowering advanced use cases for data analysis.
And in that spirit, we're overjoyed to announce that starting from [v5.15.0](https://github.com/mui/mui-x/releases/tag/v5.15.0), you can now use [aggregation functions](/x/react-data-grid/aggregation/), and with a couple of clicks, extract information like **sum**, **average**, **count**, and others.
## Wait, what is an aggregation function?
Aggregation functions are used to return a computed result based on the values of a given column.
For example, you might have a list of financial transactions, and you want to get the sum of all transactions and display it in a summary row, as shown in the video below:
<video style="margin-bottom: 24px;" autoplay muted loop playsinline controls>
<source src="/static/blog/aggregation-functions/summary-row.mp4" type="video/mp4" />
</video>
## Intuitive end-user experience
The **Sum** function showing a **Total** in summary rows is one of the most common use cases. But users can employ multiple aggregation functions in different columns simultaneously, and even combine with row grouping to aggregate children's data on each group.
To make all that work well together, we knew that the focus had to be on creating the best end-user experience possible. The goal was to enable the majority of use cases right out of the box, without any need for significant customization.
How easy can it be to get the average transaction value per user?
Check out the video below to see it in action:
<video style="margin-bottom: 24px;" autoplay muted loop playsinline controls>
<source src="/static/blog/aggregation-functions/with-row-grouping.mp4" type="video/mp4" />
</video>
## Customize everything
The out-of-the-box experience is very important to us, but equally important is the ability to customize and extend the feature to suit your own use case.
You can change the styles of every element involved, set automatic aggregations, choose which columns can be aggregated by which functions, and even create your own custom functions.
In the example below, we created a function to get the first value in alphabetical order:
```ts
const firstAlphabeticalAggregation: GridAggregationFunction<
string,
string | null
> = {
apply: (params) => {
if (params.values.length === 0) {
return null;
}
const sortedValue = params.values.sort((a = '', b = '') =>
a.localeCompare(b),
);
return sortedValue[0];
},
// The `label` defines what's displayed in the column header when this
// aggregation is active.
label: 'First Alphabetical',
// The `types` property defines which type of columns can use this
// aggregation function. Here, we only want to propose this aggregation
// function for `string` columns. If not defined, aggregation will be
// available for all column types.
columnTypes: ['string'],
};
```
<video style="margin-bottom: 24px;" autoplay muted loop playsinline controls>
<source src="/static/blog/aggregation-functions/with-custom-functions.mp4" type="video/mp4" />
</video>
## Okay, I'm in! How can I get started?
Aggregation functions are available in `@mui/x-data-grid-premium`, version `5.15.0` or later.
This feature is currently considered experimental as we continue to validate its API and refine our goals for it.
But it is stable, and the API most likely will not change significantly.
You can activate the feature with the `experimentalFeatures` prop:
```tsx
<DataGridPremium experimentalFeatures={{ aggregation: true }} {...otherProps} />
```
And that's it! That enables the **Aggregation** option on the column menu, which is available by default on columns of type number and string.
## Use with tree data and more
We already mentioned that you could customize functions and use aggregation with row grouping. But there are a lot of other possibilities to explore!
Please check out the feature's [full documentation](/x/react-data-grid/aggregation/) to get a better overview of everything it has to offer.
## Row pinning
The Aggregation footer row is powered by another new feature called [Row pinning](/x/react-data-grid/row-pinning/).
It enables you to pin rows to the top or bottom of your data grid.
Pinned rows are visible at all times while the user scrolls the grid vertically.
<video style="margin-bottom: 24px;" autoplay muted loop playsinline controls>
<source src="/static/blog/aggregation-functions/row-pinning.mp4" type="video/mp4" />
</video>
Row pinning is available in the Pro and Premium Data Grids.
Check out more details in the [Row pinning documentation](/x/react-data-grid/row-pinning/).
## Share your feedback 🗣
**And if you're feeling generous, we're recruiting users to interview!**
We hope you're excited about the new features as we are!
As always, we're happy to hear from you.
Please feel free to open new issues to report bugs or suggest improvements.
Moreover, we're planning MUI X v6, and we'd love to hear more about your pain points and use cases.
If you want to help steer the direction of our components, please consider [contacting us](https://forms.gle/vsBv6CLPz9h57xg8A) to schedule a 30-minute user interview session.
| 4,138 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/blog/april-2019-update.js | import * as React from 'react';
import TopLayoutBlog from 'docs/src/modules/components/TopLayoutBlog';
import { docs } from './april-2019-update.md?@mui/markdown';
export default function Page() {
return <TopLayoutBlog docs={docs} />;
}
| 4,139 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/blog/april-2019-update.md | ---
title: April 2019 Update
description: Here are the most significant improvements in April.
date: 2019-05-07T00:00:00.000Z
authors: ['oliviertassinari']
tags: ['Company']
---
Here are the most significant improvements in April:
- 📚 We have migrated [most](https://github.com/mui/material-ui/issues/14897) of our demos to TypeScript. **@eps1lon** has lead the effort. You can switch between the JavaScript demo and the TypeScript demo using this toggle button:
This was only possible thanks to the contributions **@merceyz**, **@sperry94**, **@jasondashwang**, **@bh1505**, **@donigianrp**, **@Dudrie**, **@eluchsinger**, **@cahilfoley**, **@gabrielgene**, **@kenzhemir**, **@Adherentman**, **@lksilva**, **@Tevinthuku**. Thank you!
Supporting these TypeScript demos has one important implication, it forces us to have working TypeScript definitions ✨.
- 🎀 We have migrated a large chunk of our components from classes to hooks. **@joshwooding** has lead the effort. We will explain why in the v4 release blog post.
- 📐 We have updated our components to better match the Material Design guidelines
(Snackbar, List, Checkbox, Radio & Switch).
- 🎁 We have added a demo for building a [TransferList](/material-ui/react-transfer-list/) component.
[](/material-ui/react-transfer-list/)
- 💅 We have changed the class name generation to output global class names.
We have seen many people struggling with our `classes` API.
This API targets plain CSS and styled-components users.
It can be challenging to apply your class name on the right element with the `classes` API. It can also be cumbersome. ⚠️ Using global class names provide more power but comes with a responsibility. We encourage any pattern that increases your **custom style isolation**.
[](/system/styles/advanced/)
- 📅 We have moved material-ui-pickers to our organization: [@material-ui/pickers](https://www.npmjs.com/package/@material-ui/pickers). A big thanks to **@dmtrKovalenko** for creating and owning these date/time components.
- 🔥 We have fixed more Strict Mode warnings, getting us closer to [Concurrent React](https://legacy.reactjs.org/blog/2018/11/27/react-16-roadmap.html#react-16x-q2-2019-the-one-with-concurrent-mode) support.
- ♿️ We have significantly improved the keyboard behavior on the Select, Menu, Button and Tooltip components. The arrow key changes feel instantaneous. The select items can be selected with the alphabetical keys. The focus visible state is better detected.
- 💄 We have added support for responsive font sizes. You can wrap your theme with [`responsiveFontSizes()`](/material-ui/customization/typography/#responsive-font-sizes):
[](/material-ui/customization/typography/#responsive-font-sizes)
- We have added support for custom [header scroll behaviors](/material-ui/react-app-bar/#scrolling):
<video style="margin-bottom: 24px;" autoplay muted loop playsinline>
<source src="/static/blog/april-2019-update/scroll-trigger.mp4" type="video/mp4" />
</video>
But this summary is just scratching the surface. We have accepted 243 commits from 69 different contributors. We have changed 1,545 files with 36,461 additions and 20,237 deletions.
## Our roadmap intent for May
_(We'll do our best, no guarantee!)_
- We will release MUI v4 stable during the React Europe conference.
- We will start an effort to support more components. So far, we have identified a couple of useful ones:
- Layout
- Combobox
- Slider (& range)
- Dropdown
- Tree view
- Dropzone / Upload
- Skeleton
- Jumbotron
- Carousel
- Rating
- Timeline
- Something big 🌈
- ❓ Please upvote our [GitHub issues](https://github.com/mui/material-ui/issues) if you want something specific. The number of 👍 helps us to prioritize.
| 4,140 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/blog/august-2019-update.js | import * as React from 'react';
import TopLayoutBlog from 'docs/src/modules/components/TopLayoutBlog';
import { docs } from './august-2019-update.md?@mui/markdown';
export default function Page() {
return <TopLayoutBlog docs={docs} />;
}
| 4,141 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/blog/august-2019-update.md | ---
title: August 2019 Update
description: Here are the most significant improvements in August.
date: 2019-09-07T00:00:00.000Z
authors: ['oliviertassinari']
tags: ['Company']
---
Here are the most significant improvements in August:
- ✨ We have introduced [a search page](/material-ui/material-icons/) that makes it easy to find the perfect Material Design icon:
Developers spend a lot of time finding the right icons for each context. We have seen an opportunity to make it simpler. We keep a close eye on the "no results" search event to improve our synonyms list.
At the same time, the list of icons has grown. You can find 10 new brand icons and 61 new official material icons.
- 🦴 We have introduced a new [Skeleton component](/material-ui/react-skeleton/) in the lab.
- ⚛️ We have started to move the description of the props to the TypeScript definitions of the components.
- 🎨 We have worked on seeding https://mui.com/store/.
- 📖 We have updated our ROADMAP. [Check it out](/material-ui/discover-more/roadmap/).
But this summary is just scratching the surface. We have accepted 193 commits from 74 different contributors. We have changed 5,875 files with 35,101 additions and 14,701 deletions.
## Our roadmap intent for September
_(We'll do our best, no guarantee!)_
- 🔍 We will keep working on providing ready-to-use autocomplete, combo box, and multi-select components. We announced it last month but have made little progress so far due to focusing on fixing bugs in existing components. Let's make it happen!
- ❓ Please upvote our [GitHub issues](https://github.com/mui/material-ui/issues) if you want something specific. The number of 👍 helps us to prioritize.
| 4,142 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/blog/benny-joo-joining.js | import * as React from 'react';
import TopLayoutBlog from 'docs/src/modules/components/TopLayoutBlog';
import { docs } from './benny-joo-joining.md?@mui/markdown';
export default function Page() {
return <TopLayoutBlog docs={docs} />;
}
| 4,143 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/blog/benny-joo-joining.md | ---
title: Benny Joo joins MUI
description: We are excited to share that Benny Joo has joined MUI. He has started last month full-time and is now a Junior Software Engineer in the Core team.
date: 2021-11-16T00:00:00.000Z
authors: ['mnajdova']
tags: ['Company']
---
We are excited to share that [Benny Joo](https://github.com/hbjORbj) has joined MUI.
He has started last month full-time and is now part of the Core team.
Before joining full-time, Benny was our first intern during the summer.
He joined us right after graduating from The University of Edinburgh.
He had a great start with his internship, implementing the [Masonry component](https://mui.com/material-ui/react-masonry/)! It was one of the [most upvoted issues](https://github.com/mui/material-ui/issues/17000) that we simply didn't have the bandwidth to work on.
As part of the Core team, he will help with the community support, as well as work on some of the new features we plan for the community version of the library, like the unstyled components and the second design system.
I am excited to see what other valuable contributions he will make in the future.
The Core team will continue developing the foundations on which to build great design systems. Here's a quick view of [the community roadmap](https://github.com/orgs/mui/projects/18/views/1).
We couldn't be more excited to have Benny on the team!
| 4,144 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/blog/build-layouts-faster-with-grid-v2.js | import * as React from 'react';
import TopLayoutBlog from 'docs/src/modules/components/TopLayoutBlog';
import { docs } from './build-layouts-faster-with-grid-v2.md?@mui/markdown';
export default function Page() {
return <TopLayoutBlog docs={docs} />;
}
| 4,145 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/blog/build-layouts-faster-with-grid-v2.md | ---
title: Build layouts faster with the new Grid component
description: The new Grid v2 features simplified logic, support for offsetting and nested grids, and more.
date: 2022-08-20T00:00:00.000Z
authors: ['siriwatknp']
tags: ['MUI Core', 'News']
card: true
---
You can now use the new `Grid` component, shipped with [Material UI v5.9.0](https://github.com/mui/material-ui/releases/tag/v5.9.0), for updated features and a better developer experience when building layouts.
```js
import Grid from '@mui/material/Grid'; // The current grid, a.k.a. Grid v1
import Grid from '@mui/material/Unstable_Grid2'; // The new grid, a.k.a. Grid v2
```
## The motivation
- To fix the migration pain points ([#26266](https://github.com/mui/material-ui/issues/29266) and [#31244](https://github.com/mui/material-ui/issues/31244)) for the grid component which is caused by the [implementation changes](https://github.com/mui/material-ui/pull/24332) introduced in v5.
- To add the long-awaited [offset feature](https://github.com/mui/material-ui/issues/11251) to the layout grid component.
- To remove the child combinator (`>`) from the grid item styles, which [complicates the customization](https://github.com/mui/material-ui/issues/28855) of the old grid.
- To fix [the limitation on nested grids](https://mui.com/material-ui/react-grid/#nested-grid).
- To eliminate the unnecessary `item` prop.
## What's new
For v2, the `Grid` component has been rewritten from scratch using CSS variables and `calc()`, which help address many of the issues listed above.
### 💥 Breaking change
The negative margin in the new `Grid` spreads equally on all sides by default.
This is the same as the `Grid` in Material UI v4.
:::info
We believe that the migration from Grid v1 to v2 will be smooth for most users.
To get started right away, head over to the [Grid v2 migration guide](/material-ui/migration/migration-grid-v2/).
:::
### 🚀 New features
#### [Disable the scrollbar](/material-ui/react-grid2/#disable-the-scrollbar)
A new prop called `disableEqualOverflow` solves the problem of an unwanted scrollbar appearing on small viewports.
#### [Offset](/material-ui/react-grid2/#offset)
We have added the long-awaited offset feature to v2 of the `Grid`.
Thanks to CSS variables, we're able to implement this feature with just a few lines of code.
### ✨ Improvements
#### Simplifying logic
Some parts of the layout calculation are delegated to CSS by using CSS variables and `calc()`.
Taken together, they significantly reduce the need for JavaScript and make the component scalable.
The `Grid` v1 calculates the width by reading the value from the React context.
With CSS variables in place, we can remove the React context entirely and hand over the work to CSS instead:
```js
{
// --Grid-columns is defined in the grid container
width: `calc(100% * ${value} / var(--Grid-columns))`,
}
```
In v1 of the `Grid`, grid items have no information about the padding they should have, because the `spacing` prop is defined on the grid container.
So the simplest way to control the padding is to use the CSS child combinator `>` on the container:
```js
function getOffset(val) {
const parse = parseFloat(val);
return `${parse}${String(val).replace(String(parse), '') || 'px'}`;
}
// ...The code is shorten for readability
({
[`& > .${gridClasses.item}`]: {
// Grid item's padding is controlled by its container
paddingTop: getOffset(themeSpacing),
},
});
```
In v2, the communication between the grid container and its items happens via CSS instead of JavaScript, so that the logic behind these components is better separated.
- The grid container takes care of generating variables based on the `spacing` prop:
```js
// The code is simplified for readability
{
'--Grid-rowSpacing': spacingProp,
'--Grid-columnSpacing': spacingProp,
}
```
- The grid item then makes references to those variables:
```js
{
padding: `calc(var(--Grid-rowSpacing) / 2) calc(var(--Grid-columnSpacing) / 2)`,
}
```
This is a very good use case for applying CSS variables when it comes to components that have a parent-child relationship and also support media query customization.
#### Remove unnecessary props
In v2, `Grid` is always an item—similar to the Flexbox item in CSS—so the `item` prop is no longer needed.
The new `Grid` automatically handles the sizing of truncated text that's too long for its container, so we've also removed the `zeroMinWidth` prop since it's no longer needed:
```diff
<Grid container spacing={2}>
- <Grid item zeroMinWidth><Typography>Long text...</Typography></Grid>
+ <Grid><Typography>Long text...</Typography></Grid>
</Grid>
```
#### Nested grid
With the addition of CSS variables and the removal of the `item` prop, there are no more limitations when it comes to creating nested grids.
As a bonus, a grid container automatically inherits row and column spacing values from the root grid container, unless they are specified directly on the component.
```js
import Grid from '@mui/material/Unstable_Grid2';
// root grid container
<Grid container spacing={2}>
<Grid>...</Grid>
<Grid container>
{/* inherits spacing from the root container */}
<Grid>...</Grid>
<Grid>...</Grid>
</Grid>
<Grid>...</Grid>
</Grid>;
```
## Future plan and migration
Since the `Grid` has been rewritten from scratch for v2, it is currently considered _unstable_ as we give the community time to try it out and offer feedback.
We will make it stable and deprecate v1 in the next major release of Material UI.
Ready to make the jump?
Check out the [Grid v2 documentation](/material-ui/react-grid2/) and the [Grid v2 migration guide](/material-ui/migration/migration-grid-v2/).
<hr />
That's it for today! Happy coding 👨💻👩💻!.
I hope this new Grid implementation will make your life easier. Don't forget to share this update with your friends and colleagues.
To get more updates like this in the future, **subscribe to our newsletter** at the bottom of this page.
| 4,146 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/blog/callback-support-in-style-overrides.js | import * as React from 'react';
import TopLayoutBlog from 'docs/src/modules/components/TopLayoutBlog';
import { docs } from './callback-support-in-style-overrides.md?@mui/markdown';
export default function Page() {
return <TopLayoutBlog docs={docs} />;
}
| 4,147 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/blog/callback-support-in-style-overrides.md | ---
title: Introducing callback support in style overrides
description: We're excited to introduce callback support for global theme overrides in this minor version update!
date: 2022-01-31T00:00:00.000Z
authors: ['siriwatknp']
tags: ['MUI Core', 'News']
card: false
---
<span class="x x-first x-last">[</span>MUI Core v5.3.0](https://github.com/mui/material-ui/releases/tag/v5.3.0) introduces the ability to write a callback in style overrides (global theming), giving you full control of component customization at the theme level.
Why is using a callback better than the existing plain object? Let me explain from the beginning<span class="x x-first x-last">…</span>
## The problems
In v4, the style engine library was JSS which had some limitations.
Style overrides were not able to support dynamic props via a callback so we relied on using classes. Take a look at the [`Chip` classes](https://github.com/mui/material-ui/blob/97d32b0ff3fae4537c20c79e619f132f4a5c5cbb/packages/mui-material/src/Chip/chipClasses.ts) for example – there are more than 20 classes that are incomplete if we count the permutation of elements (`root | avatar | icon | label | deleteIcon`), size (`small | medium | large`), and color (`primary | secondary | ...`).
This leads to a poor theming experience because developers need to know which specific key to customize.
We believe it would be better for developers if they could create custom styles by reading the component props, without ever needing to know what key they should use.
Fortunately, it is now possible in v5 because of the new style engine powered by emotion. Theming is simpler and more flexible. You only need to know the component's slot name and then provide an **object** (static overrides) or a **callback** (dynamic overrides).
## Using callback in `styleOverrides`
The callback gives you the `props` that the slot received. Most of the time you would use:
- `props.ownerState`: the combination of runtime props and internal states.
- `props.theme`: the theme object you provided to `ThemeProvider`, or the default one.
```jsx
import { ThemeProvider, createTheme } from '@mui/material/styles';
<ThemeProvider
theme={createTheme({
components: {
MuiChip: {
styleOverrides: {
// you can now use the theme without creating the initial theme!
root: ({ ownerState, theme }) => ({
padding: {
small: '8px 4px',
medium: '12px 6px',
large: '16px 8px',
}[ownerState.size],
...(ownerState.variant === 'outlined' && {
borderWidth: '2px',
...(ownerState.variant === 'primary' && {
borderColor: theme.palette.primary.light,
}),
}),
}),
label: {
padding: 0,
},
},
},
},
})}
>
...your app
</ThemeProvider>;
```
> 💡 The side benefit of using a callback is that you can use the runtime theme without creating the outer scoped variable.
### TypeScript
The callback is type-safe.
- `ownerState`: `ComponentProps` interface, e.g. `ButtonProps`, `ChipProps`, etc.
- `theme`: `Theme` interface from `@mui/material/styles`.
```tsx
{
MuiChip: {
styleOverrides: {
// ownerState: ChipProps
// theme: Theme
root: ({ ownerState, theme }) => ({...}),
},
}
}
```
If you extend the interface via module augmentation like this:
```ts
declare module '@mui/material/Button' {
interface ButtonPropsVariantOverrides {
dashed: true;
}
}
```
you will be able to see those props in `ownerState.variant` 🎉. `theme` can be augmented as well.
## Experimental `sx` function
Initially, `sx` was designed to be a prop that enables you to inject styles with a shorthand notation to components created with the `styled` API:
```jsx
import { styled } from '@mui/material/styles';
import Box from '@mui/material/Box';
const Label = styled('span')({
fontWeight: 'bold',
fontSize: '0.875rem',
})
<Box sx={{ display: 'flex' }}>
<Label sx={{ color: 'text.secondary' }}>Label</Label>
</Box>;
```
> 💡 All MUI components are created with the `styled` API, so they accept `sx` prop by default.
`sx` helps developers write less code and be more productive once they are familiar with the API. With the callback support in `styleOverrides`, it is now possible to use an `sx`-like syntax in global theme overrides.
All you need is to use the [`unstable_sx`](/system/styled/#how-can-i-use-the-sx-syntax-with-the-styled-utility) function from the `theme`. In the following example, the `sx` is used to style the `Chip` component:
```jsx
import { ThemeProvider, createTheme } from '@mui/material/styles';
<ThemeProvider
theme={createTheme({
components: {
MuiChip: {
styleOverrides: {
root: ({ theme }) =>
theme.unstable_sx({
px: '12px', // shorthand for padding-left & right
py: '6px', // shorthand for padding-top & bottom
fontWeight: 500,
borderRadius: '8px',
}),
label: {
padding: 0,
},
},
},
},
})}
>
...your app
</ThemeProvider>;
```
If I want to add more styles based on these conditions:
- border color `palette.text.secondary` is applied when `<Chip variant="outlined" />`.
- font size is `0.875rem` in mobile viewport, `0.75rem` in larger than mobile viewport when `<Chip size="small" />`.
An array can be used as a return type to make the code easier to add/remove conditions:
```js
// The <ThemeProvider> is omitted for readability.
{
root: ({ ownerState, theme }) => [
theme.unstable_sx({
px: '12px',
py: '6px',
fontWeight: 500,
borderRadius: '8px',
}),
ownerState.variant === 'outlined' && ownerState.color === 'default' &&
theme.unstable_sx({
borderColor: 'text.secondary',
}),
ownerState.size === 'small' &&
theme.unstable_sx({
fontSize: { xs: '0.875rem', sm: '0.75rem' },
})
],
}
```
<hr />
**That's it for today!** Happy styling 💅.
I hope this small update makes your customization experience better than ever. Don't forget to share this update with your friends and colleagues.
To get more updates like this in the future, **subscribe to our newsletter** at the bottom of this page.
## Read more
- [Component theming](/material-ui/customization/theme-components/)
- [All supported shorthands in `sx`](/system/getting-started/the-sx-prop/#theme-aware-properties)
- [`sx` performance tradeoff](/system/getting-started/usage/#performance-tradeoffs)
- [`sx` with `styled`](/system/styled/#difference-with-the-sx-prop)
| 4,148 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/blog/danail-hadjiatanasov-joining.js | import * as React from 'react';
import TopLayoutBlog from 'docs/src/modules/components/TopLayoutBlog';
import { docs } from './danail-hadjiatanasov-joining.md?@mui/markdown';
export default function Page() {
return <TopLayoutBlog docs={docs} />;
}
| 4,149 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/blog/danail-hadjiatanasov-joining.md | ---
title: Danail Hadjiatanasov joins MUI
description: We are excited to share that Danail Hadjiatanasov has joined MUI as part of the enterprise team. This was his first full-time week.
date: 2020-10-23T00:00:00.000Z
authors: ['oliviertassinari']
card: true
tags: ['Company']
---
We are excited to share that [Danail Hadjiatanasov](https://twitter.com/danail_h) has joined MUI as part of the enterprise team. This was his first full-time week.
For the past 3 years Danail has been working in a company called [Backbase](https://www.backbase.com/) where he was responsible for building a UI library based on Angular that was specifically designed for banks. The UI library and its corresponding design system were sold under a commercial license, and today some of the biggest names in the banking industry have web applications powered by those UI components (RBC, Central 1, Deutsche Bank, BNP Paribas, and others).
Although he was working with Angular, his true passion is React, having hacked side projects with it. Now he will be able to combine these two talents, and help take MUI X to the next level!
Danail has already landed his first feature in the data grid: [column reordering](https://mui.com/x/react-data-grid/columns/#column-reorder):
<video autoplay muted loop playsinline style="margin-bottom: 24px;">
<source src="/static/blog/danail-hadjiatanasov-joining/reorder.mp4" type="video/mp4" />
</video>
He's now actively working on new features for the data grid.
The enterprise team will continue developing the data grid component, and progressively extend to new advanced components as we grow the team. Here's a quick view of [the enterprise roadmap](https://github.com/mui/mui-x/projects/1).
We couldn't be more excited to have Danail on the team! You can follow him on [Twitter](https://twitter.com/danail_h).
| 4,150 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/blog/danilo-leal-joining.js | import * as React from 'react';
import TopLayoutBlog from 'docs/src/modules/components/TopLayoutBlog';
import { docs } from './danilo-leal-joining.md?@mui/markdown';
export default function Page() {
return <TopLayoutBlog docs={docs} />;
}
| 4,151 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/blog/danilo-leal-joining.md | ---
title: Danilo Leal joins MUI
description: We are excited to share that Danilo Leal has joined MUI.
date: 2021-07-15T00:00:00.000Z
authors: ['oliviertassinari']
card: true
tags: ['Company']
---
We are excited to share that [Danilo Leal](https://daniloleal.co/) has joined MUI!
He started a couple of days ago as a Lead Designer.
Before joining MUI, he worked as a designer at Loggi, a Brazilian logistics unicorn.
He has spent the last five years diving into product design, product strategy, and design systems.
Danilo strongly believes that code is a fundamental piece of a designer's work. It is, after all, the real medium through where users experience the product.
For instance, one of his continuous contributions to Loggi was deep-diving into MUI's codebase to fulfill Loggi's customization needs.
His aspirations are well aligned with where we want to push the company in the long term.
He wants to challenge the status quo.
He wants to push the envelope around how products are built.
We believe there are two high potential opportunities to explore: 1. how designers and developers collaborate, 2. how accessible is creating custom UIs.
His design [challenge assignment](https://www.figma.com/file/UPgXH2mdWqV8QzAuN5VM37/Danilo-assignment) (done under a few hours) gave us confidence that Danilo is exactly who the role needs.
While we can't predict the future, he's initially leading the design rebranding effort.
Then, he will likely focus on a [second design system](https://github.com/mui/material-ui/issues/22485).
We couldn't be more excited to have Danilo on the team! He's the first designer to join us, ever.
A focus area with high potential 🌈 and that we have underinvested in for too long.
See the other areas we want to invest in: we are [hiring](/careers/#open-roles).
| 4,152 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/blog/date-pickers-stable-v5.js | import * as React from 'react';
import TopLayoutBlog from 'docs/src/modules/components/TopLayoutBlog';
import { docs } from './date-pickers-stable-v5.md?@mui/markdown';
export default function Page() {
return <TopLayoutBlog docs={docs} />;
}
| 4,153 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/blog/date-pickers-stable-v5.md | ---
title: The MUI X Date and Time Pickers get a stable v5 release
description: Migrate to the latest version for improved DX, customizability, and API consistency.
date: 2022-09-19T00:00:00.000Z
authors: ['alexfauquette', 'josefreitas']
tags: ['MUI X', 'News']
card: true
---
About four months ago, we moved the date and time pickers from `@mui/lab` and released the first alpha version of the date pickers package.
We have focused on improving stability and developer experience since then, and now, we're happy to announce the first official `@mui/x-date-pickers` [v5 release](https://github.com/mui/mui-x/releases/tag/v5.17.0).
## TL;DR
- The beta phase is over. You can now download `v5.0.0`.
- Dozens of bugs have been fixed since the first alpha.
- DX and overall API consistency have been improved.
- Improved customizability.
- Follow the [installation instructions](https://mui.com/x/react-date-pickers/getting-started/) and the [migration guide](https://mui.com/x/migration/migration-pickers-lab/).
## What's changed?
### Documentation
We revamped the [getting started](https://mui.com/x/react-date-pickers/getting-started/) page to ease the burden with installation, and improved sections that are key to customization, like the documentation of component [slots](https://mui.com/x/react-date-pickers/custom-components/).
### Bug fixes and other issues
More than 150 issues were solved during the pre-releases (alpha/beta), including the epic [refactoring of the date/time selection behavior](https://github.com/mui/mui-x/pull/4408), which has clarified edge cases about how a date is selected, accepted, dismissed, and which callbacks are triggered when.
A big thanks to all the contributors who took the time to clarify the edge cases they faced. It's been a huge help in refining the components behavior.
<img src="/static/blog/date-pickers-stable-v5/monkeyuser-237-fov.png" style="width: 796px; margin-top: 16px; margin-bottom: 8px; aspect-ratio: 112/59;" loading="lazy" alt="Bug illustration from monkeyuser.com" />
### Better APIs and improved customization
The property names and customization strategies were standardized to flatten the learning curve.
For example, the `MonthPicker`'s prop `onMonthChange` and the `YearPicker`'s prop `onYearChange` have both been renamed to `onChange`.
We also added new customizable slots:
- `ActionBar` lets you customize the actions below the picker. It replaces the props `clearable`, `showTodayButton`, `cancelText`, `okText`
- `PaperContent` lets you add custom elements in the desktop view
- `Tabs` lets you customize the tab used to switch between date and time view
### Integrated localization
It's not obvious at first glance, but the pickers do contain some textual information, including action buttons as well as aria-labels for accessibility support.
We integrated a [new localization](https://mui.com/x/react-date-pickers/localization/#translation-keys) pipeline similar to the one used by the Data Grid.
It lets you import translations directly into the main theme in a few lines.
And thanks to the amazing contributors, translations for 11 languages are already available.
```jsx
import { createTheme, ThemeProvider } from '@mui/material/styles';
import { DataGrid, bgBG as dataGridBgBG } from '@mui/x-data-grid';
import { bgBG as coreBgBG } from '@mui/material/locale';
import bgLocale from 'date-fns/locale/bg';
import { CalendarPicker, LocalizationProvider, bgBG } from '@mui/x-date-pickers';
import { AdapterDayjs } from '@mui/x-date-pickers/AdapterDayjs';
const theme = createTheme(
{
palette: {
primary: { main: '#1976d2' },
},
},
bgBG, // x-date-pickers translations
dataGridBgBG, // x-data-grid translations
coreBgBG, // core translations
);
```
## Community migration
With all those changes, we wondered if the community has been interested in the new versions.
According to npm download data, less than 40% of the community still uses the versions in `@mui/lab` (alpha.0 and alpha.1).
So a significant share has already migrated.
And the adoption speed across versions is very encouraging.
Over 40% of users are already using the beta versions.
<img src="/static/blog/date-pickers-stable-v5/date-picker-versions.png" style="width: 796px; margin-top: 16px; aspect-ratio: 168/89;" loading="lazy" alt="Evolution of downloaded version of @mui/x-data-pickers" />
<p class="blog-description">Relative distribution of `@mui/x-date-pickers` versions between June and August.</p>
## Installation and migration from `@mui/lab`
You can find the installation instructions in our [getting started](https://mui.com/x/react-date-pickers/getting-started/) page.
If you are migrating from the `@mui/lab` package, we've prepared a [migration guide](https://mui.com/x/migration/migration-pickers-lab/) to support you, including a codemod to replace the date pickers declarations.
## What to expect next?
After working on stability and developer experience, we're now pushing to improve the usability of the components.
We've been exploring different approaches and implementations for the date fields, and we'll soon release a v6 alpha version to start iterating on the new and improved components.
You can expect support for v5 stable release with patches for critical bugs, but we encourage the community to help us build the next generation of date pickers and migrate whenever possible to the v6 pre-releases.
If you want to help steer the direction of the new components, please consider [contacting us](https://forms.gle/vsBv6CLPz9h57xg8A) to schedule a 30-minute user interview session. We're working on MUI X v6, and we'd love to hear more about your pain points and use cases.
| 4,154 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/blog/december-2019-update.js | import * as React from 'react';
import TopLayoutBlog from 'docs/src/modules/components/TopLayoutBlog';
import { docs } from './december-2019-update.md?@mui/markdown';
export default function Page() {
return <TopLayoutBlog docs={docs} />;
}
| 4,155 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/blog/december-2019-update.md | ---
title: December 2019 Update
description: Here are the most significant improvements in December.
date: 2020-01-07T00:00:00.000Z
authors: ['oliviertassinari']
tags: ['Company']
---
Here are the most significant improvements in December:
- 🚨 We have introduced a new [Alert](https://v4.mui.com/components/alert/) component in the lab, thanks to **[@dimitropoulos](https://github.com/dimitropoulos)** ([#18702](https://github.com/mui/material-ui/pull/18702)). The component also supports composition with a [Snackbar](https://v4.mui.com/components/snackbars/#customized-snackbars).
<p class="blog-description">Standard variant</p>
<p class="blog-description">Filled variant</p>
- 👤 We have added [stacking](https://v4.mui.com/components/avatars/#grouped) support to the avatar.
- ↕️ We have added [vertical](https://v4.mui.com/components/button-group/#vertical-group) support to the button group.
- 🌎 We have almost doubled the number of supported [locales](https://v4.mui.com/guides/localization/#supported-locales) from 13 to 22, thanks to our awesome contributors. Help us double this number next month 🚀!
But this summary is just scratching the surface. We have accepted 168 commits from 73 different contributors. We have changed 1,059 files with 13,468 additions and 8,584 deletions.
## Our roadmap intent for January
_(We'll do our best, no guarantee!)_
- 💄 We will keep working on a new [pagination](https://github.com/mui/material-ui/pull/19049) component. You can already [preview it](https://deploy-preview-19049--material-ui.netlify.app/components/pagination/) (lead by **[@mbrookes](https://github.com/mbrookes)**).
- 📅 We will keep working on a major upgrade of the [date/time picker](https://github.com/mui/material-ui-pickers/issues/1293) components. We are working on desktop and range support (lead by **[@dmtrKovalenko](https://github.com/dmtrKovalenko)**).
- 🧮 We will keep working on a new [data grid](https://github.com/mui/material-ui/pull/18872) component. You can already [preview it](https://deploy-preview-18872--material-ui.netlify.app/components/data-grid/) (lead by **[@oliviertassinari](https://github.com/oliviertassinari)**).
❓ Please upvote our [GitHub issues](https://github.com/mui/material-ui/issues) if you want something specific. The number of 👍 helps us to prioritize.
| 4,156 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/blog/discord-announcement.js | import * as React from 'react';
import TopLayoutBlog from 'docs/src/modules/components/TopLayoutBlog';
import { docs } from './discord-announcement.md?@mui/markdown';
export default function Page() {
return <TopLayoutBlog docs={docs} />;
}
| 4,157 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/blog/discord-announcement.md | ---
title: 'MUI is now on Discord!'
description: Come join our community to engage in lively discussions, share your projects, and interact with the MUI team.
date: 2023-08-02T00:00:00.000Z
authors: ['richbustos']
tags: ['News']
card: true
---
<a href="https://mui.com/r/discord/"><img src="/static/blog/discord-announcement/discord.png" width="1280" height="640" style="margin-bottom: 16px;" alt="Discord banner with link" /></a>
This year, one of our highest priorities has been to create a central hub for the MUI community.
Up until now, our community has been scattered across discussions and interactions on [Twitter](https://twitter.com/MUI_hq), [LinkedIn](https://linkedin.com/company/mui), [GitHub](https://github.com/mui), and [Stack Overflow](https://stackoverflow.com/questions/tagged/material-ui).
That's why we've officially launched our [Discord Server](https://mui.com/r/discord/)—and we'd love for you to be a part of our community!
Come join to engage in lively discussions, share your projects, and interact with the MUI team as well as developers just like you from all around the world.
## Why you should join our Discord Server?
There are a plethora of reasons why you should join, but here are the three biggest benefits:
1. **Real-time communication with our community**:
As mentioned above, our communication with the community has often been slow and _scattered_ across too many different platforms.
Developers are frequently unsure whether to open an issue on GitHub, tweet at us, or send us an email when they have a question or want to share feedback.
_Discord provides real-time chat capabilities_, allowing you to communicate and collaborate with us and other developers, instantly.
What's a better way to get a real-time response from the MUI team and other users?!
2. **Community building**:
Discord is a great place for us to get together and chat!
For so long, there wasn't a way for us to get together.
We have big plans to set up events such as hack-a-thons, monthly office hours with our Developer Advocates, speaking events with MUI founders, and the list goes on.
3. **Networking and collaboration opportunities**:
We want this to be a safe place where you can join, have fun, and meet new people.
Someone is out there using this same tool as you.
We created two awesome channels to help you find work opportunities (and we can always create more—just let us know what you need)!
1. 🎨 │ Show-Off
- Show off your MUI projects! Get wild. Ask questions.
Or use this channel simply to boast. 😉
2. 📝 │ Freelance
- Looking for some help on completing your vision?
Use this channel to find work or market yourself for work.
There are thousands of developers, designers, and teams using MUI.
You're bound to find someone to help you complete your project.
## Chat with you soon
Overall, we're super excited to have you join our community.
Come show off your projects, introduce yourself in the **"👋 | new-members"** channel, or just ask general questions in the forums.
As always, we would love to hear from you.
**See you on our [Discord Server](https://mui.com/r/discord/)!**
| 4,158 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/blog/docs-restructure-2022.js | import * as React from 'react';
import TopLayoutBlog from 'docs/src/modules/components/TopLayoutBlog';
import { docs } from './docs-restructure-2022.md?@mui/markdown';
export default function Page() {
return <TopLayoutBlog docs={docs} />;
}
| 4,159 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/blog/docs-restructure-2022.md | ---
title: 'Our docs just got a major upgrade—here's what that means for you'
description: Each of MUI's products now has its own dedicated documentation, making it easier than ever to find exactly what you need.
date: 2022-04-06T00:00:00.000Z
authors: ['danilo-leal']
tags: ['News', 'Product']
card: true
---
As MUI continues to grow beyond our flagship product, Material UI (we [rebranded the company](/blog/material-ui-is-now-mui/) last year as a first step), it has become clear that the documentation for our products can no longer all live under one roof.
That's why we're excited to announce that we are shipping a major upgrade to our documentation, to make it easier than ever to find exactly what you need—no matter which MUI products you're working with.
## Wait… what MUI products are you talking about?
We currently offer two main product lines:
- **MUI Core**—a collection of foundational component libraries, including:
- _Material UI_ —components that implement Google's Material Design
- _Base UI_ —unstyled components for implementing your own design system
- _MUI System_ —CSS utilities for quickly laying out design systems
- **MUI X**—a collection of advanced components for complex use cases, including:
- _Data grid_ —fast, feature-rich, extendable React data table
- _Date and Time pickers_ —interface control components for selecting dates and times
## What has changed?
All MUI products still live under the [mui.com](https://mui.com) domain, but each of them now has its own respective URL and documentation.
We added an identifier and menu to the upper-left corner of the docs for improved navigation:
<img src="/static/blog/docs-restructure-2022/docs-separation.png" style="width: 796px; margin-top: 16px; margin-bottom: 16px;" alt="Screenshot of the product identifier menu" />
As for the URLs, this is how they look now:
- MUI Core:
- Material UI: [https://mui.com/material-ui/](https://mui.com/material-ui/getting-started/)
- Base UI: [https://mui.com/base-ui/](https://mui.com/base-ui/getting-started/)
- MUI System: [https://mui.com/system/](https://mui.com/system/getting-started/)
- MUI X:
- Data grid: [https://mui.com/x/react-data-grid/](https://mui.com/x/react-data-grid/)
- Date and Time pickers: [https://mui.com/x/react-date-pickers/](https://mui.com/x/react-date-pickers/getting-started/)
> 📖 The date and time pickers have been promoted from the lab (`@mui/lab`) to MUI X—still available under the MIT license. To learn more, check out the [blog post about the newest MUI X components](/blog/lab-date-pickers-to-mui-x/).
### Improved search experience
The documentation restructuring ranks search results based on the product that you are currently looking at.
For example, if you are looking at Material UI documentation, when you press <kbd><kbd class="key">⌘</kbd>+<kbd class="key">K</kbd></kbd> (or <kbd><kbd class="key">Ctrl</kbd>+<kbd class="key">K</kbd></kbd> on Windows) and type a keyword, you will find that most of the results are related to Material UI.
We have also added product labels for Material UI and Base UI in case it's unclear which library the search results refer to.
<img src="/static/blog/docs-restructure-2022/docs-product-label.png" style="width: 796px; margin-top: 16px; margin-bottom: 16px;" alt="Screenshot of the search results displaying product labels per result" />
As a side benefit of the documentation restructuring, we have seen a huge improvement in the quality of search results related to MUI X. Data Grid users can now see comprehensive results when searching for features. Previously a search for pagination returned results for the Material UI pagination component, followed by those for the data grid:
<img src="/static/blog/docs-restructure-2022/docs-search-before.png" style="width: 796px; margin-top: 16px; margin-bottom: 16px;" alt="Screenshot of search results for pagination before the documentation restructuring, returning at first results for the Material UI pagination component followed by those for the data grid" />
Now when viewing the MUI X section, only results related to the data grid pagination feature are returned:
<img src="/static/blog/docs-restructure-2022/docs-search-after.png" style="width: 796px; margin-top: 16px; margin-bottom: 16px;" alt="Screenshot of search results for pagination after the documentation restructuring. Now when viewing the MUI X section, only results related to the data grid pagination feature are returned." />
## Moving forward
This separation will become increasingly beneficial as each product grows, such as additional components in MUI X and Base UI.
As we move forward working on [our second design system package](https://deploy-preview-30686--material-ui.netlify.app/experiments/), the separation will make it possible for us to build the documentation for each system using its default styles—so the docs themselves will serve as examples of their corresponding component libraries.
If you have any feedback or suggestions, we definitely want to hear from you.
Please open an issue in the [mui/material-ui repository on GitHub](https://github.com/mui/material-ui/issues), and be sure to start the **Title** with [docs].
Happy developing! 👩💻
| 4,160 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/blog/first-look-at-joy.js | import * as React from 'react';
import TopLayoutBlog from 'docs/src/modules/components/TopLayoutBlog';
import { docs } from './first-look-at-joy.md?@mui/markdown';
export default function Page() {
return <TopLayoutBlog docs={docs} />;
}
| 4,161 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/blog/first-look-at-joy.md | ---
title: First look at Joy UI 🥳
description: A sneak peek at MUI's new starting point for your design system.
date: 2022-06-08T00:00:00.000Z
authors: ['danilo-leal', 'siriwatknp']
tags: ['News', 'MUI Core']
card: true
---
<a href="/joy-ui/getting-started/"><img src="/static/blog/first-look-at-joy/card.png" style="width: 692px; aspect-ratio: 2/1; margin-bottom: 24px;" alt="First look at Joy UI: a new starting point for your design system." /></a>
If you're a close follower of everything MUI, you might be aware that we've been working on a new design system.
If not, then this post will give you a first look at **Joy UI**－MUI's new starting point for your design system!
If you've ever considered using Material UI because of the developer experience, reliability, and completeness, but hesitated because of the design, this is great news for you.
Joy UI offers all of that, but with a modern look and feel, ease of customization, and lower overhead by not carrying unused Material Design specific code and styling.
## How does Joy UI relate to Material UI?
You might naturally associate MUI with Material UI, which despite the similar names, are separate things.
Material UI is MUI's React implementation of Google's Material Design.
Over time Material UI has established itself as the go-to library for quickly breathing life into products, mostly thanks to its design, customizability, and documentation.
However, the components do come by default with the 2018 Google look and feel that is no longer as popular as it once was.
And as we've confirmed with [our latest developer survey](/blog/2021-developer-survey-results/#what-are-your-most-important-criteria-for-choosing-a-ui-library), design quality is one of the most important elements that developers consider when choosing a UI library.
## Why not just build a new Material UI theme?
One of the main objectives with this new product is to break away from Material Design.
A different theme would still require you and your team to have at least some understanding of how Material Design is structured, and how that is expressed in Material UI.
With Joy, you're able to start with a fresh design by default.
We also had many ideas for improving the experience of developing design systems, so a separate package is an opportunity to prototype and test some of these new features without running the risk of compromising the experience of the thousands of teams that use Material UI today.
Material UI and Joy UI still share many of the same conventions and features.
We've done this not only to decrease the learning curve for adopting Joy UI, but also because we believe that the conventions we've established represent the ideal developer experience for working with design systems.
:::info
Any new DX feature introduced in Joy UI will eventually be reproduced in Material UI, and vice versa.
:::
## What new features does Joy UI offer?
Aside from a fresher look and feel for your upcoming project, here are a few features included in the alpha version of Joy UI:
### Global variants
Instead of defining variants at the component level, Joy UI defines them at the global level.
This sounds bold at first, but the more we experiment the more it starts to make sense.
[Global variants](/joy-ui/main-features/global-variants/) mostly affect three CSS properties: color, background, and border.
What this means is that you're able to switch between the same set of variants in any component, more easily maintaining consistency across your app.
The four variants available in the components are `solid`, `soft`, `outlined`, and `plain`.
<a href="/joy-ui/react-button/#variants"><img src="/static/blog/first-look-at-joy/global-variants.png" style="width: 692px; margin-top: 16px; margin-bottom: 16px;" loading="lazy" alt="Screenshot of button component using all available variants." /></a>
```jsx
<Button variant="solid">
<Button variant="soft">
<Button variant="outlined">
<Button variant="plain">
```
### Automatic adjustment
We meticulously constructed the CSS variables for each component so you can seamlessly compose them with little customization necessary.
One good example is the input component, where the border radius of the input's children automatically adapts to that of the input.
These small details mean the components adapt to different scenarios, which saves considerable time when customizing the components by avoiding manual adjustments.
<img src="/static/blog/first-look-at-joy/component-integration.png" style="width: 692px; margin-top: 16px;" alt="Screenshot of two text inputs, one being native from Joy UI and another with border-radius customized" />
<p class="blog-description">When customizing the input's border radius, the icon button inside of it adapts automatically.</p>
```jsx
<Input
placeholder="password"
endDecorator={<IconButton size="sm"><Visibility /></IconButton>}
/>
<Input
size="lg"
placeholder="password"
endDecorator={<IconButton><Visibility /></IconButton>}
sx={{ '--Input-radius': '24px' }}
/>
```
Joy UI doesn't sacrifice customization in order to have these automatic adjustments.
You're still able to override the style completely via the usual CSS overrides, or even adjust the predefined CSS variables with the `sx` prop.
### Perfect dark mode, for server-side rendering
Joy UI provides an effective way to prevent UI flicker when users refresh or re-enter a page with dark mode enabled.
The out-of-the-box CSS variables support allows every color scheme to be rendered at build time, inserting the selected color scheme and mode before the browser renders the DOM.
What's more, it provides a function called `getInitColorSchemeScript()` that enables you to have perfect functioning dark mode in various React frameworks, such as Next.js, Gatsby, and Remix.
```js
// A Next.js example
import Document, { Html, Head, Main, NextScript } from 'next/document';
import { getInitColorSchemeScript } from '@mui/joy/styles';
export default class MyDocument extends Document {
render() {
return (
<Html data-color-scheme="light">
<Head>...</Head>
<body>
{getInitColorSchemeScript()}
<Main />
<NextScript />
</body>
</Html>
);
}
}
```
### Unlimited color schemes
Beyond light and dark mode toggling, Joy UI lets you provide your users with multiple color schemes.
Within each mode, you'll be able to have as many color schemes as you want－powered by CSS variables.
## When will Joy UI be ready to use?
A significant part of the core infrastructure for Joy UI has already been developed, and we've been working for the last couple of months on adding more components.
The package is already [available from npm](https://www.npmjs.com/package/@mui/joy) but until we get to a reasonable number of components, and with sufficient documentation, it remains an _initial_ work in progress.
It should be ready for more mature experimentation and testing in the second half of 2022.
Meanwhile, we've developed a couple of templates that showcase what Joy UI looks like out of the box, so you can explore it further.
Follow the templates' CodeSandbox or live demo links to experiment with Joy UI for yourself.
:::success
They are also available in the docs [Templates page](/joy-ui/getting-started/templates/).
:::
### Email
<a href="/joy-ui/getting-started/templates/email/"><img src="/static/blog/first-look-at-joy/email.png" style="width: 692px; margin-top: 8px; margin-bottom: 16px;" loading="lazy" alt="Screenshot of an email application mockup built with Joy UI" /></a>
- [Live demo](/joy-ui/getting-started/templates/email/)
- [CodeSandbox](https://codesandbox.io/s/8gtttr?file=/App.tsx)
### File management
<a href="/joy-ui/getting-started/templates/files/"><img src="/static/blog/first-look-at-joy/files.png" style="width: 692px; margin-top: 8px; margin-bottom: 16px;" loading="lazy" alt="Screenshot of file management application mockup built with Joy UI" /></a>
- [Live demo](/joy-ui/getting-started/templates/files/)
- [CodeSandbox](https://codesandbox.io/s/ro2b1t?file=/App.tsx)
### Team management
<a href="/joy-ui/getting-started/templates/team/"><img src="/static/blog/first-look-at-joy/people.png" style="width: 692px; margin-top: 8px; margin-bottom: 16px;" loading="lazy" alt="Screenshot of a team management application mockup built with Joy UI" /></a>
- [Live demo](/joy-ui/getting-started/templates/team/)
- [CodeSandbox](https://codesandbox.io/s/dclgbp?file=/App.tsx)
Joy UI is just getting started and we hope you're as excited as we are－stay tuned for more news in the near future!
Happy developing! 👩💻
| 4,162 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/blog/introducing-base-ui.js | import * as React from 'react';
import TopLayoutBlog from 'docs/src/modules/components/TopLayoutBlog';
import { docs } from './introducing-base-ui.md?@mui/markdown';
export default function Page() {
return <TopLayoutBlog docs={docs} />;
}
| 4,163 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/blog/introducing-base-ui.md | ---
title: 'Introducing Base UI: the headless alternative to Material UI'
description: The Base UI component library gives you complete control over the look and feel of your app.
date: 2022-09-07T00:00:00.000Z
authors: ['michaldudak', 'samuelsycamore']
tags: ['News', 'MUI Core']
card: true
---
<a href="https://mui.com/base-ui/"><img src="/static/blog/introducing-base-ui/hero-image.png" style="width: 692px; aspect-ratio: 132/61; margin-bottom: 24px;" alt="Demo components built with Base UI, a newly introduced library of unstyled components and hooks" /></a>
While Material UI is excellent for building sleek user interfaces that adhere closely to Material Design, it can become unwieldy when your design system diverges significantly from the defaults.
We get it.
We've all been there.
That's why we're building an entirely new library of headless React UI components and hooks called **Base UI**—to give you complete control over the look and feel of your user interface, with no defaults to override.
Base UI is easy to pick up if you're already familiar with Material UI, as the APIs are very similar—indeed, they were designed to be complementary to one another.
Start from scratch with Base UI, or use Material UI for rapid prototyping, and then switch to Base UI when you need more customization options.
## Why Base UI?
Base UI was created to serve a different set of needs than those addressed by Material UI.
Material UI shines at providing you with the means to quickly create user interfaces that look close to the Material Design specification.
Base UI, on the other hand, prioritizes customizability over the speed of development.
This makes it better suited for public-facing projects where pixel-perfect implementation is crucial.
So, why not use any of the headless libraries already present on the market instead?
There are other alternatives like Headless UI, Radix UI, and React Aria, to name a few.
Base UI's significant advantage is that it takes the best parts from Material UI, which is a complete, mature library.
It is free from many of the issues that have been reported and fixed in Material UI.
Also, many of the improvements to Material UI proposed by the community over the years are included in Base UI.
While they were created for different use cases, these two libraries share many common features and design patterns, and are intended to be complementary to one another within the MUI ecosystem.
Base UI's API will be familiar to you if you've used Material UI before, making it easy to migrate a project—or just a part of it—from one library to the other if needed.
We aim to create [unstyled versions of all Material UI components](https://github.com/mui/material-ui/issues/27170) (that make sense to do so).
## Components and hooks
Base UI offers two kinds of building blocks: unstyled components and hooks.
Components are more straightforward to use of the two.
Place a component on a page, add your own styles, and it's ready to go!
It's important to note that you are not limited to the styling options available in Material UI.
You can, of course, still use [MUI System](https://mui.com/system/getting-started/), but if you prefer Emotion, Tailwind CSS, plain CSS, or any other styling engine, they are available too!
Check out the [Working with Tailwind CSS guide](/base-ui/guides/working-with-tailwind-css/) for an example of using this library.
In contrast to Material UI, Base UI's components do not have any default styles.
They provide functionality and structure, while designers and developers are responsible for the visuals.
Each unstyled component lets you modify or override its _slots_—smaller subcomponents representing the interior elements that comprise the component's DOM structure.
For example, a `SwitchUnstyled` contains the root, thumb, input, and track slots.
You can control props passed to each of these slots (including `className`) based on the component's state, and even replace the default slot components with your own.
<img src="/static/blog/introducing-base-ui/switch-slots.png" style="width: 692px; aspect-ratio: 173/80; margin-bottom: 24px;" loading="lazy" alt="Depiction of SwitchUnstyled components' slots" />
See how it works on the live demo:
<iframe src="https://codesandbox.io/embed/mui-base-switch-overview-frsm5f?fontsize=12&hidenavigation=1&module=%2Fsrc%2FMySwitch.tsx&theme=dark"
style="width:100%; height:350px; border:0; border-radius: 10px; overflow:hidden; margin-bottom: 24px"
title="Base UI Switch overview"
sandbox="allow-forms allow-modals allow-popups allow-presentation allow-same-origin allow-scripts"
></iframe>
Hooks take this one step further by extracting the logic from the structure entirely, so you can build from scratch using any DOM elements you need.
This requires more work to implement but gives you the most freedom to customize.
Upon calling, a hook returns an object describing the component's state (i.e., whether the switch is turned on), along with methods that apply accessibility props and event handlers.
You should spread these props on the components you've defined, as shown below:
```tsx
function MySwitch(props: UseSwitchParameters) {
const { getInputProps, checked, disabled } = useSwitch(props);
return (
<span className={clsx('root', { checked, disabled })}>
<span className="thumb" />
<input className="input" {...getInputProps()} />
</span>
);
}
```
## What's included
The initial version of the library contains 17 components.
Check out the [Base UI documentation](/base-ui/getting-started/) for details.
You can track our progress in adding new components—and comment to influence our priorities—in [this dedicated GitHub issue](https://github.com/mui/material-ui/issues/27170).
The @mui/base package is released as an alpha.
This means the component APIs are subject to change—especially as we receive feedback from the community about room for improvement.
However, we believe the library is solid enough at this point to start building design systems with it.
In fact, we're using Base UI to create [Joy UI](/blog/first-look-at-joy/)—the next product we'll be launching in our line of Core component libraries that also includes Material UI.
In the future, Base UI will also be used as the foundation for Material UI components to provide a consistent developer experience across our entire suite of products.
## Feedback needed
Give Base UI a try today by installing the package via npm:
```bash
npm install @mui/base
```
or yarn:
```bash
yarn add @mui/base
```
Check out [the docs](/base-ui/getting-started/), play with the components, and be sure to let us know what you think!
If you find any bugs or want to share ideas for improvements, please don't hesitate to open an issue in the [MUI Core repository on GitHub](https://github.com/mui/material-ui/issues/new/choose).
Be sure to include "[base]" in the issue title to help us keep things organized.
**Happy creating!**
| 4,164 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/blog/introducing-the-row-grouping-feature.js | import * as React from 'react';
import TopLayoutBlog from 'docs/src/modules/components/TopLayoutBlog';
import { docs } from './introducing-the-row-grouping-feature.md?@mui/markdown';
export default function Page() {
return <TopLayoutBlog docs={docs} />;
}
| 4,165 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/blog/introducing-the-row-grouping-feature.md | ---
title: Give your users more freedom with data grid row grouping
description: The new row grouping feature gives your users more customization options for organizing their data.
date: 2022-01-20T00:00:00.000Z
authors: ['alexfauquette']
tags: ['MUI X', 'News']
---
After an incredible year fully focused on improving our data grid component, we are moving forward by launching the first feature of our new Premium plan: [row grouping](/x/react-data-grid/row-grouping/), released in [v5.3.0](https://github.com/mui/mui-x/releases/tag/v5.3.0).
Let's take a closer look at this feature.
## Navigate your data 🚢
If you already use the Pro plan, you may be familiar with the [tree data](/x/react-data-grid/tree-data/) which allows your users to navigate in the hierarchy by opening and closing children of a row.
But not all data has a natural hierarchy, and your users might need to modify the order.
Good news! This is now possible with row grouping.
### Row grouping in action
Consider this sample data of the top 250 movies according to IMDb. Would you group them by director, box office results, or year of release?
The answer depends on what the user wants to do. So give them the freedom to choose!
With the new row grouping feature, you can click on the **Director** column menu and select **Group by Director** to group all the rows with the same director.
When you're ready to return to the default view, click on **Stop Grouping by Director** in the same column menu.
<img src="/static/blog/introducing-the-row-grouping-feature/blog1.gif" alt="grouping and un-grouping by director" style="width: 100%; margin-bottom: 16px;" />
## How to unlock this feature 🔓🎁
The row grouping feature will be part of the Premium plan when it is launched. For now, you can access it on the Pro plan by enabling experimental features.
```js
<DataGridPro experimentalFeatures={{ rowGrouping: true }} {...otherProps} />
```
Note: Row grouping is stable in its current form. The _experimental_ flag is here to make sure that the Pro plan will not have any regression when the feature is eventually moved to the Premium plan.
## How to set the default grouping ⚡️
Save your users time by defining the initial grouping. To do so, specify the row grouping model in the `initialState` prop.
For a page with information about directors, we could group by director and box office as follows:
```js
<DataGridPro
experimentalFeatures={{ rowGrouping: true }}
initialState={{
rowGrouping: {
model: ['Director', 'BoxOffice'],
},
}}
{...otherProps}
/>
```
You can still modify this grouping configuration in the column menus.
But as you can see in the example below, setting the default grouping allows us to hone in on the data we find most interesting, such as the box office results of Hitchcock's films:
<img src="/static/blog/introducing-the-row-grouping-feature/defaultSettings.png" alt="remove groupable option" style="width: 100%; margin-bottom: 16px;" />
## Cherry-pick the groupable columns 🍒
Before letting your users enjoy this new feature, let's adapt it to your use case.
Not all columns will be ideal candidates. Row grouping is most useful when information is repeated in a given column, such as the names of movie directors.
In our example of the top 250 movies, grouping by title does not make sense—each movie has a different name, so there will be no row groups.
You can remove the ability to group a specific column by setting the property `groupable` to `false` in the column definition.
This removes the **Group by** option in the corresponding column menu.
<img src="/static/blog/introducing-the-row-grouping-feature/groupable1.png" alt="remove groupable option" style="width: 100%; margin-bottom: 16px;" />
## Customize grouping behavior 🔧
Some columns are interesting, but don't lend themselves well to grouping.
For example, the release date of a movie is interesting information, but grouping by the exact date leads to one group per movie (except for _The Thing_ and _Blade Runner_, which as we all know were both released on June 25th, 1982 😅).
It is more interesting to group them by decade.
For this purpose, the column definitions accept the property [`groupingValueGetter`](/x/react-data-grid/row-grouping/#using-groupingvaluegetter-for-complex-grouping-value).
Its signature is similar to `valueGetter` and it returns the grouping value associated with the column.
To group our movies by decade, we could use the following:
```js
groupingValueGetter: ({ value }) => `${Math.floor(value.getFullYear() / 10)}0's`;
```
<img src="/static/blog/introducing-the-row-grouping-feature/blog2.gif" alt="grouping by release decade" style="width: 100%; margin-bottom: 16px;" />
## Share your feedback 🗣
We hope you find this new feature useful. Please don't hesitate to open [issues](https://github.com/mui/mui-x/issues/new/choose) to share feedback, report bugs, or propose enhancements.
More details about row grouping customization can be found in the [documentation](/x/react-data-grid/row-grouping/#disable-the-row-grouping).
For more information about our v5.3.0 release, visit the [changelog](https://github.com/mui/mui-x/releases/tag/v5.3.0).
| 4,166 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/blog/july-2019-update.js | import * as React from 'react';
import TopLayoutBlog from 'docs/src/modules/components/TopLayoutBlog';
import { docs } from './july-2019-update.md?@mui/markdown';
export default function Page() {
return <TopLayoutBlog docs={docs} />;
}
| 4,167 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/blog/july-2019-update.md | ---
title: July 2019 Update
description: Here are the most significant improvements in July.
date: 2019-08-04T00:00:00.000Z
authors: ['oliviertassinari']
tags: ['Company']
---
Here are the most significant improvements in July:
- 🌳 We have introduced a new [Tree View component](/x/react-tree-view/) in the lab. Big thanks to Josh for it.
- 💄 We have added support for [vertical tabs](/material-ui/react-tabs/#vertical-tabs).
- ⚛️ We have introduced a codemod that makes it easy to migrate to top-level imports.
Read our [Minimizing Bundle Size](/material-ui/guides/minimizing-bundle-size/) guide to learn how your project should be configured.
```js
import { Button, TextField } from '@mui/material';
```
- ⭐️ We have introduced a new [Rating component](/material-ui/react-rating/) in the lab.
But this summary is just scratching the surface. We have accepted 146 commits from 54 different contributors. We have changed 2,004 files with 29,022 additions and 25,455 deletions.
## Our roadmap intent for August
_(We'll do our best, no guarantee!)_
- 🔍 We will work on providing ready-to-use autocomplete, combo box, and multi-select components.
- 🦴 We will continue to work on a new Skeleton component. You can already [preview it](https://deploy-preview-16786--material-ui.netlify.app/components/skeleton/).
- ❓ Please upvote our [GitHub issues](https://github.com/mui/material-ui/issues) if you want something specific. The number of 👍 helps us to prioritize.
| 4,168 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/blog/june-2019-update.js | import * as React from 'react';
import TopLayoutBlog from 'docs/src/modules/components/TopLayoutBlog';
import { docs } from './june-2019-update.md?@mui/markdown';
export default function Page() {
return <TopLayoutBlog docs={docs} />;
}
| 4,169 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/blog/june-2019-update.md | ---
title: June 2019 Update
description: Here are the most significant improvements in June.
date: 2019-07-08T00:00:00.000Z
authors: ['oliviertassinari']
tags: ['Company']
---
Here are the most significant improvements in June:
- 💄 We have introduced a new [ButtonGroup](/material-ui/react-button-group/) component.
- 💄 The [Slider](/material-ui/react-slider/) component has been overhauled and enhanced with range support. It was also moved from the lab to the core.
- 💄 We have introduced a new [TextareaAutosize](/material-ui/react-textarea-autosize/) component.
<video style="margin-bottom: 24px;" autoplay muted loop playsinline>
<source src="/static/blog/june-2019-update/textarea-autosize.mp4" type="video/mp4" />
</video>
But this summary is just scratching the surface. We have accepted 198 commits from 71 different contributors. We have changed 5,384 files with 26,199 additions and 18,097 deletions.
## Our roadmap intent for July
_(We'll do our best, no guarantee!)_
- We will keep working on a new Tree View component.
You can already [preview it](https://deploy-preview-14827--material-ui.netlify.app/components/tree-view/).
- We will work on a new Rating component.
You can already [preview it](https://deploy-preview-16455--material-ui.netlify.app/components/rating/).
- ❓ Please upvote our [GitHub issues](https://github.com/mui/material-ui/issues) if you want something specific. The number of 👍 helps us to prioritize.
| 4,170 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/blog/lab-date-pickers-to-mui-x.js | import * as React from 'react';
import TopLayoutBlog from 'docs/src/modules/components/TopLayoutBlog';
import { docs } from './lab-date-pickers-to-mui-x.md?@mui/markdown';
export default function Page() {
return <TopLayoutBlog docs={docs} />;
}
| 4,171 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/blog/lab-date-pickers-to-mui-x.md | ---
title: Date and Time Pickers are moving to MUI X
description: Migrate to the new package to start building with our powerful Date and Time Pickers, now part of MUI X. Previously released MIT components will stay MIT.
date: 2022-04-03T00:00:00.000Z
authors: ['flaviendelangle']
tags: ['MUI X', 'News']
card: false
---
After more than 18 months in the lab, the Date and Time Picker components have found a new home as part of MUI X.
This means we'll be dedicating even more time and effort to these complex components, to better meet the needs of both you and your users.
## TL;DR
- The Date and Time Pickers are one step closer to a stable release.
- **No surprise licenses changes**. We are staying true to [our promises](https://mui-org.notion.site/Stewardship-542a2226043d4f4a96dfb429d16cf5bd). What's MIT stays MIT, and we're going forward with our [plan announced over a year ago](https://v5-0-6.mui.com/components/date-range-picker/) to move the date range picker to the commercial license.
- Follow the [migration steps](/x/migration/migration-pickers-lab/)
## What are Date and Time Pickers?
Date and Time Pickers are interface controls that enable the user to select a date (or time) from a menu.
<img src="/static/blog/lab-date-pickers-to-mui-x/date-time-picker.png" style="width: 796px; margin-top: 16px;" alt="Date and Time Picker component" />
<p class="blog-description">Date and Time Pickers using the default Material UI design</p>
Common design patterns include text inputs, dropdown lists, calendars, timelines, and scrolling pickers on mobile devices.
The user may need to select an individual date/time, or a range.
## What is MUI X?
[MUI X](/x/) is a collection of advanced components built for complex use cases.
As opposed to the MUI Core library, which leans on the open-source community for support, MUI X components require several full-time developers dedicated to engineering and ongoing maintenance.
MUI X components are available under two licenses:
- MUI X is MIT licensed, so free to use.
- MUI X Pro includes the most advanced features, and is commercially licensed.
## Why have the Date and Time Pickers been moved to MUI X?
Date and Time Picker UI elements appear simple enough on the surface, but they are surprisingly complicated to engineer.
When the Date and Time Picker components were ready to leave the lab, we had a choice to make: would they live in the MUI Core library, or should they become a part of MUI X?
Given the complex nature of these components, we decided that they would benefit most from the dedicated attention that they would receive from the X team.
And by offering an even more advanced component package through our commercial license, we can continue to grow our team to better serve your needs.
The Date and Time Picker components are now available in two packages:
- `@mui/x-date-pickers` has a [MIT license](https://unpkg.com/browse/@mui/x-date-pickers/LICENSE), it contains all the open-source components
- `@mui/x-date-pickers-pro` has a [commercial license](https://unpkg.com/browse/@mui/x-date-pickers-pro/LICENSE), it contains all the MIT and commercially licensed components
## Which components are only available in the Pro package?
The date range components can only be used with a commercial license.
All other Date and Time Picker components are available in `mui/x-date-pickers` and will remain MIT licensed and free forever.
## How do I purchase a commercial license?
Visit [the MUI Store](https://mui.com/store/items/mui-x-pro/) to purchase a commercial license.
## How do I migrate?
Follow the [migration steps](/x/migration/migration-pickers-lab/) by updating the package name and change from a default export to a named export:
```diff
-import DatePicker from '@mui/lab/DatePicker';
+import { DatePicker } from '@mui/x-date-pickers/DatePicker';
-import DateRangePicker from '@mui/lab/DateRangePicker';
+import { DateRangePicker } from '@mui/x-date-pickers-pro/DateRangePicker';
-import { DatePicker, DateRangePicker } from '@mui/lab';
+import { DatePicker } from '@mui/x-date-pickers';
+import { DateRangePicker } from '@mui/x-date-pickers-pro';
// DatePicker is also available in `@mui/x-date-pickers-pro`
```
We have prepared a codemod to help you migrate your codebase from `@mui/lab` to `@mui/x-date-pickers` or `@mui/x-date-pickers-pro`:
```bash
npx @mui/codemod v5.0.0/date-pickers-moved-to-x <path>
```
## Where is the Date and Time Picker documentation?
You can find the documentation for the picker components in the [MUI X docs](/x/react-date-pickers/getting-started/).
## What's next for the Date and Time Pickers?
For now, `@mui/x-date-pickers` and `@mui/x-date-pickers-pro` are in alpha.
Our next goal is to work on the stability and API consistency of these components to prepare a stable release.
| 4,172 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/blog/lab-tree-view-to-mui-x.js | import * as React from 'react';
import TopLayoutBlog from 'docs/src/modules/components/TopLayoutBlog';
import { docs } from './lab-tree-view-to-mui-x.md?@mui/markdown';
export default function Page() {
return <TopLayoutBlog docs={docs} />;
}
| 4,173 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/blog/lab-tree-view-to-mui-x.md | ---
title: The Tree View is moving to MUI X
description: Migrate to the new package to start building with our powerful Tree View, now part of MUI X. Previously released MIT components will stay MIT.
date: 2023-08-21T00:00:00.000Z
authors: ['flaviendelangle']
tags: ['MUI X', 'News']
card: false
---
After more than 4 years in the lab, the [Tree View](https://mui.com/x/react-tree-view/) components have found a new home as part of MUI X.
This means we'll be dedicating even more time and effort to these complex components, to better meet the needs of both you and your users.
## TL;DR
- The Tree View is one step closer to a stable release.
- **No surprise licenses changes**. We are staying true to [our promises](https://mui-org.notion.site/Stewardship-542a2226043d4f4a96dfb429d16cf5bd).
What's MIT stays MIT.
Therefore, all the existing features and future features of the Tree View will remain MIT and free to use.
- Follow the [migration steps](/x/migration/migration-tree-view-lab/).
## What is the Tree View?
The Tree View is a component to represent hierarchical data presented as nodes in a tree-like format.
The component allows to select one or multiple nodes.
<video preload="metadata" style="margin-bottom: 16px;" autoplay muted loop>
<source src="/static/blog/lab-tree-view-to-mui-x/treeview.mov" type="video/mp4">
</video>
## What is MUI X?
[MUI X](/x/) is a collection of advanced components built for complex use cases.
As opposed to the MUI Core library, which leans on the open-source community for support, MUI X components require several full-time developers dedicated to engineering and ongoing maintenance.
MUI X components are available under three licenses:
- **MIT license**, which is free to use and includes all the current (and more to come) Tree View features.
- **MUI X Pro**, a commercial license that offers features for handling large datasets and will include the most advanced features for Tree View, like virtualization.
- **MUI X Premium**, which is also commercial and includes, in addition to the Pro features, tooling for data analysis.
## Why did the Tree View move to MUI X?
Once a component is ready to leave the lab, it can either go to MUI X or MUI Core libraries.
Given the complex nature of the Tree View, it was a clear choice to group it with the other advanced components in MUI X.
Moreover, new advanced features such as virtualization and drag and drop are already on the roadmap.
The Tree View components are now available in the `@mui/x-tree-view` package which is [MIT licensed](https://unpkg.com/browse/@mui/x-tree-view/LICENSE) and includes all the current (free forever) features.
## How do I migrate?
Follow the [migration steps](/x/migration/migration-tree-view-lab/) by updating the package name and change from a default export to a named export:
```diff
-import TreeView from '@mui/lab/TreeView';
-import TreeItem from '@mui/lab/TreeItem';
+import { TreeView } from '@mui/x-tree-view/TreeView';
+import { TreeItem } from '@mui/x-tree-view/TreeItem';
```
or
```diff
-import { TreeView, TreeItem } from '@mui/lab';
+import { TreeView, TreeItem } from '@mui/x-tree-view';
```
We have prepared a codemod to help you migrate your codebase from `@mui/lab` to `@mui/x-tree-view`:
```bash
npx @mui/codemod v5.0.0/tree-view-moved-to-x <path>
```
## Where is the Tree View documentation?
You can find the documentation for the Tree View component in the [MUI X docs](/x/react-tree-view/).
## What's next for the Tree View?
For now, `@mui/x-tree-view` is in alpha.
Our next goal is to work on the stability and API consistency of its components to prepare a stable release in the next few months.
Please feel free to try out the component and provide any feedback you may have.
We also have a dedicated channel in our [Discord Server](https://mui.com/r/discord/) for you to provide any feedback or concerns you have with Tree View.
Happy building!
| 4,174 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/blog/making-customizable-components.js | import * as React from 'react';
import TopLayoutBlog from 'docs/src/modules/components/TopLayoutBlog';
import { docs } from './making-customizable-components.md?@mui/markdown';
export default function Page() {
return <TopLayoutBlog docs={docs} />;
}
| 4,175 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/blog/making-customizable-components.md | ---
title: Strategies for building customizable components
description: Explore the tradeoffs between different customization techniques, and how we landed on our strategy at MUI.
date: 2022-08-22T00:00:00.000Z
authors: ['alexfauquette']
tags: ['MUI X', 'MUI Core']
card: true
---
MUI's components are used by hundreds of thousands of developers worldwide, encompassing the full range of implementation from minor side projects to massive company websites.
This variety of users presents a dilemma for us as maintainers: hobbyists working on side projects want fully built components that work right out of the box, so they can focus on the application logic; many larger companies, by contrast, want to be able to fully customize components to respect their brand design.
Managing these contradictory needs only becomes more difficult as component complexity increases.
This article reviews several different approaches that a developer might take to customize UI components, as well as the various tradeoffs associated with each method.
Along the way, we'll explore how these tradeoffs ultimately led to the solution that we've settled on for customizing MUI components: the slot strategy.
## Style modification
(Don't need us to convince you to use a style library?
Feel free to skip this section and move on to [Logic modification](#logic-modification).)
### Good old CSS
Let's start with the easiest part: modifying the style.
This will necessarily involve CSS—especially the notion of [specificity](https://developer.mozilla.org/en-US/docs/Web/CSS/Specificity), which says that if an element is targeted by two CSS selectors, the browser will apply the more specific one.
Usually this means that the selector with more classes applied to it is more specific and therefore takes precedence.
For example, if we look at the Material UI `Switch` component, we have multiple subcomponents that we could expect to modify.
For each of them, we assign a specific CSS class:
<img src="/static/blog/making-customizable-components/switchHighlighted.png" style="width: 692px; aspect-ratio: 173/80; margin-top: 16px; margin-bottom: 16px;" loading="lazy" alt="Switch component with highlighted sub components" />
Notice that each element is styled using only one CSS class—the thumb style, for example, is applied with the `css-jsexje-MuiSwitch-thumb` class, so any CSS selector that includes more than one class will override its style.
I'm not a designer, so I made an ugly switch example using only CSS—
you can play around with it in [CodeSandbox](https://codesandbox.io/s/fast-http-kv85p5?file=/src/App.js):
<img src="/static/blog/making-customizable-components/uglySwitches.png" style="width: 692px; aspect-ratio: 173/80; margin-top: 16px; margin-bottom: 8px;" loading="lazy" alt="Switch customized with CSS" />
```jsx
<Switch className="uglySwitch" />
```
```css
/* two classes are more specific than the default single class selector */
.uglySwitch .MuiSwitch-thumb {
background-color: green;
}
.uglySwitch .MuiTouchRipple-root {
border: 2px solid red;
}
.uglySwitch .MuiSwitch-track {
background-color: orange;
opacity: 1;
}
```
### Let JS generate the CSS
Maybe you don't want to spend your time switching between CSS and JavaScript files, or writing long, cluttered stylesheets.
To avoid these problems you can integrate styles directly into your JS code. 🎉
Because the level of customization varies across projects, MUI's components can be customized in several different ways.
For more information on this topic, check out the [Material UI customization documentation](https://mui.com/material-ui/customization/how-to-customize/).
## Logic modification
Styling is not the only thing you need to customize.
You may have to modify the logic, which must be handled by the component itself.
### Simply add a prop
Consider a React UI component that lets users rate a product.
The default setting ranges from a score of 1 to 5.
But what if you need to increase it to 10?
In this case, you could add a `max` prop that tells the UI what the highest possible rating should be, making it simpler to customize.
This works well enough for a simple UI element, but what happens when the component in question has many more moving parts?
### It's never that simple
Let's play with a slightly more complex component: the [`DataGrid`](https://mui.com/x/react-data-grid/).
This component allows you to manage data by applying sorting, filtering, editing, exporting, and many other _-ings_.
To give you an idea of how complex this component can get, let's look at an example of a feature request for the `DataGrid` and think about how we could address it:
:::info
**[DataGrid] Sorting column options by alphabetical order**
When I open the filter panel, the input listing the names of the columns is sorted according to column position.
I would like to be able to sort it by alphabetical order.
<img src="/static/blog/making-customizable-components/issueScreenshot.png" style="width: 692px; aspect-ratio: 329/212; margin-top: 16px; margin-bottom: 8px;" loading="lazy" alt="Screen shot of the filter panel with column selector un sorted" />
:::
This request makes sense.
When you have a lot of columns, sorting them can make it easier to browse the list.
But how should we implement this kind of customization?
Adding a prop called `filterPanelColumnInputSortingStrategy` could work, but please, don't do that.
It just doesn't scale.
There are too many different props that developers might need to modify.
You will end up with API documentation so long that it will take an eternity to scroll to the end—meaning nobody will read it.
<img src="/static/blog/making-customizable-components/bruce.gif" style="width: 500px; aspect-ratio: 500/281; margin-top: 16px; margin-bottom: 8px;" loading="lazy" alt="Your user opening the list of props" />
Instead, consider these alternative solutions that can scale more efficiently with complex components:
### Other solutions
#### Don't bother with components
Passing all the parameters as props of a single component doesn't work.
So why not just create no components at all?
That's not a joke—that's the approach of headless libraries such as [react-table](https://www.npmjs.com/package/react-table).
Instead of providing working components, they provide hooks for managing the features and let developers build their components on top of it.
If you're willing to start from scratch, it can be a nice approach.
Use one hook to manage filtering, another one to manage sorting, and then build your UI using returned values.
This approach can scale because you can scope parameters to individual features.
The filtering hooks will only take into account parameters impacting the filtering, and so on—so you can split your code feature by feature.
But because this is a fully custom approach, it will take the most amount of work relative to all other options to construct a functional UI.
If your main priority is to get up and running quickly, then this may not be a viable solution.
#### Subdivide your components
Another approach I like is to provide subcomponents.
This is what we do for MUI Core components such as the [Menu](https://mui.com/material-ui/react-menu/).
This is also the approach used by [react-admin](https://marmelab.com/react-admin/) to provide a customizable administration interface.
Here is their quick start example:
The idea is to put the `Admin` component at the root level of the app.
This component a provider that's responsible for managing all data fetching and passing that data back to components.
The second important component is `ListGuesser` which defines how the data should be displayed.
```jsx
import * as React from 'react';
import { Admin, Resource, ListGuesser } from 'react-admin';
import simpleRestProvider from 'ra-data-simple-rest';
const dataProvider = simpleRestProvider('https://domain.tld/api');
export default function App() {
return (
<Admin dataProvider={dataProvider}>
<Resource name="users" list={ListGuesser} />
</Admin>
);
}
```
If you're unhappy with the rendering of the `ListGuesser`, then you can define your own components by reusing smaller components.
If you're unhappy with the smaller components, in turn, you can replace those with custom ones as well, and so on.
So you start with a component that's fully functional right out of the box, and you can rewrite any of its constituent elements as needed.
This approach has one major advantage: it gives you a lot of flexibility.
For example, you can easily modify the order of the components and their parent/children relationships.
This approach has also one major drawback: it gives you a lot of flexibility.
For example, you can easily modify the order of components in a bad way.
_The more freedom, the more bugs_.
##### Drawback example
To show you how easy it is to make a mistake using this technique, here is a personal example involving Material UI components.
I recently tried to wrap a `TextField` component in a `FormControl`, and was frustrated when it didn't work.
But the reason why is quite simple: the `TextField` component is itself composed of an input wrapped inside of a `FormControl`, and neither TypeScript nor `console.error` messages could warn me that my rendered markup was redundant and broken.
```jsx
<FormControl>
<TextField>
</FormControl>
// Equivalent to
<FormControl>
<FormControl>
<InputLabel />
<Input />
<FormHelperText />
</FormControl>
</FormControl>
```
This trade-off makes sense for react-admin, which is used for building complete websites.
Their users need complete freedom when it comes to rearranging components and introducing new components anywhere.
But MUI's products exist at a lower level.
We focus on the building blocks, not the entire website—though we do have [templates](https://mui.com/templates/) for that. 😉
So that's not the approach we took for the `DataGrid`.
#### Keep a single component
For `DataGrid`, we wanted to make it as simple as possible to add the DataGrid to your application, so we stuck with the individual component structure, which is to say that to create a new data grid, all you need is `<DataGrid rows={...} columns={...} />`.
To customize this single component, we use what we call the slot strategy.
## The slot solution
Now we are back to the original problem: how to provide deep customization options for a single component. Let's look at how we use slots to balance the freedom to customize with the need to avoid building from scratch.
### Overriding default components
First let's modify the appearance of the grid.
For color, spacing, and other basic properties you have CSS, but not everything is style related.
Here is a view of the grid with the filter panel open.
There's an **x** icon on the left side of the panel for deleting the current filter.
Say you want to replace this **x** with a trash icon.
You can't do it with CSS—you need DOM modification to replace the SVG icon.
<img src="/static/blog/making-customizable-components/FilterPanel.png" style="width: 692px; aspect-ratio: ; margin-top: 16px; margin-bottom: 16px;" loading="lazy" alt="Default view of filter panel" />
To manage such a scenario, the `DataGrid` has a prop called `components`.
This prop lets you replace some internal grid components with your own custom ones.
In this case, the component to replace is the `FilterPanelDeleteIcon`, which becomes `DeleteIcon`:
```jsx
<DataGrid {...data} components={{ FilterPanelDeleteIcon: DeleteIcon }} />
```
That's all it takes.
For every icon, there is a corresponding key in `components` that we call a slot.
If you provide a component to a slot, your component will be used instead of the default one.
Beyond swapping out icons, you can also plug native HTML elements into component slots, making it simple to customize the DOM structure of any component to suit your needs.
### Passing props
Slots are great for customizing the style and structure of small components.
But what about a situation like the aforementioned [feature request](#its-never-that-simple), where we need to modify the logic of the Data Grid's column selector?
We can't provide a slot to override the selector alone, or else we would need to provide one for all of the inputs and buttons, which are too numerous to keep track of.
We could use a slot to override the filter panel.
We provide this slot just in case you need a fully customized panel.
But honestly, who wants to rewrite an entire component just for simple sorting options?
Instead, what would be nice is to have a prop called `columnsSort` that lets you sort the column selector in ascending and descending order.
By adding this prop to the default filter panel, we can derive a customized panel like this:
```jsx
import { GridFilterPanel } from '@mui/x-data-grid';
function CustomFilterPanel(props) {
return <GridFilterPanel {...props} columnsSort="asc" />;
}
```
But this strategy of adding props to customize components is a bit verbose.
So we added a way to pass props to an existing component using `slotProps`.
You can pass props to every slot on `slots` using `slotProps`.
Here's how to pass `columnsSort='asc'` to the filter panel slot:
```jsx
<DataGrid
componentsProps={{
filterPanel: {
columnsSort: 'asc',
},
}}
/>
```
This way of passing props is nice, because it scopes them.
Props for the filter panel live together in `componentProps.filterPanel`.
And the same goes for the toolbar, the column menu, and all other components.
It also works pretty well with TypeScript autocomplete, because none of the slots have very many props.
So as soon as you've specified which slot you want to pass props to, your IDE will make good recommendations.
## What should I use?
If your goal is to customize the style, please don't start from scratch—use libraries to manage your CSS.
By adhering to solid class management standards, you should be able to provide styles that are easy to override.
You should add props to a component only if they impact the entire component—for example, disabling filtering impacts the whole grid, so a prop would be a viable solution here.
You should add slots to override icons, because it's common to need to replace them, so it should be easy to do.
Slots should also be added when your component is somewhat independent from the main one.
For example, a grid can exist without its filter panel, or without its toolbar.
## Customization is key
In our last two annual [developer surveys](/blog/2021-developer-survey-results/), our users made it clear that customization is always a top priority when choosing a UI library.
Thanks to the slot strategy and the introduction of supplementary tools like [MUI System's `sx` prop](https://mui.com/system/getting-started/the-sx-prop/), it has never been easier to customize MUI's components to suit your specific needs.
[Material UI](https://mui.com/material-ui/getting-started/) and [Joy UI](https://mui.com/joy-ui/getting-started/) are designed to be both beautiful and flexible right out of the box, while [Base UI](https://mui.com/base-ui/getting-started/) gives you the most freedom to implement your own custom styling solution.
[MUI X](https://mui.com/x/introduction/) is comprised of fully featured complex components like the `DataGrid` which—as we've seen—can still be customized in many ways with minimal friction.
Get started building with the MUI X Data Grid by [installing the MIT-licensed Community package](https://mui.com/x/react-data-grid/getting-started/#installation) today.
And be sure to let us know what you think about the customization experience!
| 4,176 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/blog/march-2019-update.js | import * as React from 'react';
import TopLayoutBlog from 'docs/src/modules/components/TopLayoutBlog';
import { docs } from './march-2019-update.md?@mui/markdown';
export default function Page() {
return <TopLayoutBlog docs={docs} />;
}
| 4,177 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/blog/march-2019-update.md | ---
title: March 2019 Update
description: Here are the most significant improvements in March.
date: 2019-04-05T00:00:00.000Z
authors: ['oliviertassinari']
tags: ['Company']
---
Here are the most significant improvements in March:
- We have removed the old styles modules 💅.
Be aware of the difference between `@material-ui/core/styles` and `@material-ui/styles`.
- The community has helped us to add many TypeScript demo variants. In order to minimize the overhead of handling two variants per demo (JavaScript & TypeScript), the JavaScript variant is generated from the TypeScript variant. If you are using TypeScript, you can ignore the `.propTypes =` assignations.
- We have migrated a few demos from the `withStyles()` API to the `makeStyles()` API.
If you are wondering which you should use, we would encourage the use of `makeStyles()` where possible. `withStyles()` is interesting for overriding component styles or for handling legacy class logics.
- We have made the [Box API](/system/react-box/) stable 🥳.
```diff
-import { unstable_Box as Box } from '@material-ui/core/Box';
+import Box from '@material-ui/core/Box';
```
- We have committed to [a new Roadmap](/material-ui/discover-more/roadmap/) (prioritized) for the next 6 months.
- We have migrated 50% of the codebase from the Classes API to the Hooks API. Once we are done with this task we can remove the internal usage of higher-order components.
- We have introduced [a simplified server-side rendering API](/system/styles/advanced/#server-side-rendering), inspired by styled-components.
## Our roadmap intent for April
_(We'll do our best, no guarantee!)_
- We are almost done with [the v4.0.0-alpha breaking changes](https://github.com/mui/material-ui/issues/13663). You can already find [the upgrade path](/material-ui/migration/migration-v3/) from v3 to v4 in the documentation. Next, we will release the first beta version (no more breaking changes).
The results of the MUI developer survey suggested that there are too many breaking changes.
Don't worry, it's almost over! We will focus on providing more components once we have released v4 stable.
- We will continue, and hopefully complete, the tasks we undertook:
- TypeScript demo variants.
- Migration from Classes to Hooks, removal of unnecessary internal components.
- Removal of `findDOMNode()`, support of `StrictMode`, forward of references.
- ❓ Please upvote our [GitHub issues](https://github.com/mui/material-ui/issues) if you want something specific. The number of 👍 helps us to prioritize.
| 4,178 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/blog/marija-najdova-joining.js | import * as React from 'react';
import TopLayoutBlog from 'docs/src/modules/components/TopLayoutBlog';
import { docs } from './marija-najdova-joining.md?@mui/markdown';
export default function Page() {
return <TopLayoutBlog docs={docs} />;
}
| 4,179 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/blog/marija-najdova-joining.md | ---
title: Marija Najdova joins MUI
description: We are excited to share that Marija Najdova has joined MUI. She has started this week full-time and is now part of the community team.
date: 2020-09-15T00:00:00.000Z
authors: ['oliviertassinari']
card: true
tags: ['Company']
---
We are excited to share that [Marija Najdova](https://twitter.com/marijanajdova) has joined MUI. She has started this week full-time, and is now part of the community team.
Before joining MUI, Marija worked on the React implementation of [Fluent UI](https://www.microsoft.com/design/fluent/) at Microsoft. She's passionate about React, design systems, and component driven development. At Microsoft, as part of the Fluent UI core team since 2018, she was responsible for the icons, animations and various theme related features.
Marija is off to a running start, having made important changes happen during her free time, even before starting! These include a new structure for the theme object, as well as the ability to [add custom variants](https://mui.com/material-ui/customization/theme-components/#creating-new-component-variants) in v5:
She is now actively working on the unstyled components and [the update of the style engine](https://github.com/mui/material-ui/issues/22342). These are two items we've been eager to push forward since the release of v1 but that required someone to be dedicated to tackling them.
The community team will continue developing the foundations on which to build great design systems. Here's a quick view of [the community roadmap](https://github.com/orgs/mui/projects/18/views/1).
We couldn't be more excited to have Marija on the team! You can follow her on [Twitter](https://twitter.com/marijanajdova).
| 4,180 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/blog/material-ui-is-now-mui.js | import * as React from 'react';
import TopLayoutBlog from 'docs/src/modules/components/TopLayoutBlog';
import { docs } from './material-ui-is-now-mui.md?@mui/markdown';
export default function Page() {
return <TopLayoutBlog docs={docs} />;
}
| 4,181 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/blog/material-ui-is-now-mui.md | ---
title: Material-UI, the organization, is now MUI!
description: Starting today, we are evolving our brand identity. We are clarifying the difference between our company and our products.
date: 2021-09-16T00:00:00.000Z
authors: ['oliviertassinari', 'danilo-leal', 'mbrookes']
tags: ['Company']
card: true
---
<img src="/static/blog/material-ui-is-now-mui/intro.png" alt="The new MUI logo" style="width: 796px; margin-top: 16px; margin-bottom: 16px;" />
Starting today we are evolving our brand identity to clarifying the difference between our company and our products.
- Material-UI: the organization is now called **[MUI](https://github.com/mui)**.
- Material-UI: the Material Design components developed by MUI is now called **[Material UI](https://mui.com/material-ui/getting-started/)**, we ditched the hyphen!
- Material-UI: the set of foundational MIT React components is now called **[MUI Core](https://github.com/mui/material-ui)**.
- Material-UI X: the set of advanced React components is now called **[MUI X](https://github.com/mui/mui-x)**.
Our previous name was no longer serving our areas of focus.
We have grown our product offering.
We needed a new identity to match our increased scope.
## The origin
Material UI [started](https://www.text-em-all.com/blog/material-ui-the-internet-found-our-ui-project) as a React implementation of the Material Design guidelines in 2014.
The goal was simple, to empower React developers to use Material Design.
The community [loved it](https://news.ycombinator.com/item?id=8582439) and was craving for more, so we kept building.
We made it easy for the community to contribute and started actively reviewing pull requests and guiding issues.
Over 2,200 developers have cared enough about our mission to contribute, so far.
Things started to really take off with [the release of v1](/blog/material-ui-v1-is-out/) in 2018.
The frontend community was actively migrating to React, but didn't have the bandwidth to rebuild legacy interfaces from scratch,
so before we knew it, we had grown into the most popular React UI component library.
The components were heavily used and customized to build customer-facing applications, internal tools, and mobile-hybrid apps.
## A larger focus
In our last survey, the number of developers that commented about improving the Material Design implementation was down by [60%](/blog/2020-developer-survey-results/#comparison-with-last-year) compared to the year before.
At the same time, 5X more developers were struggling to customize the components.
It was based on this context that we started work on v5 in 2019.
Our primary focus was to revamp the **customization Developer Experience (DX)**.
It had become clear that design (aesthetic, UX) and DX were key to unlocking the next stage of growth.
The new brand supports the [v5.0.0 release](/blog/mui-core-v5/) while also creating space for new initiatives that broaden the company horizon. It's a big deal!
Our ultimate goal is to become the most effective and efficient tool to build UIs while making it accessible to the many.
## Our new brand
### A new name
We are breaking the strong association with Material Design
as we have seen too many people confusing Material UI with Google, or as a synonym of Material Design.
We are now called **MUI**. It stands for **M**aterial to build **UI**s
and is pronounced [/ɛm juː aɪ/](http://ipa-reader.xyz/?text=%C9%9Bmju%CB%90a%C9%AA).
It's shorter, it distinguishes us, and it's familiar – many people already used it for abbreviating Material UI.
More importantly, it allows for the release of products not directly coupled to Material Design, such as an unstyled/headless version of the components, a brand new second design system as an alternative to MD, and more ambitious initiatives.
### A new domain name
A new name wouldn't be so official without a new domain,
so we have moved home from https://material-ui.com/ to https://mui.com/, a very easy to type (and find) domain.
### New logos
We've tightened up the company logo to match the new brand.
It's basically the same, to keep it familiar –
we're keeping the geometrical shape, to resonate with the _building blocks_ idea of the components –
however, we're reducing the emphasis on the 3D perspective, stepping away from the notion of elevation that Material Design coined.
<img loading="lazy" src="/static/blog/material-ui-is-now-mui/old-new.png" alt="Side-by-side of the new and old logo" style="width: 796px; margin-top: 16px; margin-bottom: 16px;" />
To better identify, market, and promote each product, we're introducing logos for each one of them.
<img loading="lazy" src="/static/blog/material-ui-is-now-mui/products.png" alt="Logos for MUI Core, MUI X and Templates" style="width: 796px; margin-top: 16px; margin-bottom: 16px;" />
- **MUI Core** contains ready-to-use foundational components, free forever.
- **MUI X** includes advanced and powerful components for complex use-cases.
- **Templates** is a collection of fully built, out-of-the-box, React templates for your application. They are developed by the community curated by us for quality.
### New package names
The package names have changed in v5, which is a **breaking change**.
You can find more details in the [release](https://github.com/mui/material-ui/releases/tag/v5.0.0) [notes](https://github.com/mui/mui-x/releases/tag/v4.0.0).
The npm organization name (scope) has moved from @material-ui to [@mui](https://www.npmjs.com/org/mui).
### A new website & documentation
Lastly, to celebrate the start of a new chapter for the company with the release of v5.0.0, and new products in the making, we're introducing a brand new website and documentation design. You'll find a completely different theme from Material Design – new typeface, colors, box-shadows, and more,
all done using the flexible theming features of v5. [Head to the new website](/)!
<img loading="lazy" src="/static/blog/material-ui-is-now-mui/website-homepage.png" alt="Screenshot of the new website homepage" style="width: 796px; margin-top: 16px; margin-bottom: 16px;" />
> 💡 Note that these changes in the website and documentation do **not** impact the design of the components released under the `@mui/*` npm packages.
## The path ahead
There are many more exciting things to come in the future as we roll into this new chapter.
We're grateful to have you with us, supporting the library, and helping it grow and mature.
Material Design will continue to be supported with the same attention to detail as before.
We aim to keep serving those who like the library for closely following MD, while also leveraging the strong foundation built so far to offer new components, designs, and products.
We hope you like it. Happy building!
| 4,182 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/blog/material-ui-v1-is-out.js | import * as React from 'react';
import TopLayoutBlog from 'docs/src/modules/components/TopLayoutBlog';
import { docs } from './material-ui-v1-is-out.md?@mui/markdown';
export default function Page() {
return <TopLayoutBlog docs={docs} />;
}
| 4,183 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/blog/material-ui-v1-is-out.md | ---
title: Material UI v1 is out 🎉
description: It has taken us two years to do it, but Material UI v1 has finally arrived!
date: 2018-05-18T00:00:00.000Z
authors: ['oliviertassinari', 'mbrookes']
tags: ['Company']
---
> React components that implement Google's Material Design.
 header & logo by @hai-cea](https://cdn-images-1.medium.com/max/2050/1*BKssrX-qEmyN6YaRNTvNlw.png)
<p class="blog-description">Our new documentation header & logo by @hai-cea</p>
It has taken us two years to do it, but Material UI v1 has finally arrived!
We are so excited about this release, as it's setting a new course for the project. Thank you to _everyone_, especially to [the team](/about/), and to everyone who's contributed code, issue triage, and support. **Thank you.**
✨✨✨ See the **[1.0.0 Release Note](https://github.com/mui/material-ui/releases/tag/v1.0.0)** on GitHub. ✨✨✨
<iframe src="https://codesandbox.io/embed/4j7m47vlm4" width="100%" height="300px" frameborder=0></iframe>
<p class="blog-description">One button</p>
## High-level Goals for v1
Material UI was started [3 years ago](https://github.com/mui/material-ui/commit/28b768913b75752ecf9b6bb32766e27c241dbc46) by [@hai-cea](https://github.com/hai-cea). The React ecosystem has evolved considerably since then, and we have also learned along the way. Two years ago, [@nathanmarks](https://github.com/nathanmarks/) [started](https://github.com/mui/material-ui/commit/cf0934dda2ef83852ca094ac7250e2d562ce6156) an ambitious task to rebuild Material UI from the ground-up, taking advantage of this knowledge to address long-standing issues in customizability, ease of use, and code quality.
### Customizability
Material UI v1 is our second stab at the execution of [the vision](/material-ui/discover-more/vision/).
We want Material UI to become whatever is generally useful for application development, all in the spirit of the Material Design guidelines. Material UI is not only an implementation of the Material Design guidelines, but a general use UI library of components that are needed by many. We are even allowing developers to build non Material themes on top of Material UI components. We will soon open source examples of this.
- **CSS-in-JS**. We have seen [a great potential for **inline-styles** in the past](https://github.com/mui/material-ui/issues/30). It was an opportunity to solve four problems at once: removing the LESS toolchain dependency, allowing dynamic styles, allowing style code splitting and make overrides simpler.
Unfortunately, the **[execution didn't deliver](https://github.com/mui/material-ui/issues/4066)**. We were lacking key features only available in CSS: media queries, pseudo selectors, pseudo elements, browser prefixes. Debugging was much harder. Overriding styles was very challenging – developers always had to look the implementation, and couldn't use CSS without relying on !important.
Two years ago, we decided to move away [from inline-styles toward **CSS-in-JS**](https://github.com/oliviertassinari/a-journey-toward-better-style). We are very happy with the outcome. We would like to thank [@kof](https://github.com/kof) for the awesome work he has done with [JSS](https://github.com/cssinjs/jss), the internal solution we use. It's allowing us to be [interoperable](/material-ui/guides/interoperability/) with all the other styling solutions.
- **Theme**. You can't have a good customizability story without a good theming story. We have been redesigning the theme. It's a [JavaScript object](/material-ui/customization/default-theme/) that contains all the variables and utility functions you might need to style your components: a palette, a typography, breakpoints helpers, transition helpers, etc.
The theme object can be dynamic and nested.
### Ease of use
We know the ease of use is a critical part of user acquisition. The more user we have, the more likely we can make the project sustainable. Improving the ease of use comes in different flavors:
- **Onboarding**. We have reduced the onboarding friction as much as possible. We know the onboarding is a critical step for user acquisition. The onboarding friction comes in different flavors:
We have reduced the number of installation steps needed. It should be as simple as 1. npm install @mui/material and 2. import Button from '@mui/material/Button'; . We don't ask for polyfill, custom webpack plugin or any specific build tool. The usage of MuiThemeProvider is no longer mandatory.
- **Examples**. We are hosting [example projects](https://github.com/mui/material-ui/tree/master/examples) with the most popular solutions to start a project: [create-react-app](https://github.com/facebook/create-react-app), [Next.js](https://github.com/vercel/next.js), [Gatsby](https://github.com/gatsbyjs/gatsby), and CDN.
- **Isolation**. Our components now work in isolation. You should be able to use a single Material UI component in an existing codebase without any side effect. No global CSS override needed, no bundle size bloat.
- **Documentation**. We have made a huge investment in the documentation. We use [Next.js](https://github.com/vercel/next.js) for a blazingly fast navigation experience. It's also allowing us to provide a first server-side support for the components. We had added a search bar powered by [Algolia's DocSearch](https://docsearch.algolia.com/). (don't miss the s shortcut to focus the search bar). We have added many new documentation sections: guides, FAQ, etc. We have made the demos more interactive thanks to a direct integration with CodeSandbox.
- **DOM**. We have focused on providing low-level components, in this v1 rewrite. By low-level, we mean components as close as possible to the underlying DOM structure and as stateless as possible. It should help reduce the mental overhead of using the components, encourage interoperability, and simplify customizability. For instance with the TextField. The component was broken down into 4 components. Our Input exposes the same API than a native input. You can switch one for the other. Leveraging this structural choice, we were able to demonstrate 3 autocomplete integration example with [Downshift](https://github.com/downshift-js/downshift), [react-autosuggest](https://github.com/moroshko/react-autosuggest), and [react-select](https://github.com/JedWatson/react-select).
### Code quality
Many people discover web development through Material UI but it's also used in production to serve millions of customers. We have an important responsibility, our implementation needs to be rock solid.
- **Best practices.** We are following the best practices as much as possible. We have made the components: fully accessible, fully [HTML5 compliant](https://validator.w3.org/) and SEO friendly.
 report of the Material UI documentation homepage](https://cdn-images-1.medium.com/max/2000/1*_x_j-jasswGw0WaDyeHk-g.png)
<p class="blog-description">Lighthouse report of the Material UI documentation homepage</p>
- **Continuous integration.** Every single line of code is tested. We have an impressive [💯% test coverage](https://codecov.io/gh/mui/material-ui/branch/master). With more than 700 contributors, it's really important. All these tests allow us to quickly iterate and with confidence. We run the test suite runs on all the supported platforms. We also run more than [180 visual regression tests](https://app.argos-ci.com/mui/material-ui/builds) thanks to [Argos-CI](https://www.argos-ci.com/).
 build](https://cdn-images-1.medium.com/max/2000/1*bnWGqotk36ivrYTp3dY7fA.png)
<p class="blog-description">An example BrowserStack build</p>
- **Bundle size**. If you take all the Material UI components, your bundle will weight more than 100 kB gzipped. Material UI looks like a huge dependency but it's fine in practice with code splitting. You will most likely use ~40% of the library on a given page/screen. The bundle size is important. It's [constantly monitored](https://github.com/mui/material-ui/blob/ca69253843208c21593fff230151e1fffd93a566/.size-limit), which prevents us from introducing size regressions, and allows us to recognize positive efforts.
 output](https://cdn-images-1.medium.com/max/2000/1*AQoyq9OvjFZJE2Ep0UtCzA.png)
<p class="blog-description">An example of size-limit</p>
- **Development warnings**. Because the API surface of UI components is so large, it's easy to leave the beaten path. We have condensed a large number of the issues raised into a number of informative development mode warnings to help you stay on the right track. Aside from [propTypes](https://legacy.reactjs.org/docs/typechecking-with-proptypes.html), we have added more than [20 warnings](https://github.com/mui/material-ui/search?p=1&q=warning&type=&utf8=%E2%9C%93), and the list will grow as we discover more edge cases.
## What's new in v1?
There are so many new things, we can't be exhaustive. Aside from what we have already announced, you will find:
- Simpler and more powerful theme
- Grid layout component
- New documentation
- Right-To-Left support
- First class server-side support
- [Premium themes](https://mui.com/store/)
- First class TypeScript support
- **And much, much more**
## What's next?
- **Material Design.** The Google Design team has recently released a new iteration on the Material Design guidelines, it's focused on themability. This is great news! We will do our best to be up to date. It also confirms that heavily investing in customizability for v1 was a good call. We will continue our efforts.
- **More utils.** We want to work on new utility components: Spacing, Display, Color, etc.
- **Documentation.** We want to host multiple version of the documentation. Each minor release will bring a new hosted version of our documentation. Right now, we have v1.0.0, and come v1.1.0's release, we'll add that too. Prior releases will continue to be linked from our navigation as is already the case for v0.x.
We want to translate the documentation into Chinese and more languages. [Any help is welcomed!](https://github.com/mui/material-ui/issues/9511)
- **Learning materials.** The quality of the documentation is equally as important as the quality of the implementation, and while the reference documentation is comprehensive, we could author a [learning tutorial](https://learnnextjs.com/) like Next.js has done, or an [egghead.io](https://egghead.io/) course.
- **Themes.** We want to provide common layouts example to make getting started even easier. We also plan on adding more premium themes.
- **Performance.** We can't optimize something we can't measure, and we don't currently have a CI performance benchmark, so we will need to build one and start investigating bottlenecks.
- **Bundle size.** The library needs to be as small as possible, so we need to work on solutions to further reduce the bundle size, for instance, supporting [Preact](https://preactjs.com/) or [Nerv](https://nerv.aotu.io/) can help.
- **Type checking.** We will continue to improve the TypeScript and maybe the Flow coverage of the library.
## Premium themes
We have shipped the long-awaited Material UI v1 stable release. With a new codebase designed to better support customization, it's the perfect timing to start building and promoting premium themes. We are very happy to announce [the first two](https://mui.com/store/) from [Creative Tim](https://mui.com/store/contributors/creative-tim/). More are coming.
<p class="blog-description">Creative Tim themes</p>
<p class="blog-description">A preview of an open source theme we will soon release.</p>
## Thank you
Finally, one last thank you to everyone who's contributed to Material UI v1.
I'm so excited at the idea we are making it stable, but rest assured, it's just the beginning. We will keep working hard on delivering the best possible UI library components.
Material UI is an MIT-licensed open source project. It's an independent project with ongoing development helped by the support of these awesome [backers](/material-ui/discover-more/backers/). If you'd like to join them, please consider:
- [Become a backer or sponsor on Open Collective](https://opencollective.com/mui-org).
- [Become a backer or sponsor on Patreon](https://www.patreon.com/oliviertassinari).
<p class="blog-description">Our gold sponsors</p>
- GitHub: https://github.com/mui/material-ui ⭐
- Twitter: https://twitter.com/MUI_hq
| 4,184 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/blog/material-ui-v4-is-out.js | import * as React from 'react';
import TopLayoutBlog from 'docs/src/modules/components/TopLayoutBlog';
import { docs } from './material-ui-v4-is-out.md?@mui/markdown';
export default function Page() {
return <TopLayoutBlog docs={docs} />;
}
| 4,185 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/blog/material-ui-v4-is-out.md | ---
title: Material UI v4 is out 🎉
description: Material UI v4 has finally arrived. We are so excited about this release, as it defines better foundations for the UI components.
date: 2019-05-23T00:00:00.000Z
authors: ['oliviertassinari', 'mbrookes', 'eps1lon']
tags: ['Company']
---
> React components for faster and simpler web development. Build your own design system, or start with Material Design.
Material UI v4 has finally arrived. We are so excited about this release, as it defines better foundations for the UI components. Thank you to everyone, especially to [the team](/about/), and to everyone who's contributed code, issue triage, and support. **Thank you.**
✨✨✨ See the **[4.0.0 Release Note](https://github.com/mui/material-ui/releases/tag/v4.0.0)** on GitHub. ✨✨✨
<p class="blog-description">https://mui.com/</p>
## Summary
- [High-level goals for v4](#high-level-goals-for-v4)
- [What's new?](#whats-new)
- [What's next?](#whats-next)
- [Premium themes store](#premium-themes-store-✨)
## High-level goals for v4
Material UI v1 was [released](https://medium.com/material-ui/material-ui-v1-is-out-e73ce13463eb) one year ago. Version 4 is our most important major release since then. For those unfamiliar with the history of the project, we didn't release a v2, and v3 only introduced a slight browsers support change.
This release happens within our [fixed frequency](https://mui.com/versions/#release-frequency) release strategy. We try to release a major at least every 12 months and at most every 6 months. The migration from v0 to v1 was painful, it almost felt like using two different UI libraries. We've done our best to minimize the time needed to migrate from v3 to v4. To help ease the transition, you can follow this [migration guide](/material-ui/migration/migration-v3/) 📚. It shouldn't take more than a few hours.
This release is influenced by two major factors. First, following the Developer Survey we ran in March, we have [analyzed the results](/blog/2019-developer-survey-results/) and used them to change [our priorities](/material-ui/discover-more/roadmap/#priorities) for the coming year. Secondly, we needed to be up to date with the latest best practices in the React community and with the Material Design Specification.
### Customization
The Material Design team at Google has made the customization of their design system framework a core feature: [Material Theming](https://m2.material.io/design/material-theming/overview.html). It's an important dimension of the library for us. Since the release of v1, we have been improving the component customization demos, release after release. We demonstrate a wide range of different designs:
<p class="blog-description"><a href="https://v4.mui.com/components/text-fields/#customized-inputs">live demo</a></p>
<p class="blog-description"><a href="https://v4.mui.com/components/tabs/#customized-tabs">live demo</a></p>
<p class="blog-description"><a href="https://mui-treasury.com/styles/button/">live demo</a></p>
After listening to v3 customization experiences of hundreds of developers, we realized that we could do better. We have found 4 classes of common problems.
- **CSS specificity**. The developers' style specificity needs to be higher to win over the style Material UI injects in the page. By default, Material UI injects its style at the end of the `<head>` element. However, styled components and other popular styling solutions inject the style just before it, losing specificity. To solve the problem, we have introduced a new prop: `injectFirst`.
```jsx
import { StylesProvider } from '@mui/styles';
<StylesProvider injectFirst>
{/* Your component tree.
Styled components can override Material UI's styles. */}
</StylesProvider>;
```
<p class="blog-description">The DOM output once injectFirst is used.</p>
- **classes boilerplate**. Early in the v1 effort, we [decided](https://github.com/oliviertassinari/a-journey-toward-better-style) to use a CSS-in-JS styling solution: [JSS](https://cssinjs.org/). The large majority of the CSS-in-JS solutions output non-deterministic class names, e.g. `.fHmkjM`. This design decision helps the isolation of the style of each component, however, it makes the overrides harder. We introduced a `classes` API in v1 to target all our elements as an attempt to mitigate this problem.
We have observed the use of this API for months and have seen many people struggling with it. It can be challenging to apply the class name on the right element and requires boilerplate as well.
As an attempt to further improve the situation, we have changed the class name generation to [output global class names](/system/styles/advanced/), while keeping the `classes` API working as before 💅.
<p class="blog-description">side by side comparison of both valid classes vs global approaches.</p>
⚠️ Using global class names provide more power but comes with responsibility. We encourage patterns that increase your custom style isolation.
- **Pseudo-classes.** A pseudo-class is a keyword added to a selector that specifies a special state of the selected element. The native elements support a wide range of pseudo-classes, the most popular ones being: `:focus`, `:hover`, `:active`. Sometimes, Material UI can't use a pseudo-class as the state doesn't exist in the platform, e.g. the selected state of a menu item. Material UI implements support of eight different [custom pseudo-classes](/material-ui/customization/how-to-customize/#state-classes). It's important to understand that you need to increase the specificity when using a pseudo-class. For instance:
```css
.MenuItem {
color: black;
}
/* We increase the specificity */
.MenuItem.Mui-selected {
color: blue;
}
```
- **Dynamic variations.** As one of the most requested features, we have added the support for style functions:
```jsx
const useStyles = makeStyles({
// style rule
foo: (props) => ({
backgroundColor: props.backgroundColor,
}),
bar: {
// CSS property
color: (props) => props.color,
},
});
function MyComponent() {
// Simulated props for the purpose of the example
const props = {
backgroundColor: 'black',
color: 'white',
};
// Pass the props as the first argument of useStyles()
const classes = useStyles(props);
return <div className={`${classes.foo} ${classes.bar}`} />;
}
```
### Documentation
Documentation was reported as the 3rd most critical pain point in the developer survey. We have fixed some of the reported issues and aim to continuously improve going forward.
- **TypeScript**. TypeScript's growth is impressive, the traffic of their documentation website has grown by a factor of 6 in 3 years. Material UI v1 was released with built-in TypeScript definitions, but we needed to do more. Sebastian has led the effort to migrate all the demos from JavaScript to TypeScript. This has two important implications. First, we type check our demos, this drastically improves our TypeScript test coverage. We have fixed many issues during the migration. Second, if you are writing your application with TypeScript, you can directly copy & paste our demos without needing to convert them, or having to fix the obscure errors.
<p class="blog-description">https://www.typescriptlang.org traffic estimation over time.</p>
<p class="blog-description">Use the JS/TS toggle to see code in JavaScript or TypeScript</p>
- **i18n**. Developers come to Material UI's documentation from all around the world. We want to include as many people as possible 🌎🌍🌏. We have completed the effort started in v3 by working on the Algolia search support, Google search indexing, Table Of Contents and Side Nav infrastructure.
We would like to thank [Danica Shen](https://github.com/DDDDDanica), [Dominik Engel](https://github.com/Domino987), and [Jairon Alves Lima](https://github.com/jaironalves) for their heroic work on the 🇨🇳, 🇩🇪 and 🇧🇷 translations, while not forgetting the other 348 (and growing) translators.
- **Best practices**. We are now recommending the use of the hooks API over the classes API wherever possible. We have migrated a large portion of the demos to showcase a single approach.
- **A better UX**. We have changed the menu organization to group all the components under a single navigation item. We have changed the background color to white to increase the text contrast and readability.
### Performance
You may be afraid that using Material UI's components will bloat and slow down your website/application. Would you be better off writing your own components? Well, it's our mission to make this cost as minimal as possible 🚀.
- **Tree shaking**. Material UI v4 is the first version to support native tree shaking with ES modules. This has one important DX benefit—you can now use destructured imports when importing multiple components:
```js
import {
Table
TableBody,
TableCell,
TableHead,
TableRow,
Paper,
} from '@mui/material';
```
- **Bundle size reduction**. The bundle size went from 95 kB gzipped to below 80 kB gzipped between the last v3 release and the first v4 beta release. This is _remarkable_ considering that we have added new features and components along the way 😍! This was made possible by many small incremental changes: tree shaking, removal of [multiple](https://github.com/timoxley/keycode) [internal](https://github.com/oliviertassinari/react-event-listener) dependencies, hooks migration, clsx migration, [smart Babel plugin](https://github.com/merceyz/babel-plugin-optimize-clsx), etc.
<p class="blog-description">A -15% bundle size reduction. ⚠️ Please don't use the absolute number to compare different UI libraries. Nobody should import the whole barrel index.js file. What matters is the cost of the individual modules you import.</p>
- **Continuous bundle size tracking**. This bundle size reduction is only possible because we track this metric in each pull request. We have improved our strategy moving from [size-limit](https://github.com/ai/size-limit) to a React [inspired solution](https://github.com/mui/material-ui/pull/14662).
<p class="blog-description">Fine level tracking</p>
- **Preact X.** We have introduced a working [integration example with Preact](https://github.com/mui/material-ui/blob/HEAD/examples/material-ui-preact/README.md). Preact is a fast, 1/10 smaller alternative to React, with the same modern API. We will do our best to support it.
- **Runtime performance**. We have heard that some people struggle with the runtime cost of using Material UI. We have solved a few problems reported, but nothing systematic. We have observed [a slight gain](https://github.com/mui/material-ui/pull/15023) by moving from the classes API to the hooks API. However, it's hard to make progress as we lack a properly setup performance bench. It's something to consider for v5.
### Preparing for the future
Material UI v4 depends on React ≥16.8.0. This is the first version of React that supports the [new Hooks API](https://legacy.reactjs.org/docs/hooks-intro.html).
- **Ref forwarding**. Most of the time, you use the `ref` prop to access the underlying DOM node of a React element. You might want to focus an element, compute the position of an element, and so on. You should never need to access a Material UI component's instance methods, they are considered private. The components expose an `action` when it's really needed. For instance, you might want to update the tab indicator position when it goes out of sync with the tab item position. To ease this use case, Sebastian has lead an effort to implement [`React.forwardRef()`](https://legacy.reactjs.org/docs/forwarding-refs.html). In practice, this means that you can retrieve a reference to the DOM node like you would do with a built-in component (`button`, `div`, etc.):
```jsx
import { Button } from '@mui/material';
function MyButton() {
const myRef = React.useRef();
return <Button ref={myRef}>;
}
```
- **Hooks migration**. While there is [no plan](https://legacy.reactjs.org/docs/hooks-intro.html#gradual-adoption-strategy) to remove classes from React, the React Team [encourages](https://legacy.reactjs.org/docs/hooks-faq.html#do-i-need-to-rewrite-all-my-class-components) new code to be written with the hooks API.
Josh has led an effort to rewrite the vast majority of our components with the hooks API. The change has a couple of advantages.
Not all [the platforms we support](/material-ui/getting-started/supported-platforms/) can use the class API natively, so we transpile the syntax with Babel. Functions are supported everywhere, they require fewer line of code. We have observed a -2% gzipped bundle reduction by removing the need to transpile classes.
It reduces the noise in the React Dev Tools ⚛️, since we could reduce the number of intermediary elements from 5 to 2 in the most common cases.
We have found the hooks API easier to work with: to write, to read, and to change. This is a net positive for everyone's productivity.
Developers read our source to find inspiration, so we should do our best to promote the best patterns.
<p class="blog-description">React Dev Tools output for one Typography element in production (<a href="https://github.com/mui/material-ui/pull/15023">this POC</a> might further improve the situation).</p>
- **Concurrent mode**. React has shared its [release timeline](https://legacy.reactjs.org/blog/2018/11/27/react-16-roadmap.html#react-16x-q2-2019-the-one-with-concurrent-mode) for the important features coming into React. [Concurrent mode](https://legacy.reactjs.org/blog/2018/11/27/react-16-roadmap.html#react-16x-q2-2019-the-one-with-concurrent-mode) should be released within the next few months. Concurrent Mode lets React apps be more responsive by rendering component trees without blocking the main thread. We have worked on getting ready for it. Most of the work was related to fixing the [<React.StrictMode>](https://legacy.reactjs.org/docs/strict-mode.html) warnings. You should soon be able to leverage it 🔥.
- **Shallow tests.** We have removed the majority of our internal shallow tests to rely on [full mount tests](https://twitter.com/dan_abramov/status/1109461529227866112).
### Material Design
Most of our users are interested in the good looking functional aspect of our components, rather than in a strict application of the Material Design guidelines. However, we think that it's important for us to keep up to date with the guidelines. The specification received it's most significant update since Google made it the design language for its apps in 2014, at [Google I/O 2018](https://design.google/library/io-2018-our-definitive-guide-design/).
The Material Design "v2" announcement caught us by surprise when we released Material UI v1. We have worked on upgrading our components since then. In v4, we have updated the styles of the Tab, Snackbar, Checkboxes, Radios, Switches, List, Dialog, and other components ✨.
<p class="blog-description">Dense Outlined text field</p>
<p class="blog-description">Dense Filled text field</p>
## What's new?
There are so many new things, we can't be exhaustive. Aside from what we have already announced, you will find:
- A new **strapline** "_React components for faster and simpler web development. Build your own design system, or start with Material Design._" that better embodies our mission and emphasize the [customizability potential](https://techcrunch.com/2018/05/08/google-makes-its-material-design-system-easier-to-customize/).
- New [templates](/material-ui/getting-started/templates/).
<p class="blog-description">One example among others</p>
- [Responsive font sizes.](/material-ui/customization/typography/#responsive-font-sizes)
- [A Box + system utility helpers](https://medium.com/material-ui/introducing-material-ui-design-system-93e921beb8df).
An application example of the Box component.
- [A better spacing helper.](/material-ui/customization/spacing/)
An example of the new spacing helper API.
- A new [@material-ui/pickers](https://github.com/mui/material-ui-pickers) package created and supported by [Dmitriy Kovalenko](https://github.com/dmtrKovalenko) 📅.
<p class="blog-description">Keyboard support</p>
<p class="blog-description">Inline mode</p>
- A new [@mui/styles](/system/styles/basics/) package that isolates our styling solution. It can be used independently of the core components. It comes with a hooks API that requires less boilerplate 😍
```jsx
import * as React from 'react';
import { makeStyles } from '@mui/material/styles';
const useStyles = makeStyles({
root: {
background: 'linear-gradient(45deg, #FE6B8B 30%, #FF8E53 90%)',
border: 0,
borderRadius: 3,
boxShadow: '0 3px 5px 2px rgba(255, 105, 135, .3)',
color: 'white',
height: 48,
padding: '0 30px',
},
});
export default function Hook() {
const classes = useStyles();
return <button className={classes.root}>Hook</button>;
}
```
⚠️ Be aware of the difference between _@mui/styles_ and _@mui/material/styles_. The latter contains the [default theme](/material-ui/customization/default-theme/).
- A well supported [Gatsby plugin](https://github.com/hupe1980/gatsby-plugin-material-ui) for _@mui/styles_.
- A [Cookbook](https://www.packtpub.com/product/react-material-ui-cookbook/9781789615227) published by Packt and written by Adam Boduch.
## What's next?
Together, we have accomplished most of the objectives we defined a year ago in the v1 release [blog post](https://medium.com/material-ui/material-ui-v1-is-out-e73ce13463eb). We're proud of everyone who contributed. We're going to try to execute these new objectives with the same regularity:
- **More components.** This is, by far, the most requested improvement dimension of the library. We have identified a few useful components we are interested in building:
- Layout components
- Autocomplete/ ComboBox / Dropdown List / MultiSelect
- Slider in core and the support for range values
- Tree view
- Dropzone / Upload
- Skeleton
- Jumbotron
- Carousel
- Rating
- Timeline
- Advanced table
Let us know the components you want! 🚀
- **Documentation**. The documentation is paramount. We are working on a page ranking mechanism that will help us better prioritize our effort on the documentation.
- **Use `system` in the core.** We have received great feedback on the new system package. Going forward, we will try to move it to the core components. Ideally, you should be able to use dynamic color & variants from your theme as well as have access to all the props:
```jsx
import { Button } from '@mui/material';
<Button mt={{ xs: 2, md: 3 }}>Hello worlds</Button>;
```
- **Styled components.** We have seen many people asking for migration to styled components. We want Material UI v5 to be better aligned with the community's best-loved tools, but at the same time, we don't want to break your code.
So we will work on isolating the components from the styling solution. The new _@mui/styles_ package is the first step in this direction. We envision a world where you can use Material UI styled with styled components, linaria, and JSS or without any styles.
Developers should be able to use their preferred styling solution without paying the cost of two CSS-in-JS runtimes.
- **Accessibility.** While we try to fix all accessibility issues as they are reported by our users, we feel that we can do better. We want to run a professional ADA audit of all our components ♿️.
## Premium themes store ✨
How are we going to sustain this ambitious roadmap?
We will follow the Bootstrap model.
We are working on [a Premium themes store](https://mui.com/store/).
We have built partnerships with the best theme authors of the ecosystem.
Within a few weeks, you should find a collection of the best Material UI templates and themes 😍.
## Thank you
Finally, one last thank you to everyone who's contributed to Material UI v4.
I'm so excited about this release! It's just the beginning. We will keep working hard on delivering the best possible React UI framework components.
<hr />
_You can find the [same post on Medium](https://medium.com/material-ui/material-ui-v4-is-out-4b7587d1e701)._
| 4,186 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/blog/matheus-wichman-joining.js | import * as React from 'react';
import TopLayoutBlog from 'docs/src/modules/components/TopLayoutBlog';
import { docs } from './matheus-wichman-joining.md?@mui/markdown';
export default function Page() {
return <TopLayoutBlog docs={docs} />;
}
| 4,187 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/blog/matheus-wichman-joining.md | ---
title: Matheus Wichman joins MUI
description: We are excited to share that Matheus Wichman has joined MUI.
date: 2021-04-05T00:00:00.000Z
authors: ['oliviertassinari']
card: true
tags: ['Company']
---
We are excited to share that [Matheus Wichman](https://github.com/m4theushw) has joined MUI.
He started a couple of days ago full-time, and is part of the advanced components team.
Before joining MUI, Matheus worked as a software engineer at a consulting agency in Brazil.
He has spent the last three years focusing on React and the frontend world - his last project was for a payment processing company, where he created a design system based on MUI and developed new components for enterprise applications.
Matheus is passionate about software development, so much so that he started his career very early on, coding in PHP and JavaScript, at age 14.
We were impressed by his capability to quickly jump into an unknown codebase and solve problems at their root.
In a couple of days, he has managed to report and fix bugs, both in the core components (_mui/material-ui_) and in the advanced components repository (_mui/mui-x_).
While we can't predict the future, Matheus will initially help us deliver the planned breaking changes of MUI v5, increase the pace of development of the date range picker, and push the data grid forward.
Matheus is the first of a series of 5 new positions we have recently opened and almost all filled.
We will cross the 10 person milestone in the coming weeks.
We have opened these positions as our revenue growth allows.
At the current pace, we will soon open new positions.
You can [follow us on Twitter](https://twitter.com/MUI_hq) to hear about upcoming positions.
These new roles will help accelerate our mission, strengthen our existing offering, and initiate a new vertical.
We couldn't be more excited to have Matheus on the team!
| 4,188 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/blog/may-2019-update.js | import * as React from 'react';
import TopLayoutBlog from 'docs/src/modules/components/TopLayoutBlog';
import { docs } from './may-2019-update.md?@mui/markdown';
export default function Page() {
return <TopLayoutBlog docs={docs} />;
}
| 4,189 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/blog/may-2019-update.md | ---
title: May 2019 Update
description: Here are the most significant improvements in May.
date: 2019-06-08T00:00:00.000Z
authors: ['oliviertassinari']
tags: ['Company']
---
Here are the most significant improvements in May:
- 🎉 We released MUI v4 stable during the React Europe conference.
You can find the details in our [blog post 📝](/blog/material-ui-v4-is-out/) and a quick introduction in this [5 minutes talk](https://www.youtube.com/watch?v=m54_CPfbWow).
- 🐛 We have made two subsequent releases after v4.0.0, containing a significant number of fixes (v4.0.1 and v4.0.2).
But this summary is just scratching the surface. We have accepted 206 commits from 78 different contributors. We have changed 3,031 files with 96,616 additions and 85,768 deletions.
## Our roadmap intent for June
_(We'll do our best, no guarantee!)_
- We will release an improved Slider component with range support. You can already [preview it](https://deploy-preview-15703--material-ui.netlify.app/components/slider/).
- We will work on a new Tree View component. You can already [preview it](https://deploy-preview-14827--material-ui.netlify.app/components/tree-view/).
- We will add more themes to the [premium theme marketplace](https://mui.com/store/).
- We will start exploring how we can provide style adapters in v5 (styled-components, JSS, linaria, naked, etc.)
- We will experiment around advisory offerings for enterprises.
If you are an enterprise and are looking for one of the following:
- A dedicated communication channel giving priority access to MUI engineers.
- Architecture Reviews. Sit down with a MUI engineer and walk through all aspects of your MUI project and current tech stack or architecture, to identify issues and opportunities for improvement.
You can contact us at [email protected].
- ❓ Please upvote our [GitHub issues](https://github.com/mui/material-ui/issues) if you want something specific. The number of 👍 helps us to prioritize.
| 4,190 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/blog/michal-dudak-joining.js | import * as React from 'react';
import TopLayoutBlog from 'docs/src/modules/components/TopLayoutBlog';
import { docs } from './michal-dudak-joining.md?@mui/markdown';
export default function Page() {
return <TopLayoutBlog docs={docs} />;
}
| 4,191 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/blog/michal-dudak-joining.md | ---
title: Michał Dudak joins MUI
description: We are excited to share that Michał Dudak has joined MUI.
date: 2021-06-14T00:00:00.000Z
authors: ['oliviertassinari']
card: true
tags: ['Company']
---
We are excited to share that [Michał Dudak](https://twitter.com/michaldudak) has joined MUI!
He started a couple of days ago full-time and is part of the core components team.
Before joining MUI, Michał worked as a full-stack engineer and software architect at Future Processing, a high-end development agency in Poland.
He has been a professional practitioner in the field for over a decade.
He admires great designs and clever solutions.
Creating with TypeScript and CSS is a pleasure for him.
We were impressed by his technical challenge.
He leveraged most of the best practices we enforce when writing components, without prior experience contributing to our codebase.
While we can't predict the future, Michał is currently responsible for the development of a new vertical for MUI: the unstyled & headless React components.
Marija initiated this effort with a couple of new modules under the [@mui/base](https://unpkg.com/browse/@mui/base@latest/) package.
This is a strategic effort for us, with the intent to solve two problems:
1. Share logic between Material Design and the second design specification that [Jun will work on](/blog/siriwat-kunaporn-joining/). This is important to stay efficient.
2. Grow the audience of the library. It provides a new customization tradeoff. It maximizes freedom and minimizes bundle-size. We have recently exceeded [20%](https://docs.google.com/spreadsheets/d/1l5j3Xjtvm9XZtmb4ulLiWElQaXSlZlyCWT5ONrQMpBo/edit#gid=0) market share of the React ecosystem (@mui/material downloads divided by react-dom downloads). We're aiming for [+20%](https://npm-stat.com/charts.html?package=@angular/core,@angular/material,@angular/cdk) of the market coming from this effort in the next four years.
Michał is the third of a series of five new positions we have recently opened and filled.
We will reach 11 people by the end of June.
We have opened these positions as our revenue growth allows.
These new roles will help accelerate our mission, strengthen our existing offering, and initiate a new vertical.
You can find the next positions we aim to fill in [the Career page](https://mui.com/careers/#open-roles).
We couldn't be more excited to have Michał on the team!
| 4,192 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/blog/mui-core-v5-migration-update.js | import * as React from 'react';
import TopLayoutBlog from 'docs/src/modules/components/TopLayoutBlog';
import { docs } from './mui-core-v5-migration-update.md?@mui/markdown';
export default function Page() {
return <TopLayoutBlog docs={docs} />;
}
| 4,193 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/blog/mui-core-v5-migration-update.md | ---
title: Why you should migrate to Material UI v5 today
description: We have completely revamped our Migration guide to reduce friction when upgrading to v5. Get started now!
date: 2022-06-20T00:00:00.000Z
authors: ['samuelsycamore']
card: true
tags: ['MUI Core']
---
Are you still using Material UI v4 in 2022?
What are you thinking?! 😛 Don't get left behind!
We [released v5 in late 2021](/blog/mui-core-v5/), and since then, we've seen [a steady migration of users](https://npm-stat.com/charts.html?package=@mui/material,@material-ui/core) over to the new packages.
This is exciting for us, because we're super proud of all the improvements that were shipped with v5.
But it seems as though a fair share of users are still hesitant to make the jump.
This could be because v5 contains many breaking changes from v4, so the migration can be a large undertaking.
That's why we've completely revamped our [v4 -> v5 migration guide](/material-ui/migration/migration-v4/)—to help reduce the amount of friction you might encounter when updating to v5.
We hope it helps!
Be sure to check out [the updated migration guide](/material-ui/migration/migration-v4/) in the Material UI docs.
## Why you should upgrade to v5
Here are the top 5 reasons why you should upgrade to v5 ASAP.
### 1. React 18 support
Material UI v5 is the only version that fully supports [React 18](https://legacy.reactjs.org/blog/2022/03/29/react-v18.html), so you'll need to update if you want to take advantage of the latest and greatest React features.
### 2. New style engine
One of the biggest changes in v5 is the replacement of JSS with [Emotion](https://emotion.sh/docs/introduction) as the default style engine.
This offers significant advancements in performance when it comes to dynamic styles, and we also believe that it leads to a much more enjoyable developer experience.
Emotion unlocks many new customization options that developers had been requesting for years, such as custom style utility props, color variants, and custom theme variants.
Check out [this RFC on GitHub](https://github.com/mui/material-ui/issues/22342) for details about this change.
<a href="https://github.com/mui/material-ui/issues/22342"><img src="/static/blog/mui-core-v5-migration-update/style-engine.png" alt="Screenshot of the new style engine GitHub issue in Material UI's repository" style="width: 692px; aspect-ratio: 2/1;" loading="lazy" /></a>
Keep in mind that the new style engine is 100% [incrementally adoptable](/material-ui/migration/migrating-from-jss/): you can use JSS and Emotion together in the same app while migrating your components over.
### 3. Better customization tools
Material UI v5 introduces the `sx` prop, which opens up a whole new realm of possibility for applying custom styles.
Now you can apply style rules to individual components without needing to involve the `styled()` API, which would be overkill when dealing with one-off styles.
The `sx` prop lets you work with a superset of CSS, making it very intuitive to pick up and start using if you're already comfortable with CSS.
```tsx
import * as React from 'react';
import Box from '@mui/material/Box';
export default function BoxSx() {
return (
<Box
sx={{
width: 300,
height: 300,
backgroundColor: 'primary.dark',
'&:hover': {
backgroundColor: 'primary.main',
opacity: [0.9, 0.8, 0.7],
},
}}
/>
);
}
```
### 4. IntelliSense prop descriptions
All prop descriptions are now written in TypeScript, which means that you can access details about the usage of a given prop right inside of your IDE—no need to seek out the official documentation to find this information.
<img alt="Screenshot of IntelliSense tooltip showing the details about the Material UI Badge component" src="/static/blog/mui-core-v5-migration-update/intellisense-tooltip.png" style="width: 692px; aspect-ratio: 2/1;" loading="lazy" />
### 5. Upcoming CSS variables support
[CSS variables](https://developer.mozilla.org/en-US/docs/Web/CSS/Using_CSS_custom_properties) will help us solve a lot of customization issues in the future.
One of them is the dark mode flashing issue that has been requested for a long time.
More importantly, this feature is opt-in if you are using Material UI v5!
You can check out the progress on this effort [in this GitHub issue](https://github.com/mui/material-ui/issues/32049).
## Upgrade now
What are you waiting for?
Jump into the [newly revised migration documentation](/material-ui/migration/migration-v4/) and get started today.
Let us know if you have any questions along the way!
| 4,194 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/blog/mui-core-v5.js | import * as React from 'react';
import TopLayoutBlog from 'docs/src/modules/components/TopLayoutBlog';
import { docs } from './mui-core-v5.md?@mui/markdown';
export default function Page() {
return <TopLayoutBlog docs={docs} />;
}
| 4,195 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/blog/mui-core-v5.md | ---
title: Introducing MUI Core v5
description: After over 400 days of development and over 40 canary releases, we are excited to introduce MUI Core v5.0.0!
date: 2021-09-16T00:00:00.000Z
authors:
[
'oliviertassinari',
'eps1lon',
'mnajdova',
'michaldudak',
'siriwatknp',
'danilo-leal',
'mbrookes',
]
card: true
tags: ['News']
---
After over 400 days of development and over 40 canary releases, we are excited to introduce [MUI Core v5.0.0](https://github.com/mui/material-ui/releases/tag/v5.0.0)!
<img src="/static/blog/mui-core-v5/card.png" alt="" style="width: 100%; margin-bottom: 16px;" />
This release features some major highlights:
- [High-level goals for v5](#high-level-goals-for-v5)
- [A new brand](#a-new-brand)
- [Improved customizability](#improved-customizability)
- [Migration from JSS to emotion](#migration-from-jss-to-emotion)
- [The sx prop](#the-sx-prop)
- [Dynamic props](#dynamic-props)
- [Global class names](#global-class-names)
- [Unstyled components (alpha)](#unstyled-components-alpha)
- [Improved DX](#improved-dx)
- [Smaller demos in the docs](#smaller-demos-in-the-docs)
- [Props descriptions in IntelliSense](#props-descriptions-in-intellisense)
- [Migration from Enzyme to Testing Library](#migration-from-enzyme-to-testing-library)
- [TypeScript migration](#typescript-migration)
- [Strict Mode support](#strict-mode-support)
- [A new product line: X](#a-new-product-line-x)
- [Data Grid](#data-grid)
- [Date Picker](#date-picker)
- [New components](#new-components)
- [Improved Grid](#improved-grid)
- [More Material Design icons](#more-material-design-icons)
- [Stack](#stack)
- [Promotion from the lab](#promotion-from-the-lab)
- [New in the lab](#new-in-the-lab)
- [v4 migration](#v4-migration)
- [Change of the package names](#change-of-the-package-names)
- [Change of the styling solution](#change-of-the-styling-solution)
- [Changes to the supported platforms](#changes-to-the-supported-platforms)
- [Design kits](#design-kits)
- [What's next?](#whats-next)
- [A public roadmap](#a-public-roadmap)
- [Unstyled components and hooks](#unstyled-components-and-hooks)
- [Second design system](#second-design-system)
- [MUI X](#mui-x)
- [Design kits](#design-kits-1)
- [Thank you](#thank-you)
## High-level goals for v5
In our last survey, the number of developers that commented about improving the Material Design implementation was down by [60%](https://mui.com/blog/2020-developer-survey-results/#comparison-with-last-year) compared to the year before.
At the same time, 5X more developers were struggling to customize the components.
It is based on this context that we started to work on v5 in 2019.
Our primary focus was to revamp the **customization Developer Experience (DX)**.
It had become clear that design (aesthetic, UX) and DX were key to unlocking the next stage of growth.
The last major iteration on the library was completed with v4, released [two-and-a-half years ago](https://mui.com/blog/material-ui-v4-is-out/),
meaning over a year without innovation.
So, we have approached v5 with a focus on delivering **long-term value**.
For instance, we stopped all development on v4 as soon as we started to work on v5,
and have taken the liberty of introducing breaking changes anytime we have identified a long-term upside.
You can find the initial RFC plan for v5 in [issue #20012](https://github.com/mui/material-ui/issues/20012).
## A new brand
Material UI is now **MUI**! Head to the [dedicated blog post](https://mui.com/blog/material-ui-is-now-mui/) to learn more.
We hope you are going to enjoy the DX improvement of only having to type 3 letters to type to find us on the internet: [mui.com](https://mui.com) and to import us from npm `@mui`!
## Improved customizability
### Migration from JSS to emotion
The first step we took to improve the customization experience was to rethink the styling solution from a blank page.
If you have been following MUI for a long time, you have probably noticed that we have iterated (a lot!) on the styling solution over the last seven years.
We started with Less, then inline-styles, then JSS, and now emotion. Why change it again? We wanted to solve the following **problems**:
1. The React community is settling on `styled()` as the **most popular** CSS-in-JS API. We have used popularity as a proxy for "best".
```jsx
const StyledDiv = styled('div')({
color: 'red',
});
// or
const StyledDiv = styled.div`
color: red;
`;
```
<p class="blog-description"><a href="https://codesandbox.io/s/elastic-yonath-uedfv?file=/src/App.js">CodeSandbox</a></p>
You can find it in [styled-components](https://styled-components.com/), [emotion](https://emotion.sh/docs/styled), [goober](https://goober.js.org/), [stitches](https://stitches.dev/docs/api#styled), or [linaria](https://linaria.dev/).
While MUI is compatible with any styling solution (as long as the styles have more specificity, for example, Tailwind CSS), many developers still felt the need to learn something new: the [`makeStyles`](https://mui.com/system/styles/basics/#hook-api) API.
2. Our React integration with JSS (`@mui/styles`) is **too slow** to unlock the next layer of customization DX we aim for.
The static CSS generation using v4 was fast enough, even [faster](https://codesandbox.io/s/nb05w?file=/src/App.js) than emotion,
however, the dynamic style generation was too slow to be used in production. We would have needed to reimplement it.
3. Many developers were advocating for MUI to [migrate to styled-components](https://github.com/mui/material-ui/issues/6115),
which would allow us to drop the custom React JSS wrapper we maintain.
From our experience, maintaining a custom styling solution takes a considerable amount of time.
After [exploring](https://github.com/mui/material-ui/issues/22342) many different options, we settled on what we believe is a great tradeoff to **solve** the above issues:
1. We have made `styled()` the lowest level primitive to add styles.
This API is already known by many.
2. We have defined a common interface with concrete implementations:
- `@mui/styled-engine`: implemented with Emotion (default).
- `@mui/styled-engine-sc`: implemented with styled-components
- If you are using a different styling library, feel free to contribute a wrapper. For instance, there is [one attempt with goober](https://github.com/mui/material-ui/pull/27776), a library obsessing on bundle size (3kB gzipped).
This allows developers to swap between different style engines. For example, styled-components users no longer need to bundle Emotion **and** styled-component, nor do they need to configure the server-side rendering for each.
How does the [swap work](https://mui.com/material-ui/guides/styled-components/)? The same way it does from React to Preact.
3. For the last couple of months, we have been [sponsoring](https://opencollective.com/emotion) Emotion with a $100/month grant. We are now increasing this amount to $1,000/month. It's in our best interest to help ensure the library keeps pushing the envelope, leading the state of the art in a competitive space.
The first immediate benefit of the move to Emotion was **performance**. The `<Box>` component is [x5-x10 more performant](https://codesandbox.io/s/zlh5w?file=/src/App.js) in v5, compared to v4.
We would like to thank all the community contributors that made the migration of the components and documentation possible in [#24405](https://github.com/mui/material-ui/issues/24405) and [#16947](https://github.com/mui/material-ui/issues/16947): [@natac13](https://github.com/natac13), [@vicasas](https://github.com/vicasas), [@mngu](https://github.com/mngu), [@kodai3](https://github.com/kodai3), [@xs9627](https://github.com/xs9627), [@povilass](https://github.com/povilass), [@duganbrett](https://github.com/duganbrett), [@queengooborg](https://github.com/queengooborg), and more.
It was a major undertaking!
Going forward, developers can either keep using JSS with the legacy `@mui/styles` package [or migrate from JSS](https://mui.com/material-ui/migration/migrating-from-jss/).
We recommend the latter to match the core components.
### The sx prop
While the `styled()` API is great to style complex components or to create highly reused components, there are cases where it's overkill.
We started to [explore](https://medium.com/material-ui/introducing-material-ui-design-system-93e921beb8df) this **problem** three years ago with the introduction of the `<Box>` component to solve the following concerns:
1. **Switching context** wastes time.
The styled API forces you to constantly jump between the use of the styled components and where they are defined.
Could we move the style descriptions right where we need them?
2. **Naming things** is hard.
Have you ever found yourself struggling to find a good name for a styled component?
Could we remove the need to create and name yet another component?
3. **Enforcing consistency** in UIs is hard.
This is especially true when more than one person is building the application, as there has to be some coordination amongst members of the team regarding the choice of design tokens and how they are used, what parts of the theme structure should be used with what CSS properties, and so on.
In v5, we have pushed the solution one step further with the `sx` prop.
The prop is now available on **all** the components (made possible by emotion).
It exposes a superset of the CSS API: the normal CSS properties, shorthands, and media query helpers.
For instance, you can add one unit of vertical margin with:
```jsx
// add margin: 8px 0px;
<Slider sx={{ my: 1 }} />
```
<p class="blog-description"><a href="https://codesandbox.io/s/nostalgic-williams-zmo5r?file=/src/App.js">CodeSandbox</a></p>
Developers already seem to [love it](https://twitter.com/AnsonLowZF/status/1397034690771443715).
You can find a [side-by-side comparison](https://mui.com/system/getting-started/usage/#why-use-mui-system) of `styled()` vs. `sx` in the documentation to determine when you should use the prop.
Some developers use `sx` for everything, others only in simple cases.
The four components categorized as CSS utilities: Box, Grid, Typography, and Stack pushes the approach one step further.
They expose a subset of the `sx` prop as flat props, for instance:
```jsx
<Typography color="grey.600">
// is equivalent to
<Typography sx={{ color: 'grey.600' }}>
```
<p class="blog-description"><a href="https://codesandbox.io/s/keen-worker-zo2r3?file=/src/App.tsx">CodeSandbox</a></p>
See the [API tradeoff](https://mui.com/system/getting-started/usage/#api-tradeoff) section of the documentation for why not all the components accept these flat props.
### Dynamic props
React is about composition. Developers can import one component, extend it, and re-export the wrapper.
It's how developers have extended the core components up until v4. However:
1. Each time you create a new component, it's another import option for your team.
Now, you have to ensure that the right component is imported.
2. Adding a new `color="success"` prop to a Button component requires non-trivial CSS customizations.
How do you ensure that all the styles (hover, focus, focus-visible) are consistent with the other built-in colors?
3. It adds a boilerplate.
For this reason, v5 comes with the capability to extend the built-in behavior of the components, right from the theme.
This was one of the most upvoted GitHub issues: [#13875](https://github.com/mui/material-ui/issues/13875).
In practice, this change makes the MUI Core components extendable placeholders.
**First**, you can use the [existing style mapping](/material-ui/customization/palette/#custom-colors) of the components.
For example, you can add a new `neutral` color to the palette, and the Button computes the right derivative colors.
```jsx
import { createTheme, Button } from '@mui/material';
// 1. Extend the theme.
const theme = createTheme({
palette: {
neutral: {
main: '#d79b4a',
},
},
});
// 2. Notify TypeScript about the new color in the palette
declare module '@mui/material/styles' {
interface Palette {
neutral: Palette['primary'];
}
interface PaletteOptions {
neutral: PaletteOptions['primary'];
}
}
// 3. Update the Button's color prop options
declare module '@mui/material/Button' {
interface ButtonPropsColorOverrides {
neutral: true;
}
}
// 4. Profit
<Button color="neutral" />
```
<p class="blog-description"><a href="https://codesandbox.io/s/stupefied-mclaren-ho4zs?file=/src/App.tsx">CodeSandbox</a></p>
**Second**, you can add [custom variants](/material-ui/customization/theme-components/#creating-new-component-variants) to the theme, overriding the CSS for specific component prop combinations.
```jsx
import { createTheme, Button } from '@mui/material';
// 1. Extend the theme.
const theme = createTheme({
components: {
MuiButton: {
variants: [
{
props: { variant: 'dashed', color: 'error' },
style: {
border: '1px dashed red',
color: 'red',
}
}
]
}
}
});
// 2. Update the Button's color prop options
declare module '@mui/material/Button' {
interface ButtonPropsVariantOverrides {
dashed: true;
}
}
// 3. Profit
<Button variant="dashed" color="error">
dashed
</Button>
```
<p class="blog-description"><a href="https://codesandbox.io/s/sharp-sky-xwz3d?file=/src/App.tsx">CodeSandbox</a></p>
### Global class names
In v3, we heard how frustrating using the `classes` prop API correctly can sometimes be.
In v4, we made [a step](https://mui.com/blog/material-ui-v4-is-out/#customization) towards adding global class names.
They are present, as long as no more than one ThemeProvider is used.
v5 doubles down on this direction by always adding global class names on the host DOM nodes.
These class names are available for customizing the child elements,
which can simplify the customization of complex components.
For example, compare these three options to turn the outlined input's border color red:
```tsx
import TextField from '@mui/material/TextField';
import { outlinedInputClasses } from '@mui/material/OutlinedInput';
import { styled } from '@mui/material/styles';
// Option 1: global class
const CustomizedTextField1 = styled(TextField)({
'& .MuiOutlinedInput-notchedOutline': {
borderColor: 'red',
},
});
// Option 2: global class + const
const CustomizedTextField2 = styled(TextField)({
[`& .${outlinedInputClasses.notchedOutline}`]: {
borderColor: 'red',
},
});
// Option 3: classes prop (before)
const CustomizedTextField3 = styled((props) => (
<TextField
{...props}
variant="outlined"
InputProps={{ classes: { notchedOutline: 'foo' } }}
/>
))({
'& .foo': {
borderColor: 'red',
},
}) as typeof TextField;
```
<p class="blog-description"><a href="https://codesandbox.io/s/zealous-dawn-0yr4g?file=/src/App.tsx">CodeSandbox</a></p>
Option 1 is the simplest but if you want more type safety and do not use a magic string (`MuiOutlinedInput-notchedOutline`), you can use Option 2.
### Unstyled components (alpha)
While hooks were high-risk experimentation when React released them in 2018, they are now ubiquitous.
This is a great opportunity for MUI to expose more flexibility: headless components.
A key reason why developers pick MUI is to be able to build UIs faster.
When they depend on us, they make a tradeoff.
They estimate that applying new styles on top of the Material Design components will be faster than creating components from scratch or picking another library.
They estimate that it will be performant enough, and they won't miss too much freedom.
This tradeoff works **really well** when having a small, constrained engineering team or a large team building internal (/secondary) tools.
But what about the medium/large size engineering team that works on ambitious projects? Shouldn't they have a better option for not including Material Design and maximizing freedom than building the components from scratch?
We have started working on this exact problem,
isolating the logic of the Material Design components into hooks and unstyled components.
While the effort is still in alpha, you can already find the first building blocks in a new Base package.
So far it features:
- [Autocomplete](/material-ui/react-autocomplete/#useautocomplete)
- [Button](/material-ui/react-button/#unstyled)
- [Modal](/material-ui/react-modal/#unstyled)
- [Pagination](/material-ui/react-pagination/#usepagination)
- [Slider](/material-ui/react-slider/#unstyled)
- [Switch](/material-ui/react-switch/#unstyled)
```jsx
const CustomButton = React.forwardRef(function CustomButton(
props: ButtonUnstyledProps,
ref: React.ForwardedRef<any>,
) {
const { children } = props;
const { active, disabled, focusVisible, getRootProps } = useButton({
...props,
ref,
component: CustomButtonRoot,
});
const classes = {
active,
disabled,
focusVisible,
};
return (
<CustomButtonRoot {...getRootProps()} className={clsx(classes)}>
{children}
</CustomButtonRoot>
);
});
```
<p class="blog-description"><a href="https://codesandbox.io/s/7lc1r?file=/demo.tsx">CodeSandbox</a></p>
We discuss the effort in [#6218](https://github.com/mui/material-ui/issues/6218).
You can use [#27170](https://github.com/mui/material-ui/issues/27170) to follow our progress.
## Improved DX
### Smaller demos in the docs
We have used the migration of the demos from JSS to Emotion as an opportunity to rework them.
Many of the demos were originally added taking into account how they would help maintainers work on the components.
Instead, we have reversed the priority, putting the developers using them [first](https://github.com/mui/material-ui/issues/22484).
In practice, this means breaking down complex demos into smaller ones.
We aim to have as many "inline previews" as possible. It saves one click to expand the demo, and the mental overhead of figuring out what part of the code maps with what of interest you saw on the screen.
<a href="/material-ui/react-button/#basic-button"><img loading="lazy" src="/static/blog/mui-core-v5/inline-preview.png" alt="Screenshot of the new code inline preview in our docs" style="width: 649px; margin-bottom: 16px;" /></a>
### Props descriptions in IntelliSense
The best documentation is the one you don't need to open.
We have moved all the prop descriptions to TypeScript, so IntelliSense in your editor can show you more context.
<img loading="lazy" src="/static/blog/mui-core-v5/prop-descriptions.png" alt="Screenshot of the added prop descriptions due to IntelliSense" style="width: 649px;" />
<p class="blog-description">The popup explains what the `forcePopupIcon` prop is for.</p>
These TypeScript prop descriptions are also used to generate the [API pages](https://mui.com/material-ui/api/autocomplete/#props) of the documentation, so there is a single source of truth.
### Migration from Enzyme to Testing Library
The migration of MUI from class components [to hooks in v4](https://mui.com/blog/material-ui-v4-is-out/#preparing-for-the-future) broke many of the tests we had written with [Enzyme](https://github.com/enzymejs/enzyme/).
Our tests were too coupled with the internals of React.
We decided to transition our tests suite to [Testing Library](https://testing-library.com/).
Fast forward a couple of years, Testing Library is now [the most popular](https://npm-stat.com/charts.html?package=enzyme&package=%40testing-library%2Freact&from=2020-09-13&to=2021-09-13) option to test React components in the community.
We are happy to report that we have migrated **all** our test codebase to Testing Library.
You can use our tests as inspiration when you need to write new ones.
The migration has even allowed us to rethink some of the implementations, making the components easier to test with the library.
### TypeScript migration
The MUI Core codebase is not completely written in TypeScript yet but we have been coming a long way ([MUI X](https://github.com/mui/mui-x) is).
In v4, we have written all the demos TypeScript first.
With v5, we have made new steps toward the adoption of TypeScript:
- We have made the TypeScript definitions the source of the API pages.
This reduces the likeliness for a new release to include out-of-date definitions.
- We have migrated our first component to be written in TypeScript.
- We are writing most of the new code in TypeScript.
Overall, the language stats of GitHub give some qualitative measure of the progress:
- 02/2019: 1.6%
- 03/2020: 3.2%
- 07/2020: 5.3%
- 10/2020: 25.4%
- 07/2021: 35.4%
- Today: 36.1%
<img loading="lazy" src="/static/blog/mui-core-v5/typescript.png" alt="Screenshot of our current language distribution. 36.1% TypeScript, 63.9% JavaScript." style="width: 700px; margin-bottom: 16px;" />
We expect the adoption of TypeScript to increase during the lifecycle of v5.
With this organic adoption strategy, it might take us two years to close [#15984](https://github.com/mui/material-ui/issues/15984).
### Strict Mode support
This release is compatible with `React.StrictMode`.
This is the result of two years of work on the infrastructure.
We now run the tests and the documentation in strict mode.
Thanks for the patience, this has been an old and [frequently requested](https://github.com/mui/material-ui/issues/13394) improvement.
Bonus point, we run [React v18](https://github.com/reactwg/react-18) (unreleased) in a nightly build, in strict mode, without any test failures.
> ⚠️ `@mui/styles` is not compatible with strict mode nor concurrent features.
## A new product line: X
<img loading="lazy" src="/static/blog/mui-core-v5/mui-x-blog-hero.png" alt="Mockup of some MUI X components" style="width: 700px; margin-bottom: 16px;" />
We are very excited to introduce a new product line to the MUI family: **[MUI X](/x/)**!
We have recently released our [first stable version](https://github.com/mui/mui-x/releases/tag/v4.0.0).
MUI X embodies our initiative to solve the main pain point developers have reported two years in a row during our developer's survey: [2020](/blog/2020-developer-survey-results/#5-how-can-we-improve-mui-for-you), [2019](/blog/2019-developer-survey-results/#4-how-can-we-improve-mui-for-you).
We have heard you, you want **more components**.
But, in practice, we wouldn't probably cover all the possible components you might need. It would be a titanic task.
Instead, we are focusing on the **hardest** and **most requested** components, leaving the long tail to our [community of contributors](/material-ui/discover-more/related-projects/#components).
We started working on this effort over a year ago, in a new GitHub repository: [mui/mui-x](https://github.com/mui/mui-x).
You might wonder, why work on it as a different product? Building a great data grid or charting solution takes a considerable amount of time. Taking on the challenge of developing them required us to think about a different monetization strategy and we quickly realized that the team working on MUI X would need to become, at least, two times larger than the one working on MUI Core, which already has the community contribution.
Although each product has its unique vision and mission statements, they complement each other. A solid MUI Core foundation is essential for the MUI X adoption.
- **MUI Core:**
- Vision: Create robust foundations to build UI components. "Robust" is measured by how many developers decide to depend on it.
- Mission: Unlock design skills to developers while allowing them to build UIs fast.
- **MUI X:**
- Vision: Create the last UI component library developers will ever need. High quality, consistent, feature-rich, and covering the most frequent/challenging use-cases.
- Mission: Make building rich, data-intensive, dynamic apps a breeze.
MUI Core has a positive cash flow thanks to its paid templates, design assets, ads on the documentation, and backers/sponsors (❤️). The [MIT](https://tldrlegal.com/license/mit-license) license model works great for it.
However, none of these revenue sources would scale with the outcome and amount of work required for MUI X.
It's why we are using an [open core license model](https://en.m.wikipedia.org/wiki/Open-core_model) for this new product.
The X components come in [three different plans](https://mui.com/pricing/):
- **Community.** This plan contains the MIT components that are sustainable by the contributions of the open-source community. Free forever.
- **Pro.** This plan contains the features that are at the limit of what the open-source model can sustain. For instance, providing a very comprehensive set of components. From a price perspective, the plan is designed to be accessible to most professionals.
- **Premium.** This plan contains the most advanced features.
Let's have a look at our first component:
### Data Grid
We have started the `DataGrid` and `DataGridPro` components more than a year ago with the ambition to deliver the best-in-class React data grid.
To achieve this we have a twin licensing model.
The `DataGrid` component is available under an MIT license for the features that can be relatively easily implemented, and that can be sustained with an open-source model.
The `DataGridPro` on the other hand is available under a paid commercial license for the more advanced features.
<a href="/x/react-data-grid/demo/"><img loading="lazy" src="/static/blog/mui-core-v5/data-grid.gif" alt="Screen recording of the Data Grid component demo" style="width: 700px; margin-bottom: 16px;" /></a>
<a href="/x/react-data-grid/demo/"><p class="blog-description">Check the Data Grid demo here.</p></a>
### Date Picker
We have transferred the ownership of the `@material-ui/pickers` from [Dmitriy Kovalenko](https://github.com/dmtrKovalenko) to the main organization.
The date picker components are now part of the `@mui/lab` package.
We spent a lot of time making sure they are consistent.
We are now working toward reaching the same level of excellence as the other core components.
These were our first TypeScript components in the codebase.
The date range picker will be part of the Pro plan, while the other date picker components are MIT licensed.
## New components
This release comes with eight new components!
### Improved Grid
The development of the Grid was mostly put on hold for the last three years, blocked by the size of the statically generated CSS with JSS.
The [migration to emotion](#migration-from-jss-to-emotion) has unlocked the following frequently requested changes:
Support for [row & column](/material-ui/react-grid/#row-amp-column-spacing) spacing:
```jsx
<Grid container rowSpacing={1} columnSpacing={2} />
```
Support for [responsive values](/material-ui/react-grid/#responsive-values) on all the props:
```jsx
<Grid container spacing={{ xs: 2, md: 3 }} />
```
Support for a different [number of columns](/material-ui/react-grid/#columns) than 12:
```jsx
<Grid container columns={16}>
```
An alternative implementation that uses [CSS grid](/material-ui/react-grid/#css-grid-layout):
```jsx
<Box display="grid" gridTemplateColumns="repeat(12, 1fr)" gap={2}>
<Box gridColumn="span 8">
<Item>xs=8</Item>
</Box>
<Box gridColumn="span 4">
<Item>xs=4</Item>
</Box>
<Box gridColumn="span 4">
<Item>xs=4</Item>
</Box>
<Box gridColumn="span 8">
<Item>xs=8</Item>
</Box>
</Box>
```
### More Material Design icons
The Material Design team at Google has released 600 new icons in five different themes since we released v4.
We have made them [available](/material-ui/material-icons/) in the `@mui/icons-material` package.
### Stack
We have introduced a new `<Stack>` component
to handle one-dimensional layouts. It's's similar to how Figma handles auto-layout.
<a href="/material-ui/react-stack/"><img loading="lazy" src="/static/blog/mui-core-v5/stack.png" alt="Screenshot of the Stack component and its code preview" style="width: 700px; margin-bottom: 16px;" /></a>
> Note that you might already be using `<Box display="flex" gap={1}>` to solve the same problem,
> however, [browser support](https://caniuse.com/flexbox-gap) for the flexbox `gap` CSS property is lacking in Safari.
You can find [more details](/material-ui/react-stack/) in the documentation.
### Promotion from the lab
We have moved six components from the lab to the main component package, after over two years iterating on feedback:
- [Autocomplete](/material-ui/react-autocomplete/)
- [Pagination](/material-ui/react-pagination/)
- [Rating](/material-ui/react-rating/)
- [Skeleton](/material-ui/react-skeleton/)
- [Speed Dial](/material-ui/react-speed-dial/)
- [Toggle Button](/material-ui/react-toggle-button/)
### New in the lab
The lab hosts the incubator components that are not yet ready to move to the core.
The main difference between the lab and the core is how the components are versioned.
Having a separate lab package allows us to release breaking changes when necessary while the core package follows a [slower cadence](https://mui.com/versions/#release-frequency).
The following components are now available in the lab:
- [LoadingButton](/material-ui/react-button/#loading-button). It does what you would expect. It renders the `Button` with a configurable loading/pending state.
- [FocusTrap](/base-ui/react-focus-trap/). This component traps the keyboard focus within a DOM node. For example, it's used by the Modal to prevent tabbing out of the component for accessibility reasons.
- [Masonry](/material-ui/react-masonry/). One great use case for this component is when using the `Grid` component leads to wasted space. It's frequently used in dashboards.
<a href="/material-ui/react-masonry/"><img loading="lazy" src="/static/blog/mui-core-v5/masonry.png" alt="Screenshot of the Masonry component and its code preview" style="width: 700px; margin-bottom: 16px;" /></a>
## v4 migration
We have been meticulous to minimize the pain on the migration from v4 to v5.
We know how daunting an upgrade can be.
We have used all the tools at our disposal.
We have [worked with the React core team](https://github.com/facebook/react/pull/20463) to make React DevTools display warnings directly in the components panel.
This should make it easier to find where components need to be updated for v5.
See this [CHANGELOG section](https://github.com/facebook/react/blob/main/packages/react-devtools/CHANGELOG.md#expose-dev-mode-warnings-in-devtools-ui) for more details on it.
In the following sections, we will cover some high-level changes required for a successful upgrade.
We have documented all the breaking changes, we have added as many deprecations as we could, we wrote codemods to automate the laborious tasks, and more!
If you are starting your upgrade, these are the three things you should look into:
- ⚓ We have introduced actionable deprecations in v4.
You can upgrade to v4.12.0 and start preparing your codebase to be compatible with v5.
- ⚒️ We have prepared a [codemod](https://mui.com/material-ui/migration/migration-v4/#preset-safe) that does most of the transformations you will need for the migration.
If you are not familiar with what a codemod is, check out [Effective Refactoring with Codemods by Edd Yerburgh](https://www.youtube.com/watch?v=H9qtLutnT_g&ab_channel=Pusher).
- 📄 Lastly, we have prepared a step-by-step [migration guide](https://mui.com/material-ui/migration/migration-v4/).
This guide is the one place where you can find all information required for upgrading to v5.
### Change of the package names
To support our [new brand](https://mui.com/blog/material-ui-is-now-mui/), we changed some of the terminology used in the project.
The npm packages have been renamed.
For more details on this, check [the migration guide](https://mui.com/material-ui/migration/migration-v4/).
### Change of the styling solution
We have [replaced JSS with emotion](#migration-from-jss-to-emotion) as a default styling solution while adding support for styled-components at the same time.
We recommend migration your customization from JSS/`makeStyles`/`withStyles` to the new APIs: `styled` and the `sx` prop.
If you are not ready to migrate away from the `makeStyles` API now, you can:
- add `@mui/styles` as a dependency and change the imports of the `makeStyles`/`withStyles` utilities
- use [`tss-react`](https://github.com/garronej/tss-react) - its API is similar to JSS `makeStyles` but is powered by emotion, which minimizes the bundle duplication with the core components.
You can find more information for this on the [Migrate from JSS](https://mui.com/material-ui/migration/migrating-from-jss/) section of the migration guide.
### Changes to the supported platforms
This breaking change is an opportunity to drop the support of legacy upstream dependencies.
- We have updated the minimum supported TypeScript version from 3.2 to **3.5**.
This aims to match the policy of [DefinitelyTyped](https://github.com/DefinitelyTyped/DefinitelyTyped), with versions of TypeScript that are less than two years old.
- We have updated the minimum supported node.js version from 8.0 to **12.17**.
This aims to match the [LTS versions that are in maintenance](https://github.com/nodejs/Release#release-schedule) mode.
- We have updated the minimum supported React version from 16.8 to **17.0**.
The breaking changes released between the two versions are [very limited](https://legacy.reactjs.org/blog/2020/10/20/react-v17.html).
- We have updated the supported browsers.
- IE: **partial**. We have kept the logic added in the past to support IE 11,
however, we have stopped actively working on it. We can't guarantee that it works correctly. It's discontinued.
- Edge: from 14 to **91**. The minimum version based on Chromium.
- Firefox: from 52 to **78**.
- Chrome: from 49 to **90**. We have [assumed](https://developers.google.com/search/blog/2019/05/the-new-evergreen-googlebot) that Googlebot is always using the latest version of Chrome.
- Safari: from 10 to **12.5**
These changes have allowed us to save [6 kB gzipped](https://github.com/mui/material-ui/pull/22814#issuecomment-700995216) on the `@mui/material` package.
## Design kits
We now have design kits for the MUI components available in the three main design tools out there: [Figma](https://mui.com/store/items/figma-react/), [Sketch](https://mui.com/store/items/sketch-react/), and [Adobe XD](https://mui.com/store/items/adobe-xd-react/). If you work together with a designer or team of designers, having them use the design kits makes for easier communication, as you'll be speaking the same language around the components. It'll also help designers to understand how the library is structured, especially theming features and each component prop, enabling much faster development.
<a href="https://mui.com/store/#design"><img loading="lazy" src="/static/blog/mui-core-v5/design-kits.png" alt="Screenshot of buttons in the Figma design kit" style="width: 700px; margin-bottom: 16px;" /></a>
<p class="blog-description">The design kits</p>
Figma is the first design kit that benefits from the v5 update, and we're more excited than ever to get the kits into designers' hands! We understand that designers are generally more creative and productive when their physical and digital work environment is looking fresh — that is why our kits are now cleaner in every aspect, leveraging naming, easy component-showcasing, and consistency.
Some major changes to the components:
- We've added the new colors that v5 introduces (error, warning, info & success)
- All new components are covered
- States such as hover have been added for all relevant components
## What's next?
Looking back, we are glad to say that, together, we have accomplished most of the objectives we defined in the [v4 release blog post](https://mui.com/blog/material-ui-v4-is-out/#whats-next).
Some statistics with the released of v5.0.0 compared to the one of v4.0.0:
- 5,832 new commits
- 657 new contributors
- From 2M downloads/month to 9.5M downloads/month on npm
- From 350k users/month to 700k users/month on the documentation
We're also proud to share that the monetization initiatives we started right after the release of v4, such as [the store](/blog/material-ui-v4-is-out/#premium-themes-store-✨), are working. We incorporated the company two years ago, have grown 2-3X per year since, and we're now over 10 people, with a positive cash flow 🚀. We are on track to reach 16 people by December 2021.
[We're hiring](/careers/) to grow our existing products, but also to explore a bold new product vertical, aligned with our mission.
We couldn't be more grateful for the trust that the React community puts in us.
On average, we win 4% of market shares in the React community every year.
<a href="https://docs.google.com/spreadsheets/d/1l5j3Xjtvm9XZtmb4ulLiWElQaXSlZlyCWT5ONrQMpBo/edit#gid=0"><img loading="lazy" src="/static/blog/mui-core-v5/react-market.png" alt="MUI market shares in download relative to react-dom" style="width: 439px;" /></a>
<p class="blog-description">MUI market shares in download relative to react-dom</p>
We hope we can reach 50% of the React community by 2026. This is an ambitious goal, but not impossible.
### A public roadmap
You can use our public roadmap on GitHub to learn about what features we're working on, what stage they're at, and when we expect to bring them to you:
- [MUI Core](https://github.com/mui/material-ui/projects/25)
- [MUI X](https://github.com/mui/mui-x/projects/1)
We offer this transparency into what we plan to work on so that you can plan better and share feedback earlier to influence what we're building.
From a high-level perspective, we plan to focus in the upcoming period on the following topics:
- Core product:
- Unstyled components and hooks. We want to continue improving the customization experience.
- A second design system, that will help us grow MUI beyond Material Design.
- X product:
- Focus on the data grid component, by releasing the stable 5.0 version and developing the advanced features in our roadmap.
- Expand to a second component once the data grid is on the right path.
You can find more information about the new areas we are going to work on in the next sections.
### Unstyled components and hooks
To continue improving the customization experience, we are doubling down on the version of the components without styles.
These components and hooks contain the main functionalities and accessibility, without being opinionated about how styles are applied nor what styles.
We still have work to do to have a full set of unstyled components.
You can read more about them in [the docs](/base-ui/getting-started/) and keep track of our progress in [#27170](https://github.com/mui/material-ui/issues/27170).
Our high-level plan is to use the unstyled components and hooks as the basis of the Material components and second design system.
We are aiming to complete this work with the next major release (v6).
As of now, you can evaluate the unstyled primitives in a new Base package, or check out the next implementation of the Material Design components in the `@mui/material-next` package (targeted at v6).
Please note that both packages are in an alpha state so that we can release breaking changes –
we want to take the opportunity to create the best APIs we possibly can.
You can help us shape these new packages by taking part in discussions.
There are [RFCs](https://github.com/mui/material-ui/issues?q=is%3Aopen+label%3Adiscussion+%5BRFC%5D) waiting for your feedback.
Don't hesitate to let us know what you think!
### Second design system
Developing a new design system is one of the main initiatives, alongside this new brand and the unstyled components, to grow MUI beyond Material Design. Its codename is **Joy** and we have just started [the high-level discussion](https://github.com/mui/material-ui/discussions/27803) around it.
It will be built on top of our foundation packages (the base/unstyled components and `@mui/system`) to provide the API shaped similarly to our Material Design components. We plan on having built-in CSS variables generated from the theme, a great dark mode API, a custom look and feel, and more.
We're aiming for developing the most frequently used components first, as we plan on releasing them continuously with each milestone. We intend to have Joy versions of all components already available on Material Design so that developers can then pick between them, choosing the design they like the most. The main difference will be the theme structure, where we want to achieve the right amount of flexibility while providing an amazing design by default.
We'll keep you updated about the progress. And as always, you're invited to contribute to it as well. Stay tuned!
### MUI X
The data grid is the cornerstone of any application manipulating large amounts of data. We plan to focus on it as long as necessary to deliver most of the advanced features.
We still have column pinning, tree data, grouping, pivoting, excel export, and more to build!
Once we would have grown the team and made enough progress, we will expand to a second component.
### Design kits
We plan to run extended research and surveys.
We have already identified that accessibility is something leading companies care about.
We are planning to cover more user interaction states for prototyping, e.g. focus-visible.
## Thank you
Finally, one last thank you to everyone who's contributed to MUI Core v5.
The whole team is very excited about this release! It's just the beginning.
We will keep working hard to deliver the best possible React UI components while making it accessible to the many.
| 4,196 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/blog/mui-next-js-app-router.js | import * as React from 'react';
import TopLayoutBlog from 'docs/src/modules/components/TopLayoutBlog';
import { docs } from './mui-next-js-app-router.md?@mui/markdown';
export default function Page() {
return <TopLayoutBlog docs={docs} />;
}
| 4,197 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/blog/mui-next-js-app-router.md | ---
title: MUI Core libraries support the Next.js App Router
description: Material UI, Base UI, and Joy UI are now compatible with the App Router as Client Components. Get started using the latest Next.js features with MUI!
date: 2023-07-18T00:00:00.000Z
authors: ['samuelsycamore']
card: true
tags: ['News']
---
With [v5.14.0](https://github.com/mui/material-ui/releases/tag/v5.14.0), MUI's Core component libraries—Material UI, Base UI, and Joy UI—are now compatible with the Next.js App Router. 🚀
<img alt="MUI and Next.js logos" src="/static/blog/mui-next-js-app-router/logos.png" loading="lazy" width="2076" height="900" />
## Adapting to the new paradigm
React 18 introduced the concept of React Server Components, and Next.js 13 gave us the most mature framework implementation of RSCs to date with the App Router.
While these two changes have caused major waves among the React community, it's clear that this is the path forward, and it's our responsibility as library maintainers to adapt to the new paradigm.
As a first step towards this goal, we've updated all MUI Core components to ship with the `"use client"` directive, to let your apps know that these are Client Components (since Server Components are now the default).
:::info
**A note on terminology:** although MUI components cannot be used as React Server Components (RSCs) at this time, they _do_ support server-side rendering (SSR).
See [this explanation of Client Components and SSR](https://github.com/reactwg/server-components/discussions/4) from the React Working Group for more details on the distinction between RSC and SSR.
:::
Additionally, we've created guides to walk you through setting up an app using the Next.js App Router with each of the Core libraries:
- [Material UI setup](https://mui.com/material-ui/guides/next-js-app-router/)
- [Joy UI setup](https://mui.com/joy-ui/integrations/next-js-app-router/)
- [Base UI setup](https://mui.com/base-ui/guides/next-js-app-router/)
<img alt="Screenshot of the Material UI documentation" src="/static/blog/mui-next-js-app-router/docs.png" loading="lazy" width="2400" height="1394" style="margin-bottom:24px;" />
We also have example repos for each, with everything already set up for you:
- [Material UI example](https://github.com/mui/material-ui/tree/master/examples/material-ui-nextjs-ts)
- [Base UI with Tailwind CSS example](https://github.com/mui/material-ui/tree/master/examples/base-ui-nextjs-tailwind-ts)
- [Joy UI example](https://github.com/mui/material-ui/tree/master/examples/joy-ui-nextjs-ts)
## What comes next
In the world of Server Components, "traditional" CSS-in-JS poses a serious challenge that may require us to move beyond Emotion, which is the default styling solution for Material UI and Joy UI in v5.
We're currently exploring ways to offer our own zero-runtime CSS-in-JS solution that will enable you to use relevant MUI components as Server Components.
This will also have the added benefit of improving performance across the board.
Keep an eye out for an RFC from us very soon that will detail the proposed solution.
In the meantime, please let us know if you have any questions or encounter any issues when using MUI components with the Next.js App Router.
| 4,198 |
0 | petrpan-code/mui/material-ui/docs/pages | petrpan-code/mui/material-ui/docs/pages/blog/mui-product-comparison.js | import * as React from 'react';
import TopLayoutBlog from 'docs/src/modules/components/TopLayoutBlog';
import { docs } from './mui-product-comparison.md?@mui/markdown';
export default function Page() {
return <TopLayoutBlog docs={docs} />;
}
| 4,199 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.