Device Buttons

Purpose

This page lists the name and usage of each button on the device when used in both the System Module and Content Modules (unless overridden by the content module's metadata). See the contexts page for a description of the various device contexts, which affect how the device responds to a tap or hold of the button.

Ways to Activate a Feature with a Button

Tap
to press a button and then release it within 1.0 second
Hold
to press and hold a button for greater than 1.0 seconds before releasing it. Holding a button for longer than 1.0 seconds is ignored. Whether the user continues to hold the button or not, the device will only respond to the next button to be tapped or held. This will be the case unless otherwise specified.

See contentschema:elements-onbutton for lower-level definitions of "press", "hold", and "release".

Buttons

  1. Play/Pause
  2. Left
  3. Right
  4. Up
  5. Down
  6. Select
  7. Record
  8. Home
  9. Volume Up
  10. Volume Down

1. Play/Pause

  • When content is being played, tap once to pause. Tap again to continue.
  • Functions the same as the Select button when prompted with the title of a content module during the selection process as well as in any situation where content is not immediately playable.
  • Functions the same during recording as it does during playback (pauses recording and then plays back what was just recorded if pressed again, or if record button is pressed, pause is released and recording continues.
  • * See play and record for details.

2. Left

  • When content is being played, tapping this button causes a jump 15 seconds back (unless overridden by the content module, as will usually be done by literacy content, e.g. the previous word or line of text).
  • Can be overridden by a content module to act as a multiple choice input
  • The "back 15 seconds" function of this button (typically used for info content) may cause this button to be the most used during info content. Unfortunately, it is the hardest to reach by a user holding the device in his/her right hand assuming other hand is not available.
  • This button is also used to respond to system prompts, such as with the content selection menu. In general left arrow takes user to previous range of options as the back would function on a browser.
  • See nav and selection for details.

3. Right

  • When content is being played, tapping this button causes a jump 60 seconds forward (unless overridden by the content module, as will usually be done by literacy content, e.g. the next word or line of text).
  • Can be overridden by a content module to act as a multiple choice input
  • This button is also used to respond to system prompts, such as with the content selection menu. It tipically works as the select button and Play/pause in the sense that it selects an option from multiple choices when navigating menus.
  • See nav and selection for details.

4. Up

  • When content is being played, tapping this button causes a jump back to the beginning of the previous segment of audio (unless overridden by the content module, as will usually be done by literacy content, e.g. the previous page)
  • Can be overridden by a content module to act as a multiple choice input
  • This button is also used to respond to system prompts, such as with the content selection menu. It tipically allows together with the down arrow to move between multiple choices on menus.
  • See nav and selection for details.

5. Down

  • When content is being played, tapping this button causes a jump forward to the beginning of the next segment of audio (unless overridden by the content module, as will usually be done by literacy content, e.g. the next page)
  • Can be overridden by a content module to act as a multiple choice input
  • This button is also used to respond to system prompts, such as with the content selection menu. It tipically allows together with the up arrow to move between multiple choices on menus.

6. Select

  • This button has been called the "hyperlink button" in the past. We will call it the "select" button since 1) it can be used as a select button to respond to system audio file prompts, and 2) users may understand hyperlinking as simply selecting the current part of the playback to find out more about it.
  • See hyperlink and selection for details.

7. Record

  • Is Home the only operable context for this button? What happens if it is pushed during playback? Can a content module ever prompt a user to make a recording? This could be an interesting feature for v2, but probably not now.

This button is off limits for content modules to override.

8. Home

  • Need to figure out where to put the spec for this button.
  • Overriding the tap action of this button by content modules is off-limits. It is defined only by the System Module.
  • //After tapping this button during content play, the user can hold it to go back to the last content module played.

When this button is held, it takes user into help mode. For contexts with specific help files assigned, such help files are played. Holding it again takes user to content module last played.

Content modules with contextual or other forms of help will take advantage of the hyperlink mechanism to make such help available to the user. This button cannot be deactivated or redefined in any way by content modules.

9. Volume Up

  • Overriding the functionality of this button (both tap and hold?) by content modules is off-limits. It is defined only by the System Module.
  • See device-volume for details.

10. Volume Down

  • Overriding the functionality of this button (both tap and hold?) by content modules is off-limits. It is defined only by the System Module.
  • See device-volume for details.