August 10, 2025 · current

Understanding the AAC Landscape — Full Project Research Report

The original market and evidence survey of the AAC app landscape (Proloquo2Go, TouchChat, pricing, feature norms) that motivated Oso Voice.

Augmentative and Alternative Communication (AAC) supplements or replaces speech for individuals with severe communication needs. In practice this ranges from simple picture boards to high‐tech speech‐generating apps. Children with autism or speech delays often need AAC to express needs and participate socially. However, high-tech AAC devices are often costly and complex, limiting access. For example, leading iPad apps cost ~$150–$250, and require training. By contrast, low-tech options (e.g. communication books, PECS cards) are inexpensive but much slower to use. The goal, therefore, is a mobile app that is powerful yet simple and affordable – fast enough to support real conversation but customizable to each child’s needs.

Key existing apps illustrate standard features. For example, Proloquo2Go (AssistiveWare) is a gold-standard pediatric AAC app (used by many autistic children). Proloquo offers a large built-in symbol library (25k+ images) and allows users to add custom photos, words and voices. It supports both picture-based (symbol) and text modes with word-prediction, and even bilingual output. TouchChat HD (PRC) is another full-featured app. It includes multiple vocabularies (WordPower, Gateway, etc.), full customization of pages/buttons (40k+ symbols, custom images), and adjustable access methods (switch scanning, dwell time). Both apps require no internet to generate speech, but Proloquo’s one-time price is $249.99 and TouchChat’s $149.99 (plus pricey language packs).

Key Takeaways on Existing Solutions

Modern AAC apps emphasize out-of-the-box usability with core content (to use immediately) and deep customizability. They also maximize communication speed with core vocabulary and prediction. Proloquo, for instance, uses a research-based core word set (80% of everyday language from ~200–400 words) placed in fixed locations for motor planning. Word-prediction and scalable keyboard views let literate users type faster. In summary, effective AAC apps provide rich built-in content and easy tools to tailor pages, images, and phrases to each user.

User Needs & Design Trade-offs

For young users (autism/delayed speech), the interface must be intuitive and engaging. Large visual buttons or symbols, clear language, and positive feedback are essential. Children may have fine-motor or attentional challenges, so minimizing steps is crucial. A common design is a grid of tappable icons (symbols or words) that build phrases in a “message bar”.

Customization vs. Speed

There is a tension between offering a huge personal vocabulary and keeping the interface uncluttered for quick selection. Users need access to both core words (high-frequency, general-purpose vocabulary) and fringe words (specific interests). Research shows using core vocabulary dramatically increases communication rate. In practice, we might preload core words in consistent locations so basic sentences can be formed quickly. At the same time, the system should let caregivers add personal items (favorite foods, family photos, comments) to make communication meaningful.

Interface layout also matters. A single-screen view of many buttons yields large targets (easy touch) but forces the user to remember locations; multiple pages reduce on-screen clutter but add navigation steps. Studies show this trade-off impacts speed and accuracy. Our app could use swipe or arrow navigation between pages, with “home” shortcuts for common categories. We should consider vocabulary organization (e.g. thematic pages like “People”, “Activities”, “Food”) and allow quick toggling between symbol view and text-entry view. Importantly, core words should always be quick to reach – for instance, placing verbs and pronouns on every page improves utterance speed.

Ease of Use & Learning

The app must “just work” with minimal setup. It should include pre-programmed pages of common phrases and images so a child can use it immediately, then gradually learn to modify it. Key ease-of-use features include adjustable button/grid size, simple menus, and clear icons. Tutorial videos or a guided on-boarding can help new users and families get started. Robust help and support is also advised (FAQs, support chat).

Communication Speed

Real speech is on the order of 150–200 words per minute, whereas AAC input is much slower (often 10–20 wpm with eye gaze or scanning). This huge gap is a major motivator: any design must try to boost speed. Known techniques include:

  • Rate-enhancement features: Word-prediction, abbreviation-expansion, message banking. E.g., as a child types “I wan…”, the app could suggest “I want” or “I want cookie”. According to recent research, advanced predictive models can cut typing effort dramatically – one system saved ~71% of keystrokes by predicting whole phrases, and another offline LLM-based predictor saved ~57% of motor actions versus a standard keyboard.
  • Physical access optimization: For kids who can’t touch precisely, optional switch or gaze input and scanning modes should be supported, with adjustable scan speed and dwell settings. However, note that eye-gaze is inherently slow (max ~46 wpm theoretical), so we should prioritize direct touch/tap for those who can.
  • Core vocabulary and modeling: Embedding 80% of everyday language in core words means users can say much with few selections. Also, consistent layout (motor planning) helps speed. Educating communication partners to “model” use of the app can accelerate learning.

At the same time, speed-boosting must not confuse the user. Predictions or AI suggestions should be offered passively (like smartphone autocorrect or “T9” style word suggestions) – the child still picks which to use. We must avoid any sense that the app is “taking over” the message. In our design, AI features (if any) will only suggest completions; the final selection always rests with the user or helper to ensure clarity.

Technical & Contextual Considerations

  • Offline functionality: The app must run entirely offline for core communication. While online connectivity can help download images or update libraries, basic operation (speech output, navigation, stored content) should never require internet. This means any AI/prediction engine must use on-device models or simple algorithms (e.g. an embedded language model or pre-computed n-grams), not cloud calls. Modern iPads can run lightweight neural predictors locally.
  • Hardware & platform: Targeting the iPad (iOS) means we can leverage built-in text-to-speech voices (Apple has many high-quality voices, including child voices). We should also take advantage of iOS accessibility (VoiceOver, Switch Control) so users with multiple disabilities can still navigate. Graphics and UI should be colorful and child-friendly, and possibly custom-themed for engagement.
  • User population: Since we focus on autism/delayed speech, the design must account for sensory and cognitive profiles common in ASD – e.g. strong visual interests, preference for routine, possible need for minimal distractions. We should allow adjustments (sound volume, animation on/off) and keep the UI uncluttered. Because some autistic children rely on AAC only temporarily during development, the app should be flexible: useful both for early learners (with symbols and select-and-speak) and for more advanced users (with typing/grammar support).
  • Customization workflow: We need an easy way for therapists/parents to set up and edit the vocabulary. Ideally, a secured “edit mode” lets an adult change pictures, words, voice settings without affecting the child’s data. Bulk tools (e.g. import from text files, or drag-and-drop symbol editing) would speed customization. Preloading common categories (food, feelings, school) as templates can reduce setup time.
  • Cost strategy: To undercut current apps, we should minimize licensing fees. This may mean using open-source symbol sets (e.g. the ‘ARASAAC’ or ‘TICO’ libraries) and free text-to-speech engines, or negotiating licensing for popular symbol sets. The app could be one-time purchase or a low-cost subscription. Experts suggest a one-time price below $200 to be broadly affordable; many families find anything above that cost-prohibitive. Avoiding hidden fees or required add-ons is important. We might consider grant or nonprofit funding to subsidize costs (since even our reduced price could be a barrier).

Key Questions & Next Steps

To define our PRD and refine the design, we must ask and research further:

  • Who exactly is our user? (age range, cognitive level, any physical disabilities, language skills)
  • What tasks matter most? (communication needs for requesting, commenting, socializing, academics, etc.)
  • How will we evaluate success? (communication rate, user satisfaction, social engagement?)
  • AI integration scope: How sophisticated should our predictive features be?
  • Training & support needs: How will caregivers learn the app?
  • Competitive analysis: Continue surveying existing apps for innovative ideas or gaps.
  • Offline workflow: Decide which assets (e.g. images, voices) to bundle vs. download.
  • Hardware constraints: Ensure the app runs well on older iPads and in all orientations.

Summary

A successful AAC app for children with autism/delayed speech must balance personalization with efficiency. It should launch with rich, research-based content (core words, intuitive categories) yet allow families to tailor nearly every aspect (images, phrases, voices). Communication speed can be improved via layout design and predictive assistance, but without sacrificing clarity or user control. Offline operation, cross-device compatibility, and strong support (help, tutorials) are mandatory. By draw…

Next steps: Conduct user and expert interviews (speech therapists, special-ed teachers, parents) to refine requirements. Develop prototypes of key features (e.g. vocabulary editor, prediction model). Then iterate through usability testing with actual AAC users.


Sources: Authoritative AAC research and app documentation were consulted, including recent reviews of high-tech AAC, expert feature lists  , and case studies on communication rate . These inform the recommendations above. app2speak.com,

https://www.microsoft.com/en-us/research/wp-content/uploads/2016/10/aacselfexpression-1.pdf#:~:text=of%20eye%20gaze%20input,that%20eye%20gaze%20AAC%20users

https://app2speak.com/7-must-have-features-of-a-great-aac-app-for-speech-and-communication/#:~:text=Look%20for%20an%20app%20that,time%20fee%20below%20%24200

https://app2speak.com/7-must-have-features-of-a-great-aac-app-for-speech-and-communication/#:~:text=A%20good%20AAC%20app%20should,customization%20options%20to%20look%20for

← All research