Feature request: iOS text-to-speech support for received messages
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- ios
- Domain
- accessibility, mobile
Research direction
Start by locating the iOS app’s received-message view and its accessibility or playback controls; the issue does not name specific files or tests. Read how messages are displayed and how the app currently uses native iOS APIs. Done means users can play a received message with the configured system voice, with playback controls; automatic reading is optional.
Written by the indexing model from the issue text.
Description
Description
It would be very useful to have an accessibility feature in the MeshCore iOS app that allows received messages to be read aloud using the iPhone’s built-in text-to-speech functionality.
The main purpose would be to make MeshCore more accessible for people with dyslexia, visual impairments, or other reading difficulties.
Suggested functionality
A simple option could be added to received messages, for example:
A “Read Aloud” button or menu option on each message.
Use the native iOS text-to-speech engine and the user’s configured system voice/language.
Optionally, an accessibility setting could enable automatic reading of newly received messages.
Playback controls such as stop/pause would also be helpful.
Why this would be useful
MeshCore can be used in situations where quickly understanding a message is important. For users with dyslexia or other reading difficulties, having messages spoken aloud would significantly improve accessibility and usability.
Using Apple's built-in text-to-speech capabilities should also mean that no external text-to-speech service or internet connection is required.
Platform
iOS / iPhone
Example use case
A user receives a message through MeshCore and taps the message or an accessibility button. The iPhone then reads the message aloud using the configured iOS system voice.
This could make MeshCore considerably more accessible without changing how messages are transmitted or stored.
- Dominant language
- C
- Stars
- 3.9k
- Forks
- 1.5k
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 24
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from meshcore-dev/MeshCore
-
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
meshcore-dev/MeshCore#3622 ·
Maintainers usually reply within 1 day
-
[Feature Request] Set Australia (Mid) Preset to automatically enable 2 byte default path hash sizeOpen
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
meshcore-dev/MeshCore#3571 · 5 reactions ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
meshcore-dev/MeshCore#3567 · 1 comment ·
Maintainers usually reply within 1 day
-
RTC_RX8130CE writes and reads the one-hot WEEK register as a numberPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
meshcore-dev/MeshCore#3549 ·
Maintainers usually reply within 1 day
-
Repeater: CLI reply to 'setperm <key> 0' is lost when the removed ACL entry sits before the requester (stale ClientInfo* after array shift)Possibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
meshcore-dev/MeshCore#3513 ·
Maintainers usually reply within 1 day
All issues in meshcore-dev/MeshCore
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
sumatrapdfreader/sumatrapdf#6403 ·
-
followup
Difficulty 1/5 Under an hour Newbie friendliness 83/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
oetiker/rrdtool-1.x#1392 ·
-
bottomless: finished S3 upload tasks are never reaped, so sqld memory grows by ~10 KB per WAL batchOpen
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
tursodatabase/libsql#2298 ·
-
enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 85/100