ButtonGriddle Field Test Guide

One page for trying ButtonGriddle with a real client. "Professional" below means whoever builds the boards (OT/SLP/ATP/teacher); "staff" means whoever presents choices day to day (DSP, caregiver, family).

What we're testing: can a professional build context boards for a real client, hand the tablet to staff, and can staff present choices and confirm understanding — without ever needing edit mode?

Everything stays on the tablet. No account, no cloud, works fully offline. Photos leave the device only inside backup files you export yourself.

1. Setup (professional, ~15 minutes)

  1. Install: open the app URL in Chrome on the tablet → menu (⋮) → Add to Home screen / Install app. Launch it once from the new icon — after that it works with no internet.
  2. Enter edit mode: tap the faint in the top-right corner 7 times quickly. The first time, you'll set a 4-digit passcode — this is the only thing separating staff view from edit mode.
  3. Optional head start: Settings → Import backup → choose demo-boards.json (get it from the project repo, demo/ folder). This replaces the starter board with four example context boards: Meals, Drinks & Snacks, Activities, Comfort.
  4. Make it real. Demo boards are text-only on purpose — real boards work best with photos of the client's actual items (their cup, their puzzle, the actual van). In edit mode: tap a button to edit it (photo, label, spoken phrase, color), tap an empty cell to add one, hold and drag to rearrange. ‹ Boards (top left) goes to the board list to add, rename, or delete boards.
  5. Voice check: Settings → pick a voice and speed the client responds to. The 🔊 Test button in any button editor previews it.
  6. Lock it in: Settings → Save current board as original setup. This is the known-good state that Reset returns to if edits go sideways. Then tap Done to leave edit mode, and hand over the tablet.

2. Daily use (staff — no passcode needed)

3. If something goes wrong

4. What to observe

5. Feedback we need

  1. Whose tablet should this live on — the client's own device, or a staff device shared across clients?
  2. Presenting 2–3 options in the moment: is hide/show + separate boards workable, or does this need a dedicated quick-present mode?
  3. The check screen: are "Yes / No / Not sure" the right three words? Should they be symbols? Configurable per client?
  4. What's missing most: first/then supports, visual timers, visual schedules, checklists, comfort/pain check-ins — what would you reach for next?
ButtonGriddle is a general participation support tool, not a medical device.