socialFLO API: More Details

SocialFLO is the smartphone app and portal that wearers use to configure their digital eyewear. Over the past year we’ve received numerous emails about what developers can do with our digital eyewear via our forthcoming API. Today we elaborate on what we have been planning and what we will release.

The API

Developers are exposed to the following inputs and outputs.

Eyewear

audioLevel (integer)
0 to 11
wearerHeading (number): A scalar representing the direction the wearer’s head is pointed on the XZ plane in degrees.
0 to 360
wearerPitch(number): A scalar representing the direction the wearer’s head is pointed on the YZ plane in degrees.
0 to 360
touchpadInput (array): Allows developers to map inputs that the wearer makes on the touchpad to custom actions in a developer’s mod. It includes one, two, and three finger swipes. Wearers can swap left-hand and right-hand functions via Settings in their socialFLO app.
TouchPad_L
Tap
Swipe 1 YZ
Swipe 2 YZ
Swipe 3 YZ
TouchPad_R
Tap
Swipe 1 YZ
Swipe 2 YZ
Swipe 3 YZ
buttonInput (array): Allows developers to map inputs from the 6 buttons on the eyewear to custom actions in a developer’s mod.
R1, R2, R3
Press
Hold
By default R3 is home button
By default R1 is back button
L1, L2, L3
Press
Hold
If user engages left handed configuration L3 defaults to home button
If user engages left handed configuration L1 defaults to back button
lowPower (boolean): Alerts developer’s mod and wearer to Low Power mode. Allows developers to adapt their mod’s behavior to fewer resources being available.
Mode (string): “X”, “D”, “N”, “A”: Indicates to developer’s mod and wearer the current mode. Wearers can override the automatic engagement of Drive and Active mode. When a wearer overrides a mode, it is logged and this data is used in accordance with the terms of use of the eyewear.
X: eXperimental mode is only accessible by developers (and a limited number of the developer's users). In this mode, developers have the option to lock the eyewear into certain modes or to override certain modes. Experimental mode also has no content restrictions from LAFORGE Optical, as this mode is for developers to use our eyewear for R&D and other emerging purposes. In other modes, LAFORGE may impose certain limitations on device capability for the “greater good” of the company or the public. We do not know the full potential of future developer’s creativity or the limits of public acceptance, there may be some cases where the company has not determined the legal or financial impact of allowing certain mods to be used.. However, there may be cases in which a mod created on our platform provides a novel use case of our eyewear, and proves to be beneficial to the company in the press, and/or to the "greater good" of humanity. Experimental mode is a ‘catchall’ for these cases. The company will also log when a device has been put into experimental mode and use this data in accordance with the terms of use of the eyewear.
D: Drive mode imposes the most limits on content that the wearer is able to view. Drive mode automatically engages at speeds above 17mph, further increases the text size of mods, reduces the level of fidelity to other active mods to just metadata, and will also completely prevent certain mods from being accessed or viewed. Drive mode also begins to look for data relevant to driving, such as navigation instructions and content from an automobile that may be useful to the wearer.
N: Normal mode has the least amount of limitation available to a wearer. Wearers have the ability to see mods in the highest fidelity specified by the mod developer as well as the ability to view multiple mods at the same time.
A: Active mode engages when the wearer exceeds a speed of approximately 5mph. GhOSt may increase the font size of mods and decrease the fidelity (level of detail) of text. Active mode also begins looking for data that is coming from the wearer’s health and fitness mods and will more prominently display this content.

SocialFLO

Wearer settings
Mod_Fidelity(String): Indicates the level of detail a mod is displayed to a wearer. Please see image under “additional information” to preview this.
Basic
appIconBadge
1_1
1_2
1_3
1_4
Handedness (Boolean)
Left
Right
Brightness (Integer)
0 to 11
Wearer info
larpNumber (string): Every wearer is assigned an identification number. The LAFORGE Augmented Reality Portal number allows wearers to transfer their settings, stats, achievements, and other metadata from one device to another. Developers can get more information about a wearer by accessing their LARP number.Every wearer is assigned an identification number: The LAFORGE Augmented Reality Portal (LARP) number. LARP allows wearers to transfer their settings, stats, achievements, and other metadata from one device to another. Also, developers can get more information about a wearer by accessing the user’sLARP number.
wearerAge (integer)
wearerLanguage: Initially, limited to US English and British English. May be expanded to Korean, Japanese, Chinese, German, and French at later date.
wearerCourse (number): A scalar indicating direction of movement on the XZ plane in degrees.
0 to 360

We believe that exposing developers to these inputs and outputs will unlock a wave of creativity and benefits for wearers of LAFORGE digital eyewear. As more developers use the API we will add more capability to the API.

Check back regularly as we will be providing more details and examples for the SDK and API soon.