nvladimirovi / components

Component infrastructure and Material Design components for Angular

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
@angular/cdk	Library that helps you author custom UI components with common interaction patterns	Docs
@angular/material	Material Design UI components for Angular applications	Docs
@angular/google-maps	Angular components built on top of the Google Maps JavaScript API	Docs
@angular/youtube-player	Angular component built on top of the YouTube Player API	Docs

Quick links

Documentation, demos, and guides | Frequently Asked Questions | Community Google group | Contributing | StackBlitz Template

Getting started

See our Getting Started Guide if you're building your first project with Angular Material.

Contributing

If you'd like to contribute, please follow our contributing guidelines. Please see our help wanted label for a list of issues with good opportunities for contribution.

What we're working on now (Q2 2020):

• Trying to get anything done at all during a global pandemic.
• Hosting and mentoring a large contingent of summer interns.
• Date-range picker
• Remaining test harnesses for Angular Material components
• 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 will be dedicated towards rolling out these new versions of the components across Angular apps inside Google.
• Add support for density configuration for the new components based on MDC Web.
• Authoring benchmarks to collect performance metrics for Angular Material components. These benchmarks will live inside Google's internal code repository for the time being, but we should be able to publish the results.

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 IE11 / Edge.

We aim for great user experience with the following screen readers:

• Windows: NVDA and JAWS with IE11 / FF / Chrome.
• macOS: VoiceOver with Safari / Chrome.
• iOS: VoiceOver with Safari
• Android: Android Accessibility Suite (formerly TalkBack) with Chrome.
• Chrome OS: ChromeVox with Chrome.