Skip to content

Remove (?) mostly-redundant recipient headers in DM narrow #1244

Open
@chrisbobbe

Description

@chrisbobbe

Much like an issue for topic narrows:

but this is for DM narrows. Currently it looks like this:

Many messages Few messages

We have a design from Vlad showing the many-messages case:

https://www.figma.com/design/1JTNtYo9memgW7vV6d0ygq/Zulip-Mobile?node-id=4933-16071&m=dev
image

which looks like it just removes the recipient headers. Perhaps we should do that, but first let's consider some design questions Greg raised for topic narrows in #1039 (comment) which seem equally relevant to DM narrows:

Design questions we'll want to resolve before implementing this include:

  • Have an example where the thread is shorter than the screen, so there's empty space between the app bar and the first message; make sure we're happy with how that looks, or adjust something. (Possibly switch to pinning the earliest message at the top instead of the latest at the bottom, so the empty space goes between the last message and the compose box.)
  • Decide how to handle showing the messages' dates, which currently live in the recipient header.

cc @terpimost for those design questions.

Metadata

Metadata

Assignees

No one assigned

    Labels

    a-msglistThe message-list screen, except what's label:a-content

    Type

    No type

    Projects

    • Status

      No status

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions