AAC Grid Navigation & Position-Stability — Competitive Research Findings

Date: 2026-07-21 Status: Complete — validates decisions 1–4 from the in-progress fixed-paged-grid design session (formal spec forthcoming) Type: Research synthesis (competitive/field research) Research provenance: deep-research run, 2026-07-20/21 — 102-agent fan-out across five research angles (competitor navigation architecture; motor-planning/position-stability evidence; SLP table-stakes settings guidance; user complaints/unmet needs; vocabulary-growth and orientation-handling mechanics). 20 sources fetched, 93 claims extracted, 25 put through adversarial verification (independent reviewer passes per claim) — 25 confirmed, 0 refuted, 0 left unverified — merged into the 7 findings below. Unlike the 2026-07-20 cell-color-formatting research run, this run completed its full synthesis pass (executive summary, caveats, open questions, source list) before ending.

TL;DR

Oso Voice’s reserved-slots decision (decision 2) is the best-supported design choice of the four examined here, by a wide margin: it is unanimously validated by vendor design philosophy across every leading motor-planning AAC system checked (LAMP Words for Life, Speak for Yourself, TD Snap Motor Plan, AssistiveWare’s Proloquo) and empirically supported by a peer-reviewed controlled experiment — Thistle et al. (2018) found preschoolers using position-stable symbol arrays located targets roughly twice as fast as peers using rearranged arrays by session 5 (~3.3s vs ~6.0s), with the stable group still improving and the variable group never improving at all. No leading competitor, however, keeps that stability across grid-size changes — TD Snap’s default layout relocates buttons when the grid resizes, and Proloquo2Go recomposes its layout per size — which means Oso Voice’s single canonical layout held stable across caregiver grid-size presets would be a genuine field differentiator, not merely a variant of something competitors already do. The other two decisions sit on weaker ground: grid-size presets (decision 3) are supported but contested (AssistiveWare rejects configurability outright for its newer product), and the paged prev/next navigation model (decision 4) has no validating evidence in either direction — it should not be marketed as research-backed.

Background

Oso Voice’s fixed paged grid — a single global vocabulary sequence, categories realized as contiguous page ranges, reserved positions for the full vocabulary with starter mode showing blanks, caregiver-selectable grid-size presets, and prev/next-plus-page-dot navigation with no swipe gesture — was arrived at during an in-progress design session (spec forthcoming). Position stability itself was already a standing, cross-corroborated design constraint (docs/decisions/006-motor-plan-position-stability.md, 2026-07-07), independently substantiated at the time by 5+ vendors and a peer-reviewed App Store review analysis. What that earlier decision hadn’t checked was the specific, field-level detail the new paged-grid design now depends on: how the field’s leading motor-planning AAC systems actually implement navigation, vocabulary growth, and grid-size selection — and, in particular, whether any of them preserve position stability across grid-size changes the way Oso Voice’s canonical-layout-plus-presets design intends to.

Adam commissioned a dedicated deep-research pass to check this before the paged-grid spec is finalized, and separately asked that the research be preserved as citable in-repo material for eventual marketing use — the same pattern established by the cell-color-formatting research (2026-07-20-cell-color-formatting-research.md). That run fanned out 102 agents across the five angles listed above, fetched 20 sources, extracted 93 claims, and adversarially verified 25 of them before merging the survivors into the 7 findings below. This document is the durable, in-repo synthesis of that run, written so it can be cited later without re-deriving it from session logs.

Findings

Findings are grouped by adversarial-verification strength. Tier 1 findings had every merged claim confirmed unanimously (3-0) by independent reviewer passes. Tier 2 findings are still confirmed — this run left nothing unverified — but carry either a split vote on one merged claim or an explicitly interpretive (synthesis, not directly-sourced) conclusion, and should be handled with correspondingly more hedging.

Tier 1 — Adversarially confirmed, 3-0 throughout

Motor-planning position stability is a deliberate, explicitly marketed design principle across every leading motor-planning AAC system examined. TD Snap Motor Plan: “each word appears only once with a distinct path.” LAMP Words for Life: “the motor plan to say a word… is consistent across time and unique from other words.” Speak for Yourself: “motor planning… remains consistent throughout the users’ lifetime” — a user’s first learned word “never changes position.” AssistiveWare: changing layouts forces users to “re-learn where the words are.” Four independent vendors state the same design intent in their own words — unanimous vendor validation of Oso Voice’s reserved-slots decision.

