Component infrastructure and Material Design components for Angular
Filed under user interfaceShow All
Official components for Angular
The Angular team builds and maintains both common UI components and tools to help you build your own custom components. The team maintains several npm packages.
Package Description Docs
Library that helps you author custom UI components with common interaction patterns Docs
Material Design UI components for Angular applications Docs
Angular component built on top of the YouTube Player API Docs
See our Getting Started Guide if you're building your first project with Angular Material.
What we're working on now (Q4 2021):
- Continuing to create new, API-compatible versions of the Angular Material components backed by
MDC Web (see @jelbourn's ng-conf talk). Much of our effort
is dedicated towards rolling out these new versions of the components across Angular apps
inside Google. This work will pay off with the following benefits:
- Dramatically improve consistency with the Material Design spec, which has changed significantly since Angular Material's 2016 inception. This also makes future versions of Material Design significantly easier to adopt.
- Introduce a new theming API for component density, a top feature request.
- Fix a number of longstanding accessibility bugs.
- Increase number of people working to continuously improve the components on an ongoing basis (both the Angular team and the Material Design team).
- Accessibility - we'll be focusing on improving the accessibility of
MatDatepickeras well as evaluating accessibility bugs for mobile web platforms.
About the team
The Angular Components team is part of the Angular team at Google. The team includes both Google employees and community contributors from around the globe.
Our team has two primary goals:
- Build high-quality UI components that developers can drop into existing applications
- Provide tools that help developers build their own custom components with common interaction patterns
What do we mean by "high-quality" components?
- 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 developers.
Browser and screen reader support
The Angular Components team supports the most recent two versions of all major browsers: Chrome (including Android), Firefox, Safari (including iOS), and Edge.
We aim for great user experience with the following screen readers:
- Windows: NVDA and JAWS with FF / Chrome.
- macOS: VoiceOver with Safari / Chrome.
- iOS: VoiceOver with Safari
- Android: Android Accessibility Suite (formerly TalkBack) with Chrome.
- Chrome OS: ChromeVox with Chrome.
- Continuing to create new, API-compatible versions of the Angular Material components backed by MDC Web (see @jelbourn's ng-conf talk). Much of our effort is dedicated towards rolling out these new versions of the components across Angular apps inside Google. This work will pay off with the following benefits: