Skip to content
< Back to blog

Q2 2020 Update

Olivier Tassinari. July 17, 2020.

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.
    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!

    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 and milestone.

  • ๐Ÿ“ The icons package has been updated with changes made by Google, leading to 200+ new icons.

    icons
  • ๐ŸŽจ Figma assets for MUI extend the support for design tools beyond Sketch.

    figma

    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. This work is influenced by the concurrent UI patterns presented by the React team.

    loading
  • โš›๏ธ We have made all component props available in IntelliSense. This is complementary to the propTypes and API pages in the documentation.

    props

  • โฐ A new Timeline component joins the lab.

    timeline
  • ๐Ÿ“ฃ 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. 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, Yan Lee, and Jairon Alves Lima, native speakers from the community ๐Ÿ™.

    chinese brazilian

    After English, Chinese, and Brazilian, the languages that would benefit the most from translation are Russian and Spanish.
    Feel free to get stuck into 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 implements accessible tabs following WAI-ARIA authoring practices.

<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:

    • 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 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 if you want something specific. The number of ๐Ÿ‘ helps us to prioritize.

Company

These are objectives, no guarantees:

  • ๐Ÿข We will hire 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.