# Glass app-level capture flow

## Purpose

Demonstrate a **business-owned** Activity that wraps `QuickCameraManager` for photo/video without forcing users through the SDK-heavy sample page.

## Entry points

Glass home:

- `HomeActivity` → `CameraPageActivity`

Sample Activity:

- `com.rokid.glass.CameraPageActivity`

## Platform

- Glass

## Main files

- [CameraPageActivity.kt](https://gitee.com/as_pixar/glass3sdkdemo/blob/main/glassdemo/app/src/main/java/com/rokid/glass/CameraPageActivity.kt)
- [QuickCameraManager.kt](https://gitee.com/as_pixar/glass3sdkdemo/blob/main/glassdemo/app/src/main/java/com/rokid/glass/camera/QuickCameraManager.kt)

## Flow

1. Initialize `QuickCameraManager` immediately after inflate.  
2. Touchpad gestures flip between shutter vs record modes.  
3. Snapshot path invokes `takePicture()` and enqueues artefacts for handset sync.  
4. Record path runs bespoke state machine + timers.

## FAQ

### Vs `SdkMediaActivity`

`sdk`-prefixed Activity highlights SDK API usage; **this** Activity focuses on custom transitions, choreography, HUD chrome.

### Prefer this when...

You intend to polish **wearable-ready** UX instead of validating raw SDK knobs.

## Caveats

- Busy / init-failure gates protect against half-open camera sessions.  
- Touchpad reliance means map hardware events carefully on alternative SKUs.  
- Successful snaps queue for transport—not only sandbox storage.
