[FEAT]: App: 1:1 voice call screen with flutter_webrtc

未关闭
#199 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
35/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
dart, flutter

调研方向

Start by reading the signalling and TURN sub-issues linked from #33, then find the direct chat call button and the app’s call-screen entry points. Use flutter_webrtc for the in-app voice call flow and check how chat entries are represented. Done means the listed call states and controls work, microphone permission is handled gracefully, and missed calls appear in chat; calls with the app closed are out of scope.

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

描述

area: mobile blocked difficulty: hard enhancement

Part of #33. Needs the signalling and TURN sub-issues.

What to do

  • A call button in a direct chat starts a voice call.
  • Incoming call screen (accept / decline) while the app is open.
  • In-call screen: mute, speaker, timer, hang up.
  • States: ringing, connected, ended, missed. Add a "missed call" entry in the chat.
  • Microphone permission handled gracefully.

Good to know

flutter_webrtc is free software and fine for F-Droid. Don't add Firebase or FCM. Calls when the app is closed are out of scope here.

主要语言
Dart
星标
9
派生
5
平均合并
49 分钟
30 天内合并 PR
34

环境准备

  • 提供 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 没有贡献指南

从这里开始

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

CommandLineCoding/Elephant 的其他 Issue

查看 CommandLineCoding/Elephant 的全部 Issue

相似的 Issue

更多 Dart Issue

把新 issue 发到你的邮箱

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