Sources: tobiidynavox.com/pages/td-snap-motor-plan; lampwflapp.com/about; speakforyourself.org/features; assistiveware.com/learn-aac/choosing-a-grid-size; assistiveware.com/blog/why-does-proloquo-have-a-fixed-grid-size
Verification: merged from 6 claims, all 3-0. All quotes verified verbatim on live vendor pages (July 2026).
Caveats: these are vendor design-philosophy statements, not efficacy proof. TD Snap’s Motor Plan is one page set within the app — its default Core First vocabulary is not motor-plan-fixed. Speak for Yourself’s literal “never changes position” quote covers the first learned word specifically; generalization to all words is supported by third-party SLP sources, not the primary quote alone.

Empirical support: position-stable symbol arrays sped target location, and the advantage grew with practice. In Thistle et al. (2018, American Journal of Speech-Language Pathology, peer-reviewed), preschoolers practicing with symbol arrays whose locations never changed located targets significantly faster by session 5 (~3.3s vs ~6.0s) than peers whose arrays were rearranged each session — and the variable-array group never improved at all across sessions. There was no difference in session 1; the benefit is a practice-accrued learning effect, implying that re-layouts (re-pagination on rotation, ad hoc vocabulary insertion) forfeit accumulated gains rather than merely causing momentary confusion.

Source: pubmed.ncbi.nlm.nih.gov/29860450
Verification: merged from 2 claims, both 3-0. Single peer-reviewed controlled experiment (n=24, 5 sessions).
Caveats — carry these every time this finding is cited: participants were typically developing preschoolers, not autistic AAC users; the study’s own authors call replication with AAC users “critical.” The manipulation was whole-array rearrangement per session, not incremental vocabulary growth — the same underlying principle, but not an identical scenario to Oso Voice’s “reveal blanks” mechanism.

Hide/mask on a fixed canonical layout is the field-standard vocabulary-growth mechanism — every major motor-planning system examined implements exactly Oso Voice’s “full layout is canonical, starter mode shows blanks” pattern. LAMP WFL ships staged vocabulary files (One-Hit ~83 core words → Transition → Full 3,000+) plus a Vocabulary Builder that grays out all but a chosen teaching list, with words staying “in the same location so that motor patterns learned remain consistent.” Speak for Yourself’s open/close feature lets users start with one visible word and reveal up to 13,000+ without repositioning anything. TD Snap Motor Plan’s Vocabulary Filter hides/shows words without relocating them. Proloquo2Go’s Progressive Language masks buttons so that “as you reveal new words, words the user has already learned stay in the same place.” This is the strongest-supported finding in the whole research set: masking-not- restructuring as the growth mechanism is universal among the motor-planning AAC apps examined.

Sources: lampwflapp.com/features/vocab-builder; lampwflapp.com LAMP Words for Life User Guide (PDF); speakforyourself.org/features; tobiidynavox.com/pages/td-snap-motor-plan; assistiveware.com/learn-aac/choosing-a-grid-size
Verification: merged from 7 claims, all 3-0. Four independent primary vendor sources, all verified verbatim, plus third-party corroboration (AbleNet guides for both TD Snap and SFY). Minor version drift in LAMP’s published figures (82–83 core words; 3,000–4,000+ full vocabulary, depending on version) does not affect the substance.
Note: this both validates Oso Voice’s decision 2 mechanism directly and establishes hide/mask (reversible, position-preserving) as a table-stakes setting Oso Voice needs to expose to caregivers — not an optional nicety.

Caregiver-selectable grid-size presets have direct field precedent, but configurability itself is contested across vendors. TD Snap Motor Plan is offered in exactly three fixed presets (30, 40, 66 button positions), chosen by the learner’s motor access needs. AssistiveWare’s newer Proloquo deliberately offers a single non-configurable 60-button grid (48 symbol + 12 text-only) — the opposite philosophy. Its older product, Proloquo2Go, sits at the other extreme: 23 optimized grid sizes (9–144 buttons). Oso Voice’s small preset set is mid-field practice, closest to the Motor Plan model.

Sources: tobiidynavox.com/pages/td-snap-motor-plan; assistiveware.com/blog/why-does-proloquo-have-a-fixed-grid-size; assistiveware.com/blog/adjustable-grids
Verification: merged from 3 claims, all 3-0. All primary vendor sources verified by live fetch, with third-party corroboration for Motor Plan’s three formats (CENMAC, Tek-Ninja, Tobii Dynavox white paper).

Configurable grid size carries a documented adoption hazard: caregivers tend to under-size the grid relative to what the learner could actually use. AssistiveWare’s telemetry from 10,000+ Proloquo2Go users showed almost 80% used a smaller grid than the recommended 77-button layout (30% under 20 buttons), which the vendor attributes to adults underestimating learners. Field guidance — AssistiveWare, corroborated by AbleNet and Dynamic Therapy Associates — is that grid size should be chosen by what the learner “can see and touch” (vision and motor access), never by presumed cognitive level, because every size change forces re-learning of word locations.

