Lists and Tables
Both lists and tables can:
- Present rows of information in a single column
- Support various interactions, such as scrolling and tapping
- Display a custom background color or image
In addition, lists provide a few features that tables don’t. Most notably, a list can use a carousel style for rows; support swipe interactions, such as delete; and let people reorder rows.
Style rows consistently. Using a coherent row style helps people grasp the overall logic of the list or table and focus on the information it contains. For example, you might define one row style for your main content and use a couple more to support other types of content, such as headers or footers.
When it makes sense, limit the number of rows to about 20. Short lists are easier for people to scan, but sometimes people expect a long list of items. For example, if people subscribe to a large number of podcasts, they might think something's wrong if they can't view all their items. You can help make a long list more manageable by displaying the most relevant 15 to 20 items and providing a way for people to view more.
Avoid nesting a list or table inside a group. Tables and lists resize dynamically based on the number of rows they contain; they don’t adhere to the height restrictions that groups impose.
Avoid using a chevron in a row. The row background shows people that they can tap it, so you don’t need to include a chevron or other text to indicate that a row is tappable.
Constrain the length of detail views if you want to support vertical page-based navigation. People use vertical page-based navigation to swipe vertically among the detail items of different list or table rows. Navigating in this way saves time because people don't need to return to the list to tap a new detail item, but it works only when detail views are short. If your detail views scroll, people won't be able to use vertical page-based navigation to swipe among them.