Implement “See More / See Less” for Long Messages
Currently, when users send very long messages, it results in excessive scroll behaviour in the chat UI, making it difficult to read and view multiple messages on the screen. To improve user experience, it is requested to implement a “See More / See Less” feature, an option to expand or collapse the message. This will ensure the chat view remains clean, at least 1.5 to 2 messages are visible on the screen at all times, and overall readability and usability of the chat interface are significantly enhanced.
💡 Feature Request
Implement “See More / See Less” for Long Messages
Currently, when users send very long messages, it results in excessive scroll behaviour in the chat UI, making it difficult to read and view multiple messages on the screen. To improve user experience, it is requested to implement a “See More / See Less” feature, an option to expand or collapse the message. This will ensure the chat view remains clean, at least 1.5 to 2 messages are visible on the screen at all times, and overall readability and usability of the chat interface are significantly enhanced.
💡 Feature Request
Enable Legacy Moderation Access for Team member with Moderator Role
Currently, the legacy moderation settings in the dashboard are only accessible to team members with the “admin” or “owner“ role. However this functionality should be available for team members with the “moderator” role as well. This will allow moderators to handle moderation features like reported messages directly from the dashboard without requiring admin access. Granting this access to moderators ensures they can perform moderation tasks effectively, while still restricting them from making changes to critical app settings that are reserved for admin team members.
💡 Feature Request
Enable Legacy Moderation Access for Team member with Moderator Role
Currently, the legacy moderation settings in the dashboard are only accessible to team members with the “admin” or “owner“ role. However this functionality should be available for team members with the “moderator” role as well. This will allow moderators to handle moderation features like reported messages directly from the dashboard without requiring admin access. Granting this access to moderators ensures they can perform moderation tasks effectively, while still restricting them from making changes to critical app settings that are reserved for admin team members.
💡 Feature Request
Slow mode extension in latest versions
A customer has requested the return of the “Slow Mode” extension in the latest UIKit Versions, which was previously available but now it is deprecated. This feature is especially useful in group chats with many participants, such as during live events, where it helps prevent message flooding by allowing users to send messages only at set intervals. The customer would like to see this functionality officially supported again or provided as an easy-to-integrate extension.
💡 Feature Request
Slow mode extension in latest versions
A customer has requested the return of the “Slow Mode” extension in the latest UIKit Versions, which was previously available but now it is deprecated. This feature is especially useful in group chats with many participants, such as during live events, where it helps prevent message flooding by allowing users to send messages only at set intervals. The customer would like to see this functionality officially supported again or provided as an easy-to-integrate extension.
💡 Feature Request
Disable CometChatMessageComposer Auto Focus of Web UI Kits in Desktop Mode
The CometChatMessageComposer component of Web UI Kits in the Desktop Mode currently auto-focuses the input field on render, which can be disruptive in some scenarios. Requesting a configurable option (such as a prop) to disable this auto-focus behavior, allowing developers greater flexibility and ensuring smoother integration across diverse project setups.
💡 Feature Request
Disable CometChatMessageComposer Auto Focus of Web UI Kits in Desktop Mode
The CometChatMessageComposer component of Web UI Kits in the Desktop Mode currently auto-focuses the input field on render, which can be disruptive in some scenarios. Requesting a configurable option (such as a prop) to disable this auto-focus behavior, allowing developers greater flexibility and ensuring smoother integration across diverse project setups.
💡 Feature Request
Offline Support in Flutter
Local Storage: Storing chat data locally on the device so users can access their previous conversations even when there is no internet connection. Offline Access: Displaying all previously loaded conversations and messages when the app is offline, similar to local database solutions like Hive or Drift. The goal is to allow users to view and interact with their chat history while offline, and automatically sync any new messages or changes once the device is back online. Does the Flutter SDK or UI Kit provide support for these offline capabilities?
💡 Feature Request
Offline Support in Flutter
Local Storage: Storing chat data locally on the device so users can access their previous conversations even when there is no internet connection. Offline Access: Displaying all previously loaded conversations and messages when the app is offline, similar to local database solutions like Hive or Drift. The goal is to allow users to view and interact with their chat history while offline, and automatically sync any new messages or changes once the device is back online. Does the Flutter SDK or UI Kit provide support for these offline capabilities?
💡 Feature Request
Idea
Retaining Group Conversation Messages After User Leaves the Group
When a user leaves a group, they currently lose access to the messages sent while they were a member. The request is to allow users to still see messages up until their departure, with the option to delete the group conversation if they choose to. This ensures they can refer to important discussions from before they left.
💡 Feature Request
Idea
Retaining Group Conversation Messages After User Leaves the Group
When a user leaves a group, they currently lose access to the messages sent while they were a member. The request is to allow users to still see messages up until their departure, with the option to delete the group conversation if they choose to. This ensures they can refer to important discussions from before they left.
💡 Feature Request
Idea
Add Ability to Configure Role Permissions in CometChat Dashboard
Currently, updating role permissions like listUsers requires using the API. It would be helpful to provide an option in the CometChat Dashboard to configure and update role permissions directly, making it easier for users to manage roles without API calls.
💡 Feature Request
Idea
Add Ability to Configure Role Permissions in CometChat Dashboard
Currently, updating role permissions like listUsers requires using the API. It would be helpful to provide an option in the CometChat Dashboard to configure and update role permissions directly, making it easier for users to manage roles without API calls.
💡 Feature Request
Idea
Profile Picture Update Not Reflected in Chat History
Whenever a user updates their profile picture, the change is correctly reflected on the Dashboard. However, in the chat application, previous messages still display the old profile picture. The updated image only appears in newly sent messages.
💡 Feature Request
Idea
Profile Picture Update Not Reflected in Chat History
Whenever a user updates their profile picture, the change is correctly reflected on the Dashboard. However, in the chat application, previous messages still display the old profile picture. The updated image only appears in newly sent messages.
💡 Feature Request
Idea
Add Support for Setting Draft Text in MessageComposer – React Native UI Kit v5
A customer has requested the ability to restore draft messages in the chat composer when navigating back to a conversation. While draft text can be saved in app state, the UI Kit currently does not provide a way to programmatically set the composer text.
💡 Feature Request
Idea
Add Support for Setting Draft Text in MessageComposer – React Native UI Kit v5
A customer has requested the ability to restore draft messages in the chat composer when navigating back to a conversation. While draft text can be saved in app state, the UI Kit currently does not provide a way to programmatically set the composer text.
💡 Feature Request
Idea
Title: Include Unread Message Count in Push Notification Payload
Description: While implementing unread message count functionality, there is a need to update the unread count directly from the push notification payload. Currently, the payload does not appear to include this information. It would be helpful if the unread message count is included in the push notification payload, or if there is a recommended method to fetch or calculate it when a background notification is received.
💡 Feature Request
Idea
Title: Include Unread Message Count in Push Notification Payload
Description: While implementing unread message count functionality, there is a need to update the unread count directly from the push notification payload. Currently, the payload does not appear to include this information. It would be helpful if the unread message count is included in the push notification payload, or if there is a recommended method to fetch or calculate it when a background notification is received.
💡 Feature Request
Idea
Webhook Trigger for First Message in a Conversation
As of now, CometChat triggers the webhook event (such as message.sent) for every message that is sent in the system regardless of whether it's the first message in a conversation.There is a feature request for a dedicated webhook trigger for the first message in a conversation.
💡 Feature Request
Idea
Webhook Trigger for First Message in a Conversation
As of now, CometChat triggers the webhook event (such as message.sent) for every message that is sent in the system regardless of whether it's the first message in a conversation.There is a feature request for a dedicated webhook trigger for the first message in a conversation.
💡 Feature Request
Idea
Ability to "Pin" Conversations on top
Allow users to pin important conversations to the top of their chat list for quick and easy access. Pinned chats remain at the top regardless of new incoming messages in other conversations, helping users stay organized and prioritize key conversations.
💡 Feature Request
Idea
Ability to "Pin" Conversations on top
Allow users to pin important conversations to the top of their chat list for quick and easy access. Pinned chats remain at the top regardless of new incoming messages in other conversations, helping users stay organized and prioritize key conversations.
💡 Feature Request
Idea
Fetching Unjoined Groups for a Specific User in CometChatGroups Component
Current Behavior: As of now, using the GroupsRequestBuilder, we have the ability to: Set.joinedOnly(true) to fetch only the groups the current user has already joined. Set.joinedOnly(false) to fetch all available groups (regardless of the user's membership status). However, in the context of the CometChatGroups component, this behavior is not fully supported. There is no built-in way to filter and show only the groups that a particular user has not joined. Feature: The ability to filter groups based on users who have not joined them.
💡 Feature Request
Idea
Fetching Unjoined Groups for a Specific User in CometChatGroups Component
Current Behavior: As of now, using the GroupsRequestBuilder, we have the ability to: Set.joinedOnly(true) to fetch only the groups the current user has already joined. Set.joinedOnly(false) to fetch all available groups (regardless of the user's membership status). However, in the context of the CometChatGroups component, this behavior is not fully supported. There is no built-in way to filter and show only the groups that a particular user has not joined. Feature: The ability to filter groups based on users who have not joined them.
💡 Feature Request
Idea
Support for Pasting Images from Clipboard into Chat Input
Currently,chat input does not support pasting images directly from the clipboard (e.g., screenshots or copied web images). Expected Behavior: When an image is copied to the clipboard (from a browser, screenshot tool, or system clipboard), pasting (Cmd+V or Ctrl+V) into the chat input ,image or data should be sent as a message
💡 Feature Request
Idea
Support for Pasting Images from Clipboard into Chat Input
Currently,chat input does not support pasting images directly from the clipboard (e.g., screenshots or copied web images). Expected Behavior: When an image is copied to the clipboard (from a browser, screenshot tool, or system clipboard), pasting (Cmd+V or Ctrl+V) into the chat input ,image or data should be sent as a message
💡 Feature Request
Idea
Ability to Fetch Conversations Excluding Specific Tags
The current CometChat API provides the ability to fetch conversations that include specific tags, which is helpful for targeted filtering. However, it does not yet support the option to exclude conversations based on tags.
💡 Feature Request
Idea
Ability to Fetch Conversations Excluding Specific Tags
The current CometChat API provides the ability to fetch conversations that include specific tags, which is helpful for targeted filtering. However, it does not yet support the option to exclude conversations based on tags.
💡 Feature Request
Idea
Enable Drag-and-Drop functionality for sending Media Files
Add built-in support in the CometChat UI Kit for drag-and-drop file in the chat area. Users should be able to drag files (images, documents, audio, etc.) directly into the chat window for sending.
💡 Feature Request
Idea
Enable Drag-and-Drop functionality for sending Media Files
Add built-in support in the CometChat UI Kit for drag-and-drop file in the chat area. Users should be able to drag files (images, documents, audio, etc.) directly into the chat window for sending.
💡 Feature Request
Idea
Ability to Filter Out Already Added Group Members in CometChatUsers Component
Currently, the CometChatUsers component lists all users, regardless of their group membership status. Ideal Behaviour: The ideal and expected behavior is that once a user is added to a group, they should automatically be excluded from the list in the CometChatUsers component. There should be a built-in mechanism or prop that allows this filtering to happen seamlessly.
💡 Feature Request
Idea
Ability to Filter Out Already Added Group Members in CometChatUsers Component
Currently, the CometChatUsers component lists all users, regardless of their group membership status. Ideal Behaviour: The ideal and expected behavior is that once a user is added to a group, they should automatically be excluded from the list in the CometChatUsers component. There should be a built-in mechanism or prop that allows this filtering to happen seamlessly.
💡 Feature Request