Sources: assistiveware.com/blog/why-does-proloquo-have-a-fixed-grid-size; assistiveware.com/learn-aac/choosing-a-grid-size
Verification: merged from claims 5 and 8, plus the hazard-specific portions of two claims whose configurability-precedent portions feed the preset finding above.
Caveat: the 80% figure is vendor self-reported telemetry, marshaled to justify AssistiveWare’s own fixed-grid product (Proloquo) — not independently audited. It’s independently echoed in a 2022 Forbes interview, but the underlying data source is still AssistiveWare’s own. AssistiveWare itself concedes grid-size opinions are “more about personal preference and less about hard evidence.”

Tier 2 — Confirmed, but carrying a split vote or interpretive synthesis

No leading competitor maintains one canonical layout that stays position-stable across grid sizes — Oso Voice’s cross-size stability would be a genuine field differentiator. TD Snap’s default “block flow” relocates buttons from dropped columns into first-available empty rows when grid size changes; position stability across sizes is achieved only via per-grid-size “saved states” after a caregiver manually repositions things. Proloquo2Go recomposes its layout per grid size — larger grids add more core words to the page rather than showing the same layout with more blanks revealed. Oso Voice’s reserved-slot canonical layout, applied unchanged across presets, would therefore be something no examined competitor currently offers — provided grid-size switching after adoption is discouraged, since every vendor examined treats size changes as a motor-plan hazard regardless of mechanism.

Sources: tobiidynavox.com/blogs/support-articles/understanding-pages-and-button-grids-in-td-snap; assistiveware.com/blog/adjustable-grids
Verification: merged from 3 claims — 2 at 3-0 (TD Snap block-flow and saved-state behavior, verified verbatim in official support docs and corroborated by a second Tobii Dynavox article), 1 at 2-1 (Proloquo2Go per-size recomposition).
Load-bearing qualification on the 2-1 claim: Proloquo2Go’s Progressive Language does provide position-stable growth within a chosen grid size — the deviation from Oso Voice’s approach applies specifically to scaling between grid sizes, not to P2G’s growth mechanism generally. Do not overstate this as “Proloquo2Go has no position-stable mechanism.”
Confidence is medium overall due to the split vote and because the differentiation conclusion is explicitly flagged by the research as interpretive synthesis, not a directly-sourced fact — no single source states “no competitor does this”; it’s inferred by combining what TD Snap and Proloquo2Go are each independently documented to do.

Navigation models diverge across the field; Oso Voice’s flat paged design matches no competitor exactly but is philosophically defensible. TD Snap’s within-page navigation is a vertically scrolling collection of grid screens (“an infinite, scrolling collection… much like a web page”) rather than fixed pages with explicit boundaries; LAMP and Speak for Yourself use fixed-position folder-branching instead. PRC-Saltillo (a major AAC vendor) explicitly argues that “communication cannot happen efficiently on an AAC device if attention must be paid to icons, categories and navigating to vocabulary.” Oso Voice’s single global sequence with contiguous category page-ranges, category-chip jumps, and explicit prev/next buttons matches no examined competitor’s structure, but its predictable spatial ordering is consistent with PRC’s minimize-navigation-attention principle — the deviation is deliberate, with the risk being unproven, not contradicted.

Sources: tobiidynavox.com/blogs/support-articles/understanding-pages-and-button-grids-in-td-snap; lampwflapp.com/about
Verification: merged from 2 claims, both 3-0 on the underlying facts (including a verbatim check against PRC’s live page, which itself contains a typo — “efficently” — confirming the quote was pulled from the real page rather than paraphrased). Confidence is medium not because either fact is shaky, but because the verdict on Oso Voice’s specific model is synthesis: no surviving claim directly evaluated a paged prev/next-plus-page-dots model, and the PRC quote is vendor philosophy corroborated only by limited independent research (Thistle 2018 supports position consistency generally; a 2015 independent LAMP evaluation was a small, uncontrolled 8-child study).
No evidence surfaced, in either direction, on any competitor’s rotation/orientation-change behavior.

Decision-Relevant Verdicts

The four design decisions below were made in the in-progress paged-grid design session, ahead of this research (spec forthcoming). This section states, per decision, what the research actually supports — no more, no less.

Decision 1 — One global curated sequence; categories as contiguous page ranges; chips jump

