CardView is probably the most frequently used and flexible material component, and as such, there are a considerable number of guidelines concerning its structure, appearance, and function. Cards are described by Google as being entry points to more detailed information. This means that they should provide a small number of actions in the form of buttons, clickable images, and often, simply the card itself.
The way we used cards in the previous section, to create a list, is probably not the best example of how to employ CardView. Generally, with lists of items with very similar content, a simple divider provides a far less cluttered layout, and cards were used here just to demonstrate RecyclerViews in an easily digestible fashion.
Cards come into their own when they can be be presented in a collection where they do not all share identical layouts. In fact, one of the things that makes cards so useful is that although they are required to have uniform widths, there is no necessity for...