ARKit visionOS Developer

Quick Start

1. Identify the provider set first: world tracking, hand tracking, plane detection, scene reconstruction, or another specialized provider.
2. Add only the usage strings required by the providers you actually use.
3. Create a long-lived ARKitSession and request authorization before running it.
4. Load the shared session, anchor, or bridge references first, then load only the provider files you actually need.
5. Keep anchor state in a model layer, and bridge into RealityKit only when you have a rendering target.
6. If the issue is app launch, test flow, simulator behavior, or signing, switch to build-run-debug or signing-entitlements.

Load References When

Workflow

1. Choose the provider set.
2. Load the shared session and lifecycle guidance first.
3. Add only the provider references that match the task.
4. Keep anchor reconciliation in a model layer.
5. Bridge into RealityKit only after the model layer has stable state.

Guardrails

• Keep a strong reference to ARKitSession for the full lifetime of the experience.
• Request authorization before running providers that need it.
• Do not block the main actor while awaiting provider updates.
• Do not assume every provider has the same presentation requirements.
• Route launch, build, simulator, and codesign problems out to the execution skills instead of expanding this skill with run-loop detail.

Output Expectations

Provide:

• the chosen provider set
• which shared and provider references were used
• the session and anchor-processing model
• the RealityKit bridge plan if applicable
• the next skill to use if the blocker is execution, signing, or scene work