Voice Messaging needs much more care

Description:

Audio (Voice) Messages are an important feature in all messaging services. Unfortunately I see no care to any bugs related to this in the last year.

I've opened a couple of issues with partially breaking issues and it seems the RC team is not interested to at least fix this. I've got a use case of >40% of audio messages and users are - open speech - pissed that all the issues are still there.

In Detail:

• iPhones are going into sleep during recording and the voice message is fully lost #2779
• When you miss to exactly hit the small green hook to send the message it's fully lost #3078
• When you get a call, the alarm clock runs off etc. during recording, the message is fully lost #3002
• The message length is displayed wrong, scrubber does not work correctly #2586
• Playback of voice messages does not continue in background (app needs to be in the foreground during playback all the time) #2578

Matrix/Element as well as Nextcloud Talk introduced Voice Messaging in the last weeks and even in the first implementations it's much better than in RC. Element's UI is like WhatsApp, in both solutions the length is correct, playback continues when the app runs in background, the smartphone is not falling asleep etc.

What is the plan / roadmap regarding voice messages in short term (this year)? @diegolmello mentioned months ago the UI should be reworked also in a way like WhatsApp - but nothing happens, even serious issues are not ironed out.

Start by reviewing the referenced issues #2779, #3078, #3002, #2586, and #2578 to separate the recording, interruption, duration, and playback problems. The issue names no implementation files or tests; done would require an agreed short-term voice-messaging plan and clearly scoped follow-up work.