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.
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.