Verdict: field-divergent but deliberate — philosophy-aligned, unproven, not contradicted. No examined competitor structures navigation this way (Finding 7): TD Snap scrolls within a page rather than paginating with hard boundaries, and LAMP/SFY branch through folders rather than walking a flat global sequence. Nothing in the research contradicts Oso Voice’s approach — the predictable, single-order layout is consistent with PRC-Saltillo’s stated position that navigation and category-searching attention works against communication efficiency — but nothing directly validates it either. Treat this as “aligned with a named field philosophy,” not “validated by field practice or by evidence.”

Decision 2 — Reserved slots: full-vocabulary layout is canonical; starter mode shows blanks

Verdict: strongest support of the four — unanimous vendor validation plus peer-reviewed evidence. This decision is directly backed by Findings 1, 2, and 3: every motor-planning vendor examined (LAMP, SFY, TD Snap Motor Plan, Proloquo/Proloquo2Go) implements exactly this pattern — canonical full layout, vocabulary growth by hide/mask, never by relocation — and Thistle (2018) gives it the field’s only peer-reviewed efficacy evidence, with the caveat that the study population was typically developing preschoolers, not autistic AAC users. This decision has both kinds of support the other three lack: what the field does, and independent evidence that the mechanism works.

Decision 3 — Caregiver grid-size presets, orientation-invariant

Verdict: supported but contested, and split into two halves with very different footing.

Preset selection itself (Finding 4) has direct field precedent — TD Snap Motor Plan’s 30/40/66 model is close kin to Oso Voice’s preset approach — but configurability is not vendor consensus: AssistiveWare’s newer Proloquo deliberately rejects it in favor of one fixed 60-button grid, on the reasoning that resizing later breaks the motor plan and that most caregivers under-choose (Finding 5’s 80% telemetry, self-interested but the only data available on the question). Field guidance converges on choosing preset size by the learner’s vision and motor access, not presumed cognitive level, defaulting generously, and treating a post-adoption size change as a one-time, guided, hazard-aware event — not a casual settings toggle.
Orientation-invariance (holding the same canonical layout across device rotation) is entirely unvalidated — no source in this research, for any competitor, addressed rotation or orientation-change behavior at all (see Finding 7 and Open Questions). This half of decision 3 should not be described as supported by this research in either direction.

Decision 4 — Prev/next buttons + page dots, no swipe

Verdict: unvalidated — no evidence either way. No claim in this research examined swipe vs. button-based page navigation, or evaluated page-dot indicators, for any competitor. This isn’t a case of mixed or weak evidence; it’s a genuine gap — the research plan didn’t surface anything on this question, positive or negative. State this plainly rather than reaching for adjacent findings to imply support: nothing here should be cited as backing this decision.

Field Landscape at a Glance

System	Position-stability mechanism (within a configuration)	Grid-size configurability	Stable across grid-size changes?	Verified in this research?
TD Snap (Motor Plan)	Vocabulary Filter hides/shows without relocating	3 fixed presets (30/40/66), chosen by motor access	No — default “block flow” relocates buttons on resize; cross-size stability only via manual per-size “saved states”	Yes
Proloquo (current)	N/A — single fixed grid	None; deliberately non-configurable, 60 buttons (48 symbol + 12 text)	N/A	Yes
Proloquo2Go	Progressive Language masks/reveals within a chosen size	23 sizes (9–144 buttons)	No — layout recomposes per size (more core words added on larger grids) rather than same layout plus more blanks revealed	Yes (recomposition claim: 2-1 vote)
LAMP Words for Life	Staged vocabulary files + Vocabulary Builder; masked words stay in place	Not examined in this pass	Not examined	Yes (growth mechanism only)
Speak for Yourself	Open/close reveals up to 13,000+ words without repositioning	Not examined in this pass	Not examined	Yes (growth mechanism only)
TouchChat, Grid 3, CoughDrop, Avaz	—	—	—	No — zero verified findings; coverage gap

This table is the basis for Finding 6’s differentiator claim: of the systems where cross-size behavior was actually checked (TD Snap, Proloquo2Go), neither preserves position across a grid-size change. That is a documented fact about two systems, not “the field” — see Marketing Safety below.

Marketing-Safety Guidance

Mirroring the cell-color-formatting research doc’s guidance: some of this is safe to quote publicly as-is; some needs a caveat attached every time it’s used; some must not be used until re-verified or reframed.

Safe to quote as verified (with attribution, not as a Oso Voice-originated claim):

