Connect to Armor
Discover and connect glasses, read device state, and work with the SDK’s event model.
Start with a connection →LUCYD ARMOR · DEVELOPER PLATFORM
Public platform coming 2027 View roadmap →
Bring hands-free experiences into your existing technology. Use the Lucyd SDK in your Android or iOS app to connect Armor glasses with your people, workflows, and services.
BUILT AROUND YOUR APP
Your mobile app runs the experience. The SDK connects it to the glasses. Your backend continues to own business logic, data, and integrations.
Discover and connect glasses, read device state, and work with the SDK’s event model.
Start with a connection →Explore Android AAR and iOS XCFramework integration, native code examples, and API availability by release.
Browse the SDK reference →Link an Armor-enabled app to training, work orders, knowledge bases, and your existing enterprise systems.
Plan your integration →ARMOR 2.0 DEVICE FAMILY
Connection, device status, audio and EQ form the shared SDK foundation. Camera and light capabilities depend on the model and the delivered firmware.
The examples show planned SDK capabilities. Supported operations and device compatibility will be documented with each release. Read platform plans →
A FAMILIAR STARTING POINT
Start with discovery, user-selected connection and device events. The preview docs show illustrative API patterns and workflows; final API names will be published with the SDK.
Android & iOS examples →// Illustrative API names; final package and signatures will be announced with the SDK.
val sdk = ArmorDevice(context.applicationContext)
sdk.onEvent = { event ->
when (event) {
is ArmorEvent.Discovered ->
showDevice(event.device)
is ArmorEvent.Battery ->
showBattery(event.percent)
else -> Unit
}
}
// On main, after permissions are granted:
sdk.startScan()YOUR TECHNOLOGY. YOUR WORKFLOW.
A service organization could add voice guidance to its training app, let a technician capture a part or repair step on Armor Pro, and attach the resulting file to a work order. Your team controls the application and connects it to the systems you already run.
These are integration scenarios built around planned SDK capabilities. Your pilot should validate the exact model, firmware and SDK release.
Explore enterprise patterns →Device input, audio output and model-specific capture.
Connection, permissions, device events and app experience.
Training content, work orders, AI, identity and business data.
PREPARING FOR 2027
The portal will bring together developer onboarding, SDK releases, documentation, samples and partner resources. Explore the documentation now and preview how an access request will look.