Play and Navigation

General

This location is where users can listen to content modules and where they will spend most of their time. This location is used for listening to content modules designed for literacy learning and knowledge access.

Getting into this Location:

A user selects either a content module or a particular audio segment of a content module. See selection.

Getting out of this Location:

A user must take one of the following actions to exit this location:

  • hold the Help/Home button. See behavior below.
  • tap the Record button. See behavior below.
  • slide the power switch to off. The device resumes with the Home location after power is reapplied. However, the content module will be easy to get back to, because it will have been registered at the top of the "most recently played" list once the content module was selected. See power.

Initial Actions within this Location

Once user content module has been selected, the device will:

  • register the content module at the top of the "most recently played" list.
  • play the content module from its beginning (Package OnStart)

Button Behavior in this Location

Of the ten buttons of this device buttons, five of them have a fixed behavior and five of them can be reprogrammed by the content module's metadata.

Fixed Behavior Buttons

Play/Pause:
  • Tapping this button will alternatively play and pause the currently selected content module. When paused, tapping this button will cause the content to be played, from where it was last paused (whether by user action or by a content-embedded pause, such as may occur at a segment break). If the last paused point is at the end of the content, the playback will begin at the start of the content module (Package OnStart). If the device is woken from sleep mode, play will resume just as if there was no sleep mode (Last Point Played is remembered).
  • Holding this button at any time (during playback or when paused) will cause the device to jump to the speed control menu. From there, another tap will return to the playback or pause condition that existed before this action. See speed for more information.
Volume Up/Down:
  • Tapping and holding these have the same function at all times as in system module locations, as described in volume.
Home/Help
  • Tapping this button at any time (during playback or when paused) takes user into the Help location (during playback or when paused). This will also then allow the user to easily return to where they were (Last Point Played), to jump to the Home location, or to explore the help content, i.e. to learn about the device functionality or, if provided, about the content module. See help for more.
  • Holding this button will cause the device to go straight to the system module's Home location contexts.
Record
  • Tapping this button when the content is paused, which jumps to the Record location record. There is no response if the Record button is tapped during playback.
  • Holding this button is ignored. It is not equivalent to a tap. No action is taken.

Content Programmable Buttons

  • Content Programmable Buttons basically allow the author of a content module to create metadata that specifies an action that the device should take upon a user tap or hold of the button during a certain block of time within the content module. The most common action will be the goto action; however, the destination point must remain within the same content module (package). There are two categories of content programmable buttons:
    • Select
    • Arrow Buttons
Select
  • This button has no other function (within this location) than what the content module's metadata provides for it.
  • The functionality will normally be an audio hyperlink to learn more information about the current content being played.
  • It may also be used by the content module as an "enter" or "select" button, as it can be used within the system module.
  • It is expected that this button will usually be tapped, but the content module may also assign a function to holding the button.
  • For more information, see hyperlink in the functional spec or elements-onbutton and elements-goto for a lower level view.
Arrows Buttons
  • General
    • The arrow buttons described below each have default behavior that can be overridden/reprogrammed by the content module's metadata.
    • The buttons are intended to serve two primary purposes: 1) navigation within a content module, and 2) input for interactive content applications (e.g. multiple-choice questions).
    • These functions should not conflict with each other since a content module that uses an interactive feature may not need or want the user to navigate away from the interactive part of the module – and users can always exit a misbehaving content module (see "Getting Out of This Location" above).
    • The navigation functionality of these buttons is meant to work as follows: Left and Right buttons are smaller jumps back and forward; Up and Down are larger jumps back and forward.
    • If the device is set down on top of a page, one might imagine the Left and Right arrows represent back and forth across a line of text and the Up and Down arrows represent up and down the page, even though each pair may be used for jumps of arbitrary lengths.
    • The default behavior described below is meant to work best for information content, which is the only type of content that can be recorded by the devices.
    • Literacy content requires a more complex two-level hierarchy of points in text, such as word/line or word/page or line/page. Therefore, literacy content will only be created with the content authoring product, which will make it easy for authors to indicate points in each of these two levels and then reprogram the default behavior of all four arrow buttons.
    • However, information content can be useful with break marks between only one level of audio segments (such as between chapters or topics). A second manner of navigation uses relative time jumps, which doesn't require an extra level of segmentation to be designated by the content author.

