Camera software · reviewed 12 October 2026
Review actual supplied app screens alongside reference SDK packages, Demo projects and firmware architecture. Start with the M-20 camera-reference platform, then match the software to your intended hardware and workflow.
For our standard companion-app offer, there is no app subscription fee for the first year.
The quotation should confirm when the free period starts, which services and usage allowances are included, supported regions and renewal pricing. First-year subscription inclusion does not mean lifetime-free service, unlimited AI usage or free custom app/firmware development. Third-party services and commissioned engineering are scoped separately.
These are screenshots supplied for our camera-glasses software review. They show the interface, not a connected-device acceptance test or a verified feature on every catalog model.
Photo, Video, Record and Gallery controls, plus AI Memory, translation and Live View entries. The shown device is disconnected; disabled controls are not proof of a working stream.
The supplied screen shows an English conversation setting and a glasses-assisted AI interaction entry. The selected service, region, permissions and firmware determine the working experience.
The supplied screen shows translation controls and a language picker. A visible language option does not establish translation quality, PT-BR support or offline operation.
We have reviewed Android 2.0.0 and iOS 1.2.0 reference SDK packages, Demo projects and documentation for the M-20 camera-reference platform. The table identifies actual interface evidence and separates it from hardware acceptance testing.
| Function or deliverable | Current public status | Evaluation evidence |
|---|---|---|
| Photo and recorded-video capture | Documented hardware function | Scout One supplied capture samples and model specifications; API exposure is a separate check. |
| Android and iOS reference SDKs | Packages and Demo projects reviewed | Android 2.0.0 reference with AAR/Demo/docs; iOS 1.2.0 reference with framework/Swift Demo/guide. M-20 camera-reference scope; match the actual model and firmware. |
| App pairing, capture commands and file transfer | Documented interfaces in reviewed packages | Scanning/connection, photo control, video configuration, media status and Wi-Fi file transfer. Static interface review is separate from successful sample testing. |
| Branded companion app | Scoped customization service | Agree UI/branding, functional development, account setup, app-store responsibilities and maintenance. No blanket ready-to-rebrand app is claimed. |
| Firmware behavior | Scoped development service | Agree supported changes and acceptance tests. Firmware source-code delivery is not included by default. |
| Own AI backend | Project feasibility review | Define permitted image/audio input, service endpoint, response and data handling; validate the full path. |
| Live-mode control | Documented SDK integration path | Wi-Fi live-mode entry/status/exit are documented; Android guide describes an RTSP URL path and iOS exposes live/STA controls. Validate API/library alignment, transport, audio, runtime and receiving app. |
| AI and translation audio | Documented session and audio callbacks | Audio data, AI-session status and image callbacks exist in the references. This does not establish unrestricted always-on raw microphone or arbitrary sensor access. |
| OTA | Documented host/media update paths | References include BLE host updates and Wi-Fi media-processor updates. Match firmware files and device versions; agree signing, recovery and update ownership. |
| Software maintenance | Commercial scope to agree | Version support, app-store ownership, source rights and ongoing support are agreed separately. Reference packages are not a blanket warranty of every phone/model. |
Reviewed 12 October 2026. Request the applicable reference package and access terms for your project; packages and firmware binaries are not public downloads. Interface presence is documented, but phone compatibility, feature parity and performance require a matched sample. This evidence is not automatically extended to other Scout, Cue or Verse hardware. Camera and audio SDKs are separate.
See companion-app screens and firmware architecture →The supplied architecture describes a two-processor camera platform: a host controller for Bluetooth/audio and a media processor for imaging, storage and Wi-Fi. It is a reference architecture, not the Qualcomm/BES Cue Pro architecture.
Step 1
The SDK handles commands, connection/status, agreed audio or image callbacks, and the companion-app workflow.
Step 2
The controller runs an RTOS, Bluetooth and audio orchestration, including wake, calls, prompts and mode conflict handling.
Step 3
The host sends control over an internal link. The media processor manages camera capture, processing, file storage and Wi-Fi services.
Step 4
Larger media files use the Wi-Fi transfer path; supported AI image/audio callbacks use the agreed session path. The phone/service layer supplies AI processing and responses.
Firmware arbitrates calls, AI dialogue, music, recording, transfer and updates. These modes are not assumed to operate simultaneously. Audio callback formats can differ by SDK path and decoding layer; do not assume an unrestricted raw PCM microphone API or continuous simultaneous video/audio/AI operation.
Reference packages document a Bluetooth host update path and a Wi-Fi media-processor update path, with status/progress handling. An app Firmware screen is interface evidence; the actual update, package match, recovery and ownership need device-level validation.
The Android reference describes a Wi-Fi live-mode and RTSP URL pathway; the iOS framework provides live-mode and STA-state controls. These are static integration evidence, not a tested frame-rate, latency, internet broadcasting or multi-client guarantee. Match the actual API package, firmware and receiver before committing to a live workflow.
The reviewed Android reference contains AAR libraries, a Demo project and guides for scanning, connection, camera, media, audio and OTA. Its Demo config uses minimum API 21 and target/compile API 34; that build configuration is not a promise of validated compatibility with every Android phone. The iOS reference contains a framework, Swift Demo and development guide. Minimum phone OS, license/access terms and supported hardware are confirmed with the matched package.
For acceptance, pair the supplied unit, issue a photo command, review recording behavior, transfer an original file, exercise required audio callbacks and validate the update path. Record hardware, firmware, app and SDK versions. AR-related interfaces appearing in a library do not add display hardware to camera-only glasses.
Tell us your model, phone systems, media/AI workflow and essential interfaces. We will review the applicable reference software and scope your development.