Feature Request: Support Custom Android TTS Engine Selection

Open
#143 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 2 days

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
Quiet
Tech stack
android, dart
Domain
mobile

Research direction

Start by reading the Android TTS implementation and how the TTS navigator is created, then trace where the Android system default engine is selected. Done means a host application can provide an installed engine's package name when creating the navigator and Readium uses that engine for playback.

Written by the indexing model from the issue text.

Description

upstream-issue

Currently, Readium's Android TTS implementation appears to always use the system default Android TTS engine.

This makes it impossible for host applications to let users choose a specific installed TTS engine (e.g. Google TTS, Piper, RHVoice, Samsung TTS, etc.) for Readium playback.

Please consider exposing a way to provide an Android TTS engine package name when creating the TTS navigator, so applications can select which installed engine should be used instead of always relying on the system default engine.

This would improve support for offline, privacy-focused, and third-party TTS engines without requiring users to change their device-wide Android TTS settings.

Dominant language
Dart
Stars
35
Forks
19
Avg merge
3d 10h
Merged PRs (30d)
37

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Notalib/flutter_readium

All issues in Notalib/flutter_readium

Similar issues

More Dart issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.