feature request: in-app notification sound

未关闭
#7,192 2 条评论 2 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

@psrsingh 已经在做这个了。

开始于 2026年5月16日。

  • #7327 来自 @psrsingh —— 已关闭,未合并

评估

难度
4/5
预计耗时
3-5 天
新手友好度
48/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
冷清
技术栈
react-native, typescript
领域
mobile

调研方向

首先跟踪房间设置如何通过 rooms.saveNotification 提供 audioNotificationValue,以及移动客户端中在哪里触发应用内通知。在决定预设、本地下载、选择和播放如何组合之前,先检查现有的声音资源和通知流程。完成标准是:对于有效的应用内通知,播放所选的房间声音,并在需要时使用捆绑的 fallback。

由索引模型根据 Issue 内容生成。

描述

🎉 feature type: feature
Feature Description

Currently, the mobile application allows users to select a notification sound (audioNotificationValue) which is successfully saved on the backend via rooms.saveNotification . However, this preference is not respected by the mobile client when in-app notifications are triggered.

This feature proposes enabling the mobile app to play the selected notification sound for in-app messages, ensuring that user preferences are fully applied.

The implementation should:

  • Read the audioNotificationValue from room settings
  • Map it to corresponding sound asset
  • Trigger playback when a valid notification event occurs
Motivation and Use Case

Why this matters

Users expect their notification settings to actually affect behavior. Right now:

  • Changing notification sound has no effect in the mobile app
  • This creates confusion and inconsistency between backend settings and user experience

Use cases

  • A user sets different sounds for different rooms → helps identify message source instantly
  • A user prefers subtle vs loud sounds → improves usability in different environments
  • Teams relying on notifications → need quick auditory distinction

Impact

  • Fixes a broken UX expectation
  • Aligns mobile behavior with backend/web capabilities
  • Improves personalization and usability
Implementation Ideas
  1. Fetch Presets — Backend returns a list of preset sound names (e.g. ["chime", "bell", "ping"]). Each name maps to a downloadable URL, either constructed on the client or returned directly by the API.

  2. Download on Demand — Each preset is shown with a Download button. On tap, the file is downloaded to documentDirectory/notification_sounds/<name>.mp3 via expo-file-system. Download is skipped if the file already exists locally.

  3. UI States — Each preset tracks its own state: not downloaded → downloading → downloaded → selected. User can also preview before selecting.

  4. Private Storage — Files are saved to documentDirectory, which is sandboxed to the app on both iOS and Android. Not visible to other apps or the device media library.

  5. Persist Selection — Active sound preference is saved to AsyncStorage or the existing room settings store as the local file path.

  6. Playback — On in-app notification trigger, resolve the saved path and play via expo-av. Falls back to a bundled default if the file is missing or not yet downloaded.

Is this feature available in the API or web version?

Available in Web Version

Rocket.Chat Server Version

No response

Rocket.Chat App Version

No response

Device Name

No response

OS Version

No response

Additional Context

No response

主要语言
TypeScript
星标
2.4k
派生
1.5k
平均合并
1 天 15 小时
30 天内合并 PR
29

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

RocketChat/Rocket.Chat.ReactNative 的其他 Issue

查看 RocketChat/Rocket.Chat.ReactNative 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。