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.
Developers are exposed to the following inputs and outputs.
wearerHeading (number): A scalar representing the direction the wearer’s head is pointed on the XZ plane in degrees.
wearerPitch(number): A scalar representing the direction the wearer’s head is pointed on the YZ plane in degrees.
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.
Swipe 1 YZ
Swipe 2 YZ
Swipe 3 YZ
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.
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.
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.
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.
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.
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.