Skip to content

feat(messaging): Improve message bubble UI and add delivery status action#4330

Merged
jamesarich merged 2 commits into
mainfrom
feat/message-tweaks
Jan 27, 2026
Merged

feat(messaging): Improve message bubble UI and add delivery status action#4330
jamesarich merged 2 commits into
mainfrom
feat/message-tweaks

Conversation

@jamesarich

@jamesarich jamesarich commented Jan 26, 2026

Copy link
Copy Markdown
Collaborator

This introduces several UI enhancements to the messaging feature and adds a new action to view message delivery status.

Key Changes:

  • Message Bubble Shape:

    • The logic for getMessageBubbleShape has been simplified to create a more standard chat bubble appearance. The corners are now less rounded (8.dp instead of 16.dp), and the logic for squaring off corners based on adjacent messages has been removed, resulting in a cleaner look.
  • Message Delivery Status:

    • A new item has been added to the message actions bottom sheet that displays the delivery status (e.g., "Delivered to mesh", "Acknowledged") for sent messages.
    • Tapping this item will reveal more details (though the full details screen is not part of this change).
    • The status icon in the message bubble is no longer clickable; status details are now accessed through the long-press menu.
  • UI and Layout Refinements:

    • Font size for message text has been changed to bodyMedium.
    • Padding and alignment have been adjusted for MessageItem, NodeChip, and other components to improve spacing and visual consistency.
    • MessageActionsBottomSheet composable has been removed and its content is now directly integrated, simplifying the component structure.

…tion

This commit introduces several UI enhancements to the messaging feature and adds a new action to view message delivery status.

### Key Changes:

-   **Message Bubble Shape:**
    -   The logic for `getMessageBubbleShape` has been simplified to create a more standard chat bubble appearance. The corners are now less rounded (`8.dp` instead of `16.dp`), and the logic for squaring off corners based on adjacent messages has been removed, resulting in a cleaner look.

-   **Message Delivery Status:**
    -   A new item has been added to the message actions bottom sheet that displays the delivery status (e.g., "Delivered to mesh", "Acknowledged") for sent messages.
    -   Tapping this item will reveal more details (though the full details screen is not part of this change).
    -   The status icon in the message bubble is no longer clickable; status details are now accessed through the long-press menu.

-   **UI and Layout Refinements:**
    -   Font size for message text has been changed to `bodyMedium`.
    -   Padding and alignment have been adjusted for `MessageItem`, `NodeChip`, and other components to improve spacing and visual consistency.
    -   `MessageActionsBottomSheet` composable has been removed and its content is now directly integrated, simplifying the component structure.

Signed-off-by: James Rich <2199651+jamesarich@users.noreply.github.com>
@github-actions github-actions Bot added the enhancement New feature or request label Jan 26, 2026
@jamesarich jamesarich changed the title feat(messaging): Improve message bubble UI and add delivery status ac… feat(messaging): Improve message bubble UI and add delivery status action Jan 26, 2026
This commit moves the `MessageStatusIcon` to appear before the timestamp in the message item layout. It also adjusts the padding around the icon and the timestamp for better alignment and visual consistency.

Signed-off-by: James Rich <2199651+jamesarich@users.noreply.github.com>
@codecov

codecov Bot commented Jan 26, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 0.00%. Comparing base (2b6c318) to head (a9d063e).
⚠️ Report is 3 commits behind head on main.
✅ All tests successful. No failed tests found.

Additional details and impacted files
@@          Coverage Diff          @@
##            main   #4330   +/-   ##
=====================================
  Coverage   0.00%   0.00%           
=====================================
  Files          3       3           
  Lines         28      28           
  Branches       8       8           
=====================================
  Misses        28      28           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@jamesarich jamesarich added this pull request to the merge queue Jan 27, 2026
Merged via the queue into main with commit 2f67727 Jan 27, 2026
9 checks passed
@jamesarich jamesarich deleted the feat/message-tweaks branch January 27, 2026 00:54
@rob-fi

rob-fi commented Feb 2, 2026

Copy link
Copy Markdown

I'm not sure if this PR is responsible but it was the last one I could find related to message UI changes.

If this should be opened up separately elsewhere then please let me know.

I recently updated to the latest build available via Google (2.7.12 (29319915)) and in entirely my opinion, the message UI has deteriorated since 2.7.11. At least on my device (essentially stock Android (Graphene OS) on Pixel 9a) it now looks cluttered and awkward.

photo_2026-02-02_17-02-46

There are so many elements clustered together now, what with the node short name bubbles, the message bubbles that may or may not have quote "bars", and the date/time text that is the same colour and has barely any size difference to the message text that looks especially bad on short messages. In addition to that there is not enough padding and the overall text size is too small.

If the goal is compactness then I'd suggest a Discord-like look to messages, if the goal is familiar mobile messaging then more cues should be taken from Telegram, WhatsApp etc with regards to padding and design of elements. Unoriginal? Perhaps. But on mobile usability is key :).

@jamesarich

Copy link
Copy Markdown
Collaborator Author

I'm not sure if this PR is responsible but it was the last one I could find related to message UI changes.

If this should be opened up separately elsewhere then please let me know.

I recently updated to the latest build available via Google (2.7.12 (29319915)) and in entirely my opinion, the message UI has deteriorated since 2.7.11. At least on my device (essentially stock Android (Graphene OS) on Pixel 9a) it now looks cluttered and awkward.

photo_2026-02-02_17-02-46

There are so many elements clustered together now, what with the node short name bubbles, the message bubbles that may or may not have quote "bars", and the date/time text that is the same colour and has barely any size difference to the message text that looks especially bad on short messages. In addition to that there is not enough padding and the overall text size is too small.

If the goal is compactness then I'd suggest a Discord-like look to messages, if the goal is familiar mobile messaging then more cues should be taken from Telegram, WhatsApp etc with regards to padding and design of elements. Unoriginal? Perhaps. But on mobile usability is key :).

Design is always an iterative process, there's always room for improvement, and change is hard. This is a step towards improvement, give it some time to sink in and provide concrete examples of feedback and suggested changes in a feature request.

@rob-fi

rob-fi commented Feb 2, 2026

Copy link
Copy Markdown

Design is always an iterative process, there's always room for improvement, and change is hard. This is a step towards improvement, give it some time to sink in and provide concrete examples of feedback and suggested changes in a feature request.

Sure thing, and I appreciate your efforts to improving the UI despite it might coming across as otherwise!

I have good experience when it comes to UX/UI and I'll gladly take the time to produce some mock-ups in a feature request. Minor tweaks to padding and text is really all that's needed really, but sometimes subtle changes like that can make a big difference.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants