Material Design for Angular
This is the home for the Angular team's Material Design components built for and with Angular.
See our Getting Started Guide if you're building your first project with Angular Material.
Angular Material is currently in beta and under active development. During beta, new features will be added regularly and APIs will evolve based on user feedback.
Check out our directory of design documents for more insight into our process.
If you'd like to contribute, you must follow our contributing guidelines.
You can look through the issues (which should be up-to-date on who is working on which features
and which pieces are blocked) and make a comment.
Also see our
Good for community contribution
High level stuff planned for Q3 2017 (July - September):
- As many bug fixes as humanly possible
- Additional features for data-table
- Continued accessibility improvements
- Nested menus
- All components are OnPush
- Improved documentation, guides, examples, and navigation on material.angular.io
- Improve library-wide API consistency
- Stepper component
- Sticky header helper
- action-list and selection-list
|chips||Chip-remove, integration with input in-progress||Docs|
|data-table||Sticky headers & incremental row rendering in-progress||Docs|
|list||Selection and action list planned Q3||Docs|
|menu||Nested menu planned Q3||Docs|
|snackbar / toast||Docs|
|cdk||Launched, documentation in-progress|
In progress, planned, and non-planned features
|tree||In-progress (sneak peek)||-||#3175|
|stepper||In-progress, planned Q3 2017||-||#508|
|sticky-header||In-progress, planned Q3 2017||-||#474|
|virtual-repeat||Not started, planned Q4 2017||-||#823|
|fab speed-dial||Not started, not planned||-||#860|
|fab toolbar||Not started, not planned||-||-|
|bottom-sheet||Not started, not planned||-||-|
|bottom-nav||Not started, not planned||-||#408|
The goal of Angular Material
Our goal is to build a set of high-quality UI components built with Angular and TypeScript, following the Material Design spec. These components will serve as an example of how to write Angular code following best practices.
What do we mean by "high-quality"?
- Internationalized and accessible so that all users can use them.
- Straightforward APIs that don't confuse developers.
- Behave as expected across a wide variety of use-cases without bugs.
- Behavior is well-tested with both unit and integration tests.
- Customizable within the bounds of the Material Design specification.
- Performance cost is minimized.
- Code is clean and well-documented to serve as an example for Angular devs.
Browser and screen reader support
Angular Material supports the most recent two versions of all major browsers: Chrome (including Android), Firefox, Safari (including iOS), and IE11 / Edge
We also aim for great user experience with the following screen readers:
- NVDA and JAWS with IE / FF / Chrome (on Windows).
- VoiceOver with Safari on iOS and Safari / Chrome on OSX.
- TalkBack with Chrome on Android.