nextcloud / nextcloud/talk-ios

Better voice message handling

Open
#1,261 0 comments 6 reactions 0 assignees View on GitHub
0. Needs triage enhancement
Dominant language
Swift
Stars
230
Forks
121
Avg merge
1d 6h
Merged PRs (30d)
38

Description

**Is your feature request related to a problem? Please describe.**
Voice messages work but could be handled better in my opinion.

**Describe the solution you'd like**
A few things I've noticed, in order of importance:
- there is no sign that indicates whether the voice message that has just been recorded is being sent to the server or discarded, the user just has to cross their fingers and wait until it appears (or not) in the chat
- if a voice message can't be sent to the server (e.g. you've switched 4/5G<->WiFi), it would be great to be able to re-send it without having to re-record it from scratch
- the scrubbing doesn't work well when voice messages are playing, they first have to be stopped (and even then, it's hard to grab the round "handle" to move it, I suspect the active area should be made larger)
- almost all messaging apps currently implement some form of different playback speeds, good options would be 0.5x, 1x, 1.5x, 2x in my opinion. This is missing at the moment
- related to the above: Telegram and Whatsapp have recently introduced an additional bar at the top that shows if a voice message is being played, which is permanent throughout the chats and allows to toggle between playback speeds, would be nice to have to be able to read other chats while listening to a voice message

**Describe alternatives you've considered**
Not applicable.

**Additional context**
Talk iOS 16.0.2.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.