nextcloud / nextcloud/spreed

🧩 UX Suggestions: keyboard shortcuts for messages search

Open
#15,002 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement feature: chat 💬 feature: frontend 🖌️
Dominant language
JavaScript
Stars
2.2k
Forks
586
Avg merge
18h 27m
Merged PRs (30d)
333

Description

Hello Nextcloud Talk team,

First of all, thank you for your amazing work on this project. I really appreciate the functionality and reliability of Talk. After using it regularly, I’d like to propose a few improvements focused on user experience and interface clarity.

🔸 Feature Suggestions

1. Group Conversations into Folders or Categories

In the left sidebar (conversation list), it would be very helpful to allow users to organize conversations into folders or categories. This is especially useful when dealing with a high number of group chats or topics.
Example inspiration: Mattermost uses a similar approach with custom sidebar grouping.

Benefit: Easier navigation and better focus by allowing users to sort and filter conversations based on themes, teams, or projects.
2. Add Keyboard Shortcut to Search Messages

Implementing a keyboard shortcut (like Ctrl + F or /) to quickly jump to a search bar within a conversation would save time and improve accessibility.

Benefit: Users can instantly find key parts of discussions without leaving their keyboard or manually clicking through the interface.
3. Improve Visual Distinction Between Messages

In a conversation view, it’s currently difficult to visually distinguish between my own messages and those of others. Suggestions:

Apply a different background color to my messages vs. messages from others.

Slightly align my messages to the right, and those of others to the left (similar to many chat apps).

Benefit: Enhances readability and makes it easier to follow the flow of the conversation, especially in active group chats.

💬 Final Note

These are small UX tweaks that I believe would significantly improve day-to-day usability of Nextcloud Talk. If you're open to it, I'd be happy to elaborate further or help test potential changes.

Thanks again for your time and consideration!

Best regards,

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by separating the three proposals: conversation folders, a keyboard shortcut for the in-conversation search bar, and visual distinctions between messages. Read the conversation list and conversation view entry points, then determine which proposal has a defined scope and how its completed behavior would be verified.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.