The Activity Feed is an event-based timeline meant to keep the user informed of activity within the application. The Activity Feed is grouped by days with the most recent activity at the top. Each event is tied to a source that caused the event to occur. Sources include transactions, users, and services.
When to Use
The Activity Feed is used when changes in transactions or attributes of the systems have triggered by the system, user(s), or external applications.
It should also reflect the context in which its presented (ie. Invoice – should display entries reflecting activity of that particular invoice.).
Appearance & Behavior
The Activity Feed comes in two styles, narrow and wide. Activity Feeds may reside at multiple levels within an application’s information architecture. The rules governing the specifics of an Activity Feed entry may depend on the location of the Activity Feed within the information architecture; however, the contents of an Activity Feed should always be contextually relevant. For example, the Activity Feed on a customer profile only displays events relevant to that customer. When a new item appears in the Activity Feed, it slides down into place from the date header and pushes the remaining items down the Activity Feed.
Summary of Parts
- A – Group Header
- B – Message Entry – Used to display either messages received or sent.
- C – File Attachment – Affordance to display associated file attachment to feed entry that cannot be previewed as Media. Clicking would download and view via plug-in or local application.
- D – User Activity – Events tied to a user always start with the user’s name.
- E – Media – Activity Feed events may also include images and videos, which the user can preview in a Media Light Box.
- F – Activity within External Services – Events that occur in external applications can also appear in the Activity Feed. These events should include the external application’s logo and may also include the application’s name as a Link. Clicking either navigates the user to the application.
- G – Transaction Status Change – Events can help notify the user of important changes in a transaction’s status. These events always include a status icon and start with the transaction’s name or number followed by the name of the person (e.g., customer) associated with the transaction.
- H – Call to Action – If the entry represents a transaction with a clear primary action, it may be invoked directly from feed.
- I – App Recommendations – App recommendations in the Activity Feed should be contextual to a single entry. This requirement means that recommendations only appear once the user’s specific needs have been identified. The recommendation includes a button that takes the user to the corresponding location in the App Center. The user can dismiss the recommendation at any time.
- Capitalization of all activity feed messages is sentence case