Tables present rows of content in a single column. A table row is dynamically configurable and its contents can be changed at any time. Tables are inherently scrollable, support various interactions, and can be assigned a background color or image.
Use row types consistently. Although a table can contain multiple row types, it should present a consistent overall appearance. Start with the row type you use for your main content, and add more as needed to support other types of content, such as headers or footers. Always use each row type for its intended purpose. For example, don’t display content in a row type designed for headers or footers.
Limit the number of table rows to about 20. Display the most important rows at the top and let the user view more on demand. Fewer rows are easier to scan quickly.
Don’t embed tables inside groups. Tables resize dynamically based on the number of rows they contain; they ignore height restrictions placed on them by groups.
Do not include chevrons in table rows. The row background communicates the tappable nature of the row. You do not need to include a chevron or other text to indicate that the row is tappable.
Use vertical page-based navigation for fast navigation of your table’s content. With vertical page-based navigation enabled, users swipe vertically to navigate between the detail items of different table rows. This navigation saves time by eliminating the need to navigate back to the previous screen and tap a new detail item.
For developer guidance, see WKInterfaceTable.