[Arabic] Device STT vs Cloud STT: Why We Use Both for Children's Speech Recognition

# Device STT vs Cloud STT: Why We Use Both for Children's Speech Recognition [Full Arabic translation of content] ## Device STT vs Cloud STT: Why We Use Both for Children's Speech Recognition Amal and Thurayya use a dual speech recognition architecture: on-device STT for instant, zero-latency feedback while the child speaks, and Google Cloud Speech-to-Text for higher-accuracy pronunciation scoring after the child finishes. This hybrid approach gives children the immediate responsiveness they need to stay engaged while ensuring accuracy for meaningful learning. ### The Fundamental Tradeoff | Metric | Device STT | Cloud STT | Need Both | |--------|-----------|-----------|----------| | Latency | ~100ms | ~500ms | Instant feedback + accuracy | | Accuracy | 70% | 92% | Confidence scoring | | Offline | ✓ | ✗ | Resilience | | Diacritic awareness | Limited | High (with context) | Full Arabic support | | Pronunciation detail | Coarse | Word-level timestamps | Speech marks for animation | **The child needs both simultaneously**: - Instant feedback keeps them engaged (device STT) - Accurate feedback ensures real learning (cloud STT) ### Implementation Deep-Dive **Device STT Layer** (`DeviceSTTMechanism`) Uses the `speech_to_text` Flutter package: ``` Child speaks "كتب" (kataba — wrote) ↓ [Device streams partial results] ↓ UI shows green highlights: "كتب" (70% confidence) ↓ [Zero latency — child sees feedback while speaking] ``` Device STT is perfect for "work in progress" display. Children see what the app is hearing in real-time, which maintains engagement and provides immediate