Intro
An object cell is a table view cell that fits inside the table view container. It is highly customizable to accommodate a wide variety of uses.
Object cell examples
Usage
Do
- Use an object cell to preview information about an object in an object page.
- Keep consistent height and alignment of all object cells in a table view or list report.
Don't
Do not mix object cells with different height and content types in a table view or list report.
Anatomy
Object cell anatomy
A. Left Icon Stack (Optional)
A set of up to three vertically stacked icons can be displayed on the left of the detail image. These icons provide information about the object, such as whether it is unread or if it has attachments.
B. Detail Image (Optional)
The detail image provides a visual representation of the object within a 44 pixel frame. Leveraging the avatar component, the detail image has a minimum size of 16 pixels and a maximum of 60 pixels. The image may have a square or circular frame depending on the type of object that the object cell represents. If the object cell represents a user, use a circular frame. If the object cell represents an object, use a square frame.
C. Main Content
The main content is the main area for text content. It allows for a wide range of component elements: a title, subtitle, footnote, caption, description, rating control, avatar stack, and tags. The title is the only mandatory content element for the object cell.
D. Description (Optional)
A description can be used to provide additional information about the object. The description label offers two display options: it can be truncated after a customizable number of lines, with the default set to three, or it can be configured to display the full content. Depending on the orientation of the device (portrait or landscape) the location of the description will change. In portrait mode, it appears at the bottom of the main content container. For landscape mode, the description appears in its own column shown above, this is typically a longer string of text than what is displayed in the title content area.
E. Attributes
The attributes are a vertically or horizontally stacked arrangement of labels and icons types that are displayed towards the right side of the object cell. These labels and icons can be used to indicate the condition of the item, such as its priority or status.
F. Accessory View (Optional)
The accessory view is used to add secondary action(s) in addition to the primary action of drilling down or as another indicator. These can include a navigational icon, such as a chevron (which would trigger a push navigation) an information disclosure icon, (which would bring up a model), single action download, or an overflow menu.
Variations
Vertically Centered and Top-Aligned Object Cell
Vertically centered object cell (left) and vertically top-aligned object cell (right)
Preview Object Cell
Object cell preview variation
Quick View Object Cell
Object cell quick view variation
Single Action Object Cell
Object cell single action variation
Behavior and Interaction
Select (Edit Mode)
When the edit mode is triggered, users can select single or multiple object cells at once to perform an action, such as delete, change status, and so on.
Quick Actions
Quick actions are activated by a gesture such as swipe to reveal contextual actions (for example, delete, approve, or edit). Swipe-based quick actions are intended as secondary interactions that provide efficiency for experienced users.
When quick actions are used, they must not be the only way to access the associated actions. To comply with accessibility requirements, all actions exposed through swipe gestures must also be available through a primary, single-touch interaction that is visible and operable without relying on gestures.
Acceptable primary access patterns include:
- A visible overflow right accessory button on the object cell that exposes the same actions
- Single-tap navigation to an object detail page where the actions are available via visible controls
Swipe gestures may be offered as optional shortcuts, but they must always be complemented by a discoverable, single-tap alternative. Gesture-only access (including swipe, long-press, or Peek and Pop) must not be relied on as the primary interaction.
Context Menu & Preview
On iOS 13 and later, applications may optionally use context menus and preview for an object cell using standard iOS context menu APIs (for example, via long-press). This interaction replaces the legacy Peek and Pop pattern.
Context menus and previews are also secondary interactions. They may be used to expose quick actions or lightweight previews, but (similar to quick actions) must not be relied on as the primary or sole way to access actions.
Again, all actions exposed through context menus must also be available through a visible, single-tap interaction.
From left to right: select (edit mode), quick actions, and context menu with preview view
Navigation
The preview and quick view variations both include a navigational aspect. The preview uses a chevron icon to indicate a push to the full content of the object, while the quick view uses an information disclosure icon to indicate that a modal will pop up with the full content of the object.
Example of preview and quick preview navigation
Adaptive Design
Compact and Regular Width
Object cell's adaptivity for compact and regular width
Compact and Regular Height
Example of an object cell's adaptivity for compact and regular height
Resources
Development: UIKit FUIObjectTableViewCell, SwiftUI ObjectItem
SAP Fiori for Android: Object Cell, Key Value Cell
Related Components/Patterns: Contact Cell, List Picker, Collection View