Impacts to Existing Features

Unreads, badges and notifications

When collapsed threads is enabled, notifications behave differently - see matrix of scenarios and associated outputs here (full spreadsheet of the chart below)

Client Terminology:

CRT Unsupported Client = client doesn't have the CRT front end code (CRT supported flag = false by default). This includes,

• Old mobile versions that don’t have the CRT code yet 

• Webapp/server versions that don’t have the CRT front end available to enable yet

CRT Supported Client = client has the CRT front end code (Client sends CRT supported flag = true). This includes,

• New mobile versions that have the CRT code

• New webapp/server versions that have the CRT front end available to enable in config settings

CRT Off Client = client is CRT supported but the user has the feature off. This includes when the,

• Admin has the CRT config setting “off”, or

• User has feature turned off in account settings

CRT On Client = client is CRT supported and the user has the feature on. This only occurs when the user has CRT enabled in account settings.

Desktop Notifications

• When a user receives notifications about a root post - no change to existing flow. Take the user to the channel, scrolled to the root post

• When a user receives notifications about a reply post in a thread that is followed, take the user to the thread in the Global Threads context

• When a user receives notifications about a reply post in a thread that is not followed, take the user to the thread in the Channel context (RHS)

Mobile Notifications

• When a user receives notifications about a root post - no change to existing flow. Take the user to the channel, scrolled to the root post

• When a user receives notifications about a reply post in a thread that is followed, take the user to the thread in the Global Threads context

• When a user receives notifications about a reply post in a thread that is not followed (for cases when notifications are turned on for all activity), take the user to the thread in the Channel context (RHS)

• Notification Stacks in Notification Center:

  • Root posts are stacked by channel

  • Reply posts are stacked by thread

• Clearing notifications when reading in another client/device

  • If a user gets a notification on their mobile device, but then reads the related channel or thread on another client, the related stack gets cleared on the mobile device

Channel vs. Threads badges

In summary of the above chart:

1. When a root post with an @mention is posted in a channel, the mention badge is displayed on the channel, not the Global Threads sidebar item

2. When a reply post with an @mention is posted, the mention badge is displayed on the Global Threads menu item in the sidebar.

Channels vs. Threads unread state

When a reply is posted on a root post that has a mention, the mention badge stays on the channel that has the root post, BUT the Threads view now displays as bolded with a new unread message in a thread you follow

Permalinks

Permalinks to root posts

No change to existing UX. Permalinks to root posts take users to the channel, scrolled to the highlighted post.

Permalinks to child posts

Clicking on a permalink to a reply post would take the user to the thread in the RHS with the post scrolled to and highlighted. The center channel context does not change in this case.

Marking Channels as unread vs. Marking Threads as unread

1. Marking a thread as read/unread will NOT have any effect on the Channel’s sidebar state

2. Opening a channel, marking posts as ‘read' will NOT have any effect on the Threads' sidebar state

Other Implications to existing features (webapp)

1. Search

   1. Parent posts behave as-is. The ‘Jump’ action in the hover menu opens the parent post in the channel context

   2. Child posts display similarly, but the ‘Jump’ action in the hover menu opens the thread in the RHS scrolled to the child post

2. Pinned and Flagged posts RHS

   1. Parent posts behave as-is. The ‘Jump’ action in the hover menu opens the parent post in the channel context

   2. Child posts display similarly, but the ‘Jump’ action in the hover menu opens the thread in the RHS scrolled to the child post

3. Compact Mode

   1. Displays as-is, but shows the new Thread Footer below the post content

Other Implications to existing features (mobile app)

1. Search

   1. Tapping on a search result goes to the Single Thread View (rather than opening it up in a modal) with the clicked message in view

2. Pinned and Flagged Views

   1. Tapping on an item goes to the Single Thread View with the tapped message in view