Skip to content

Families

Start with connection. Keep communication theirs.

EyeSay gives a communicator a stable language map, a separate context layer and permanently reachable self-advocacy language. Families can model on the same map without putting words into the communicator's mouth.

The family idea

A communication system should fit into family life — not turn family life into therapy homework.

EyeSay is designed around a stable Voice Canvas for learned motor locations, a Context Halo that can offer situational possibilities without deciding intent, and an Agency Strip that keeps essential self-advocacy available. The communicator remains the author: suggestions do not speak for them, and partner modelling stays separate from their own utterance and history.

Modelling at home

Show language in moments that are already happening.

Aided-language modelling means a communication partner demonstrates words on the AAC system while talking naturally. In EyeSay, Model Mode uses the same stable topology the communicator sees, but it never puts words into your child's ribbon, never makes their device speak, and never writes into their message history. Their voice stays theirs.

Snack

Model MORE, DIFFERENT, LIKE or NO — then keep the interaction moving.

Getting ready

Model NOT YET, HELP, WHERE? or BREAK without turning the routine into a quiz.

Play

Model comments such as FUN, WOW, AGAIN or a person's name — not only requests.

Hard moments

Model STOP, HELP, I DON'T WANT or SOMETHING ELSE and respect the message if it is chosen.

Model without demand

Model because language is useful in the moment, not to make the communicator copy you. Avoid “say this”, repeated prompting, hand-over-hand selection or withholding an activity until they reproduce the model. A model can stand on its own as an example.

Self-advocacy

Refusal and escape language are communication too.

EyeSay keeps core agency language reachable rather than treating it as vocabulary that must be earned. If a communicator chooses NO, STOP, BREAK or I DON'T WANT, the respectful response is to treat it as communication — not as an error to correct.

  • NO
  • STOP
  • HELP
  • BREAK
  • TOILET
  • I DON'T WANT
  • NOT YET
  • SOMETHING ELSE

What stays where

Raw communication is treated differently from adult-managed setup.

Device-local by design

In the current build, the communicator's message history, Show Me photos, browser microphone input and continuous location are not uploaded to EyeSay's cloud. Speech uses the device's built-in voices. Local data can still be reachable through an unlocked device or device-level backups configured by its owner.

Account-managed configuration

Adult account identity, communicator configuration, vocabulary definitions, routines, team roles and derived measures can be processed in the authenticated console so authorised adults can manage the service. Adults do not receive a cloud transcript of what the communicator said.

For the current data inventory, lawful bases and retention details, read the Privacy Notice.

Current delivery and access

Know what the current product is — and what is still being hardened.

Installable web app today

EyeSay is currently delivered through the browser as an installable Progressive Web App (PWA), not as a native App Store application. It can be added to a supported device's home screen. Offline behaviour is being hardened and tested across devices, so families should verify the exact offline workflow on their own device before relying on it away from connectivity.

Access-method limits are explicit

The current product prioritises direct touch and keyboard-accessible interaction. Dedicated switch-scanning profiles, formal eye-gaze validation, keyguard-specific layouts and broader specialist hardware compatibility are active roadmap items and should not be assumed supported until they are documented and tested.

See the Accessibility page for the current published capability and roadmap boundary.

A calm first week

Begin with access, modelling and ordinary life.

  1. Days 1–2

    Make it reachable, not demanding

    Put EyeSay where it can be reached during ordinary life. Explore a few stable words yourself. Do not turn the app into a test, and do not require a response before continuing the activity.

  2. Days 3–4

    Model words that matter now

    Use Model Mode during real moments: MORE at snack time, NOT YET while getting ready, HELP when something is difficult, or a comment during a favourite activity. A model is a demonstration, not a prompt for imitation.

  3. Days 5–7

    Set up their routines without moving the map

    Set up the routines that shape their day through the adult setup. Context can then surface useful possibilities around the stable motor map without relocating learned positions. Recording a child's own people, places and interests so those words appear is in development — see product status.

Next steps

Explore the app, then bring the same approach to the wider team.

Families can open EyeSay directly. SLPs, teachers and other communication partners can use the Professionals guide for modelling, motor-topology and implementation context.