IMPORTANT NOTE
The functionality of each arrow button described below must actually be specified in the record spec. It is listed here to provide an understanding of the resulting user experience, particularly of content that has no overridden defaults, such as content recorded on the devices. During playback, the device simply processes the metadata. The implementation of the defaults described below actually happens during the authoring stage, either by the content authoring product or by the device. In the case of a device recording, a very simple set of default metadata is attached to the recording, which will enable the default behavior described below. See the record spec for a definition of that metadata (still a TO-DO item as of March 23rd).

  • Left
    • Tapping this button jumps backwards 15 seconds behind the Last Point Played. If the device was in a playback state when the button was tapped, the device plays the content module at the new position; if the device was in a paused state when the button was tapped, the device remains paused. In both cases, a brief SAF is played to indicate the jump back. If there is less than 15 seconds to the beginning of the current audio segment ( block or file) the device jumps the remaining seconds back into the previous segment. If there is less than 15 seconds before the beginning of the entire content module (elements-package]), then the current position is moved to the beginning of the content module with the device, with the device in the same playback or paused state it was in before the button tap. In this beginning-of-module case, a second SAF is played to indicate the beginning of the content (this may only be a short tone, if not a spoken word/phrase….TBD).
    • Holding this button is ignored by default (unless defined by the content module). It is not equivalent to a tap. No action is taken.
  • Right
    • Tapping this button jumps forwards 60 seconds ahead of the Last Point Played. If the device was in a playback state when the button was tapped, the device plays the content module at the new position; if the device was in a paused state when the button was tapped, the device remains paused. In both cases, a brief SAF is played to indicate the jump back. If there is less than 60 seconds left in the current audio segment ( block or file) the device jumps the remaining seconds into the next segment. If there is less than 60 seconds left in the entire content module (elements-package]), then the current position is moved to the end of the content module with the device in a paused state, regardless of whether the device was paused or playing when the button was tapped. In this end-of-module case, a second SAF is played to indicate the end of the content.
    • Holding this button is ignored by default (unless defined by the content module). It is not equivalent to a tap. No action is taken.
  • Up
    • Tapping this button jumps back to the beginning of the current audio segment, unless the button is tapped within the first 1.0 second of the beginning of the audio segment, in which case it jumps back to the beginning of the previous audio segment within the same content module; unless the Last Point Played is in the first segment of the content module, in which case it still jumps to the beginning of its segment. If the device was in a playback state when the button was tapped, the device plays the content module at the new position; if the device was in a paused state when the button was tapped, the device remains paused. In both cases, a brief SAF is played to indicate the segment jump back. If the new position is the beginning of the content module, a second SAF is played to indicate the beginning of the content (this may only be a short tone, if not a spoken word/phrase….TBD).
    • Holding this button moves the current position to the beginning of the content module, just as if the same button was tapped more times than there are previous content segments.
  • Down
    • Tapping this button jumps forward to the beginning of the next audio segment or to the end of the content module if there is no next audio segment. If the device was in a playback state and not in the last audio segment of the content module when the button was tapped, the device plays the content module at the new position; otherwise, the device remains paused (or becomes paused in the end-of-module case). In all cases, a brief SAF is played to indicate the segment jump forward. If the new position is the end of the content module, a second SAF is played to indicate the end of the content (this may only be a short tone, if not a spoken word/phrase….TBD).
    • Holding this button moves the current position to the end of the content module, just as if the same button was tapped more times than there are following content segments.