The roadmap is a living document, and it is likely that priorities will change, but the list below should give some indication of our plans for the next major release, and for the future.
We are mainly focusing on bug fixes 💥.
New features have low priority and might not be reviewed nor merged.
v0.16.0 (expected in the next couple months)
The next release is going to be huge ✨
Material-UI was started 2 years ago. The ecosystem has evolved a lot since then, we have also learned a lot. @nathanmarks started an ambitious task, rebuilding Material-UI from the ground-up taking advantage of this knowledge to address long-standing issues. Expect various breaking changes.
The core team is now helping him in the next branch.
Here are some issues that we plan to fix along the way.
For more details, you can have a look a the v0.16.0 milestone.
- [#4066] There should be a more sophisticated styling solution.
- Drastically improving performance by removing inefficient computations (styles).
- Remove all imperative methods.
- [#2957] Standardize callback signatures.
- [#2880] Remove valueLink.
- [#1321] Composable AppBar component.
- [#3191] Improve component property documentation.
- Make extensive use of
popoverandrender-to-layer. - Full Featured Tabs (close, disable, move, sizing, scrolling).
- Responsive components to better support MD spec for mobile component sizes, and in preparation for react-native support.
- [#2416] TextField as a composable component for various field types.
- Better keyboard navigation support.
- Standardize API naming and available
propconvention across the library. - Better accessibility support.
- [#2251] Full featured Table.
- [#2863] Add missing components, and missing features from current ones.
- [#593] Full support for react-native.
- Add example on how to use react-virtualized / react-list for lists, menu items and table.
- [#2493] Use higher order components across the library to abstract themes passed down from context.
- [#2784] Stateless components.
- [#1673] I18n for the doc-site.