- Print
- DarkLight
Typically, an application has a presentation layer that handles the formatting of the display to the user interface. Often, this is the layer where the majority of the Z100 integration will occur. We can simply add another layer below the presentation to handle the Z100 presentation.
As information is received for display in the presentation layer, it is evaluated to see if it would be relevant to the Z100. If so, it is sent to the Z100 presentation layer.
The Z100 presentation layer may choose to discard or cache the information when the Z100 is not connected. This allows the app to behave normally for users who do not have a Z100. Their information is shown only on the phone screen.
For users with a Z100 is connected, the relevant information will also be sent to the glasses as a secondary display to the phone. The user can then put their phone away and keep using your app with just the glasses display. And if they need more information, or more controls, they can still use the phone.
There may be a small amount of application logic desired to manage the Z100, such as storing settings to decide what information the user wants to see on the glasses. On iOS there is also a simple connection process that the application must follow to allow the app to talk to the glasses.
By treating the Z100 as a secondary display with a subset of the total information, you can easily add support for the Z100 with minimal impact to the overall application.