Vendor design-philosophy quotes, verbatim, attributed to their source — e.g. TD Snap’s “each word appears only once with a distinct path,” LAMP’s motor-plan-consistency language, AssistiveWare’s “re-learn where the words are.” These are safe as “here’s what leading AAC vendors say about their own design intent,” not as clinical efficacy claims — they establish field consensus on design philosophy, not proof that the philosophy produces better outcomes.
The hide/mask vocabulary-growth pattern (Finding 3) — safe to state as unanimous field practice across the four motor-planning vendors examined; this is the best-corroborated claim in the whole research set (7 merged claims, all 3-0, four independent primary sources plus third-party corroboration).
Thistle et al. (2018) — safe to cite as peer-reviewed evidence that position-stable arrays sped target location in the study, provided the population caveat travels with it every time: typically developing preschoolers, not autistic AAC users; the authors themselves call replication with AAC users critical. Never state or imply this was studied in Oso Voice’s actual user population.
Factual descriptions of competitor configurability (TD Snap’s 3 presets, Proloquo’s single fixed grid, Proloquo2Go’s 23 sizes) — safe as attributed factual comparison.

Must not be overclaimed:

“Oso Voice is the only app with position stability” — false framing. Four other vendors also implement position stability within a chosen configuration (LAMP, SFY, TD Snap Motor Plan, Proloquo’s Progressive Language). The genuine, narrower differentiator supported by this research is stability that holds across grid-size presets/changes — not position stability as a general concept.
“No competitor does X” claims are scoped to the four systems with verified findings — TD Snap, Proloquo/Proloquo2Go, LAMP WFL, and Speak for Yourself. TouchChat, Grid 3, CoughDrop, and Avaz were named in the research plan but returned zero verified findings (a coverage gap, not a finding that they lack the feature). Never extend “no competitor” language to imply the whole field or market was checked — say “of the systems examined” or name the four directly.
The cross-grid-size differentiator (Finding 6) is medium confidence, not settled fact. One of its three merged claims passed only 2-1, and the research itself flags the differentiator conclusion as interpretive synthesis rather than a directly sourced statement. Marketing language should hedge (“appears to be,” “among the systems examined”) rather than assert it flatly, and should never drop the Progressive Language qualification when Proloquo2Go is named.
The 80% AssistiveWare telemetry figure is vendor-interested data, produced to justify AssistiveWare’s own fixed-grid product decision. Usable only as an attributed claim (“AssistiveWare reports…”) — never presented as an independently audited, field-wide statistic.
Decisions 1 and 4 (global-sequence/chip navigation; prev/next-plus-page-dots, no swipe) have zero validating evidence in this research. They must never be marketed as “research-backed” or “evidence-based” — if described publicly at all, frame them as deliberate design choices, not as validated by this research.
The rotation/orientation-invariance half of decision 3 is likewise zero-evidence — do not imply competitor research supports (or contradicts) it.

Open Questions (Queued for Follow-Up)

What do actual users and caregivers complain about? App-store reviews, r/AAC, SLP blogs, and ATIA material — especially pricing/paywalls, editing complexity, and caregiver-vs-child modes. Research question C went entirely unanswered (zero surviving claims) and needs a dedicated review-mining pass before any differentiation-opportunity ranking can be produced.
Research question B (table-stakes settings) is only partially answered. Hide/mask is confirmed as table-stakes (Finding 3). Button spacing, edit-lock/kiosk mode, and per-button customization were named in the research plan but produced no surviving verified claims — still open.
How do competitors handle device rotation? Does any leading app re-paginate or re-flow the grid on orientation change? No evidence surfaced either way, so Oso Voice’s “rotation never re-paginates” intent (decision 3’s second half) remains unvalidated against field practice.
How do TouchChat, Grid 3, CoughDrop, and Avaz structure grid navigation and position stability? Four of the eight competitors named in the original research plan have no verified findings at all — and TouchChat and Grid 3 in particular are major market presences whose absence is a real coverage gap, not a null result.
Does the Thistle (2018) speed advantage replicate in autistic children who use AAC, and does incremental vocabulary reveal (as opposed to whole-array rearrangement) show the same motor-learning benefit? This is the single most consequential open question for Oso Voice’s actual population and actual growth mechanism, and the study’s own authors flag it as critical future work.

Source Coverage Note

Source mix is heavily vendor-primary: quotes are verified verbatim and appropriate for design-intent and feature-existence claims, but they establish what vendors believe and ship, not clinical efficacy — the only peer-reviewed evidence in this run (Thistle 2018) used typically developing preschoolers, not autistic AAC users. Several Oso Voice-specific comparisons in the underlying findings (“LAMP-style,” “matches reserved slots”) are researcher analogies drawn while merging claims, not statements appearing verbatim in the sources themselves. All product facts are current as of July 2026 fetches; vendor app features and page sets change with releases, so treat configurability specifics (preset counts, button-size ranges) as a snapshot, not a permanent product description.