Introduction
The app is a tool created to assist you on your learning journey.
Manually logging Classic Button presses allows you to review which buttons are pressed when, in what sequences, and look for trends in presses over time.
Connect Button presses are logged in the app automatically.
Adding notes and additional context allows you to help your learner work through challenges with each button.
The app is also connected to a broader research effort to understand:
How communication through buttons works
What learners are learning
How to improve on best practices.
There's a robust research community as well; you are welcome to join. By applying to join this effort, you will be connected with a community of like-minded button communication enthusiasts.
Basic Overview
There are three main mechanics for logging data in the app:
Household - define who presses buttons
Activity feed - review / filter / summarize past button presses
Logging - define what buttons were pressed when, in what context.
Household
From this tab, you can add details on teachers (humans) and learners (animals). This allows you to specify who pressed buttons.
Activity Feed
This is where you can review past button presses. You can:
Filter to see presses of specific buttons, or multi-press sequences, or all presses by a specific learner in a time range.
Favorite, so you can review your favorite events from the past
Delete, so you can remove irrelevant events.
 |  |
Activity feed | Filtering feed by a presser gives extra data |
Logging
With the FluentPet Connect system, all button presses will automatically logged in the app. In addition, you can:
Edit events to add context, notes, and more.
Add other events by tapping the big "+" button in the lower right of the activity screen, you can add events to your feed.
Log Button Press- In case a press was missed or you are working with some "Classic" (i.e. sound-only) buttons, you can manually log a button press.
Add Journal Entry- allows you to make quick, time-stamped notes for convenient future reference. These notes can be anything you deem potentially relevant.
Key values that you can get by keeping a history of presses:
In early stages, this helps you keep track of your modeling events and your learner’s progress.
Later on, it becomes a critical piece to properly deciphering more complex communication from your learner.
Adding Context helps you better understand how your learner is using (or not using) specific buttons, by labeling presses such as accidental, requests, experimentation, etc
Add Notes helps paint the full picture in between a seemingly cryptic press (e.g. "WANT"), as you review for consistency in what's pressed when.
 | 
|
Logging a button press helps fill in gaps and work with Classic buttons | Logging a note helps preserve context |