Speech Synthesis in Mobile Apps: A Practical Integration Handbook

Imagine: your navigation app announces maneuvers, but the voice stutters, utterance order gets confused, and on Android synthesis doesn't start until reinitialization. Sound familiar? We'll show you how to properly embed Text-to-Speech into iOS and Android so it works reliably and predictably. With over 50 voice interface projects and 5 years of experience, our team ensures reliable TTS integration. We've served 20+ clients across logistics, healthcare, and education, delivering high-quality synthesis.

Text-to-Speech is a feature where native APIs provide acceptable quality out of the box without third-party dependencies. iOS AVSpeechSynthesizer and Android TextToSpeech work on-device, support Russian, and require no internet. The main work is correct integration, queue management, and voice selection.

Problems We Solve

• Initialization and queue. On Android, developers often forget to wait for onInit — as a result, speak() is ignored or crashes the app. We use a pattern with CompletableFuture or coroutines to guarantee order.
• Context loss on screen transitions. In fast scenarios (e.g., voice assistant), the utterance queue accumulates. We apply QUEUE_FLUSH with a check for active speech — this saves battery and doesn't annoy the user.
• Voice selection. Enhanced voices on iOS give natural synthesis, but if they are not on the device, they fall to nil. We implement fallback to compact and cache downloaded voices.

Why Native TTS APIs Are Better Than Cloud

Native APIs require no internet, work without latency, and do not send data to the server. Modern on-device voices (e.g., Milena on iOS or Google TTS on Android) are nearly as good as cloud counterparts, with no request limits. Native APIs are 3x faster due to zero network delay. The only downside is enhanced voice size, but downloading them in the background solves that. Apple AVSpeechSynthesizer Documentation

In one of our projects — a navigation app for a logistics company — we reduced the utterance drop rate from 15% to 0.2% by implementing proper queue management and fallback voices. The app now handles over 100,000 utterances per day without issues.

How to Avoid Utterance Loss on Context Switch

Use UtteranceProgressListener on Android and AVSpeechSynthesizerDelegate on iOS. Before starting a new utterance, check whether synthesis is active, and if so, call pauseSpeaking(at: .word) (iOS) or stop() with QUEUE_FLUSH. This ensures users hear the latest information without overlap.

How to Manage Speech Rate for Accessibility

Rate is controlled by the rate parameter: on iOS from 0.0 to 1.0 (default 0.5), on Android via setSpeechRate(float). For accessibility, provide a slider in app settings. Elderly users often select 0.35–0.4. iOS also supports SSML for precise tempo control of specific fragments.

AVSpeechSynthesizer on iOS

Basic case — three lines of code. Real production is more complex.

let synthesizer = AVSpeechSynthesizer() let utterance = AVSpeechUtterance(string: text) utterance.voice = AVSpeechSynthesisVoice(language: "ru-RU") utterance.rate = 0.5 // 0.0–1.0, default = 0.5 synthesizer.speak(utterance) 

Voices on iOS are divided into compact (built-in, ~50 MB) and enhanced (higher quality, downloadable ~300 MB). Enhanced voices use neural network synthesis. If the device hasn't downloaded them, AVSpeechSynthesisVoice(identifier: "com.apple.voice.enhanced.ru-RU.Milena") returns nil. Check and fall back to compact.

let enhanced = AVSpeechSynthesisVoice(identifier: "com.apple.voice.enhanced.ru-RU.Milena") utterance.voice = enhanced ?? AVSpeechSynthesisVoice(language: "ru-RU") 

AVAudioSession management is mandatory. TTS must work even if the app switched the session for microphone recording or music playback. Use .playback category with mixWithOthers or duckOthers as needed.

Android TextToSpeech: Initialization and Queue

TextToSpeech requires asynchronous initialization — a common mistake: calling speak() before onInit(status) returns SUCCESS.

val tts = TextToSpeech(context) { status -> if (status == TextToSpeech.SUCCESS) { tts.language = Locale("ru", "RU") // only now can we call speak() } } 

QUEUE_FLUSH — interrupts current utterance and starts new. QUEUE_ADD — adds to queue. For sequential notifications (e.g., navigation step announcements) use QUEUE_ADD. For assistant responses use QUEUE_FLUSH to avoid accumulation on fast input.

UtteranceProgressListener for tracking start and end of utterance:

tts.setOnUtteranceProgressListener(object : UtteranceProgressListener() { override fun onStart(utteranceId: String) { /* show indicator */ } override fun onDone(utteranceId: String) { /* hide indicator */ } override fun onError(utteranceId: String) { /* handle error */ } }) 

Each speak() call must have a unique utteranceId — otherwise callbacks won't work correctly.

Comparison of iOS and Android TTS

Common Errors and Their Solutions

Process of Work

1. Analysis — study usage scenarios: assistant, navigation, accessibility. Define requirements for voice, speed, queues.
2. Design — choose architecture: modular TTS service with lifecycle separate from UI. Design fallback strategies.
3. Implementation — write code with tests for edge cases: voice change, call interruption, background work. Use coroutines (Android) or async/await (iOS) for smooth integration.
4. Testing — test on real devices with various OS versions, including limited memory. Load test queue of 100+ utterances.
5. Deployment — publish module to private repository, documentation, and integration tests. Train your team.

What's Included in the Work

• Documentation: architectural description, flow diagram, API specification.
• Source code: module with comments, unit tests and UI tests.
• Test scenarios: 20+ cases (interruption, pause, voice change, initialization errors).
• Training: session with your team (1–2 hours) on maintenance and modification.
• Guarantee: we fix defects within 2 weeks after delivery.

Timeline and Cost

Basic TTS integration with queue management and voice handling — from 3 to 7 business days. Cost is calculated individually — contact us, we'll estimate your project in 1 day. We provide a fixed quote after requirements analysis. Save up to 30% compared to cloud alternatives, plus no monthly subscription fees — additional budget savings. Typical projects range from $800 for basic integration to $2,500 for complex multi-voice setups. 90% of our clients report improved user engagement after TTS integration.

Contact us for a consultation — we'll discuss your task and prepare a commercial proposal. Order TTS integration and get a stable voice interface that won't let you down when it matters most.