User Input

Many applications using the Z100 as a secondary display will not require any additional user input from the Z100 to operate properly. However, since incorporating the Z100 in your app allows users to put away their phone and continue using your app, it is important to consider how users will interact while wearing the glasses.

• User input can come from several sources:

• Touching the frame of the Z100

• Pressing the power button on the Z100

• Speaking to the phone app

• Screen input on the phone app

Touch Input

The Z100 is sensitive to touches to the temple arms and can report this to your application. Touching any part of the frame will send a tap event. There is no differentiation between left-side or right-side touches.

The Z100 can be configured to detect single-tap, double-taps, or triple taps touch events.  The touch reporting is the most responsive in single-tap mode since each tap is sent to the phone immediately.   In multi-tap mode, there is a short delay after detecting any tap while the glasses wait to determine if additional taps will follow. So, the glasses should be configured to detect the fewest number of unique taps that are required by the application.

Touch input can be used effectively for next/previous type navigation, for confirmations, and for start/pause type operations.

Although rare, false touch events may be detected. This is especially seen when the user adjusts the glasses or wipes their forehead. It is important to process the input with this in mind.

Power Button Input

Applications on the phone can register to be notified whenever the screen times-out and when the user presses the power button to wake or sleep the glasses. This allows your app to go into a standby mode while nothing is displayed to the user, then react properly when the user presses the button.

Developers may find it useful to intercept the power button as a user input. Please keep in mind that the user might need to dismiss the display from the glasses at any point since it is not practical to remove prescription glasses to see the unobstructed real world. Repurposing the power button as a general-purpose input is therefore discouraged. If this is required, it should only be enabled for very short durations to accomplish a specific task, such as a confirmation, such as “Really end your workout? Tap the power button to confirm.” Generally, the touch input should be used rather than the power button.

Speech Input

Speech input can be processed by the phone app.   This can be very effective in situations where the phone is being carried in a pocket or arm band. It may make sense to use another input, such as the touch input to wake the speech input.

Screen Input

In many glasses applications the phone screen is still a useful input mechanism.   For example, the phone can be used to easily select a destination, then the glasses can display the turn-by-turn information. Or the phone can configure a workout, and the glasses can display progress.