Developer preview
Enterprise integration
Bring Lucyd Armor into a mobile workflow that already connects your people, systems and business data.
Example: training and field service
A distributed service business could extend its training app with hands-free audio, then use an Armor Pro capture to document a part or a repair step. The phone app associates that file with the current job and submits it to the company’s existing work-order service.
The company keeps its application, identity provider, training library and backend. The SDK is designed to supply the app-facing connection and supported glasses operations.
Place each responsibility
| Component | Owns |
|---|---|
| Armor glasses | Firmware behavior, physical controls, device state, model-specific capture/light and hardware indicators. |
| Device SDK inside the mobile app | Communication with the glasses, native methods/events, transfer and update execution as delivered. |
| Your mobile app | OS permissions, user consent, UI, job context, storage, durable sync records and calls to your backend. |
| Your backend | Business rules, enterprise identity, data access, work orders, AI endpoints, retention and integration with your existing stack. |
| Lucyd developer portal | Documentation, SDK release distribution and partner developer resources. |
| Lucyd enterprise management layer | Enterprise fleet governance and administration are a separate product scope. |
Design a complete workflow
- Select context. The user opens a training module or work order in your mobile app.
- Connect and verify. The app establishes a ready device session and validates model/firmware support.
- Perform the device action. Use an accepted SDK operation and follow its events until the final outcome.
- Save locally. Verify the file and persist its association with the job before attempting cloud sync.
- Sync to your system. Upload through your existing authenticated backend API and record its receipt.
- Complete device cleanup. For media deletion, explicitly confirm durable sync for the exact device files.
Separate identity and device access
Your existing user login authenticates the worker to your application and services. Bluetooth pairing establishes the local device connection. Future portal API credentials will authorize specific Lucyd platform services; a portal key alone does not enforce device permissions over BLE.
Keep service secrets on a backend. Lucyd will publish account and credential guidance before onboarding opens.
Prepare your pilot
Choose one measurable workflow and one target model first. Record the SDK/hardware/firmware combination, the mobile OS matrix, permissions, storage/sync policy and interrupted-operation behavior. Define what the app should do when the glasses are unavailable, a feature is unsupported, or a user declines a network prompt.
Review model capability targets and review published SDK availability before setting expectations.