getMigrationGuide
Map each Meta DAT symbol to its Extentos replacement, with what changes and a step-by-step cutover plan for full migration.
Instructions
The entry point for a developer who ALREADY built their app against raw Meta DAT (the Device Access Toolkit / Wearables SDK) and wants to move onto the Extentos SDK. Extentos's production transport calls the SAME DAT underneath, so migration is a call-site swap, not a rewrite. Returns a map KEYED BY THE DAT SYMBOL you already have (Wearables.createSession, photoDataPublisher, addStream, Display, raw CaptureError, …) → the Extentos primitive that replaces it (glasses.connection, glasses.camera.capturePhoto, glasses.camera.videoFrames, glasses.display.show, ExtentosResult, …), plus a one-line 'what changes' per area and an ordered cutover plan. It re-embeds NO code — each mapping names the Extentos feature, so you drill into getCapabilityGuide(feature) for the Kotlin/Swift idiom and getCodeExample(pattern) for a full composition. The plan orchestrates the tools that already exist: generateConnectionModule (replaces Wearables.initialize/configure + your registration UI) → getPermissions (replaces hand-mapped manifest/plist + Meta scopes) → per-call-site swaps → validateIntegration → createSimulatorSession. Scope: FULL CUTOVER, not coexistence — running raw DAT and Extentos side-by-side in one process is not supported today (the DeviceSession is a single-owner handle), and the response says so. USE when a project already imports com.meta.wearable.dat.* (Android) / MWDATCore/MWDATCamera (iOS) and you're adopting Extentos. DON'T USE for a greenfield project with no existing DAT code (start at getPlatformInfo → generateConnectionModule).
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| from | No | Which SDK the app is migrating FROM. Optional — defaults to `meta_dat` (the only wrapper we map from today; the enum is forward-compatible for other vendors/wrappers as they land). |