Comparing AAC App Features Without Claiming One App Fits Everyone

An AAC app comparison is most useful when it begins with the person’s communication, not a list of products. A feature can look impressive in a demonstration and still be difficult to use in the person’s daily life. Another feature may seem modest but solve an important access problem.

This guide offers questions for comparing relevant options with the communicator and an AAC professional. It does not rank apps, provide current prices or claim that a product has been tested. Record the version, device and settings used in any trial, because an app name alone does not describe the complete arrangement.

Define what the comparison needs to answer

Choose several meaningful situations. These could include talking with a friend, asking a question in a group, expressing disagreement or composing a longer message. Include settings where the person already communicates well as well as those where another option is needed.

Write down the features that appear necessary to explore those situations. Separate them from conveniences that would be welcome but are not central. For example, an access method that the person can use may be essential, while a particular case colour is a preference. Both can matter, but they answer different questions.

ASHA’s AAC Practice Portal includes user preference, communication functions, access, portability and maintenance among feature-matching considerations. This supports comparing the whole communication arrangement rather than assuming that the app with the longest specification list is the most suitable.

Look at language and expression

Ask how the app supports the language or languages the person uses with different people. Check vocabulary, grammar, voice options and how personal names or locally meaningful words can be represented. A translated menu does not by itself answer whether the communication content fits the person’s language needs.

Explore how a message is created. Can the person combine words, type, use stored phrases or move between relevant options? Ask what happens when the exact message is not already available. If personalisation is required, find out who can make changes and how the communicator participates.

Use age-respectful examples. An adult’s trial should not be limited to a child’s classroom vocabulary unless that content is actually relevant. Ask whether the system can support opinions, relationships, work, interests and questions that the person chooses.

Test the complete setup

Record the device model, operating-system version and any accessory used. A feature advertised for one platform may not be available on another. Ask the developer or service to confirm compatibility with the intended hardware before relying on a screenshot or an old review.

Try relevant settings with appropriate support. Consider the display, selection method, volume and position in the actual environment. Do not assume that a successful demonstration by an experienced professional shows how the communicator will experience an unfamiliar configuration.

Compare reasonably similar opportunities. If one option has personalised vocabulary and several days of support while another is opened for two minutes with default settings, note that difference. The result may tell you more about preparation than about the underlying app.

In a fictional example, Mateo compares two possible systems with an AAC specialist. One demonstration looks faster, but it uses prepared phrases that do not cover Mateo’s interests. During a more relevant trial, the team records how each option supports composing his own messages and correcting mistakes. They keep the comparison tied to communication rather than demonstration speed.

Check privacy and control

Communication content can be personal. Ask whether messages, recordings, photographs, custom vocabulary or usage information leave the device, who can access them and how any optional sharing is controlled. Clarify whether an account is required and what happens if a school or service manages it.

The Office of the Privacy Commissioner of Canada’s 2023 mobile-app privacy guidance recommends reviewing access to device information and permissions such as contacts, location, camera and microphone. For an AAC app, ask which permissions support a function the person wants and which are unnecessary. This general guidance does not certify the privacy of any particular app.

Review editing and observation access separately from communication access. Someone who helps maintain vocabulary does not automatically need to read every private message. Ask the communicator what support is wanted and how privacy can be preserved while necessary assistance remains available.

The NJC Communication Bill of Rights includes meaningful participation and expression of preferences and opinions. Use that professional statement as a reminder to include the communicator’s view in selection; it is not a Canadian legal ruling or a product endorsement.

Check cost and continuity before committing

Request the complete cost for the proposed arrangement. Ask about the app, device, voices, accessories, subscriptions, training and support where relevant. Confirm what is included rather than assuming a headline price covers every needed function. Current prices and funding rules require a fresh check at the time of purchase.

Ask what happens if a device is replaced, a subscription ends or the person leaves a school that controls the account. Can their personalised vocabulary and settings be retained? Who can restore a backup, and has the proposed method actually been demonstrated with non-sensitive test content?

Keep unresolved questions visible in the final comparison. “Not yet checked” is more useful than a confident tick based on a marketing phrase. If a critical feature cannot be verified, ask what additional demonstration or trial would answer the question before making a costly commitment.

Common questions