Can I use it? — Apple platform compatibility reference for RealityKit, ARKit, Metal, and hardware-gated features across iOS, visionOS, and macOS.

→ uncannyuse.com

A caniuse.com-style compatibility matrix for Apple developer APIs, verified directly from Xcode SDK .swiftinterface files — not documentation.

Currently covers 62 public RealityKit Component types from Xcode 26.3 with:

• iOS / visionOS / macOS version support (minimum SDK version)
• Reality Composer Pro Add Component menu coverage (28/62)
• Platform-exclusive flags (5 visionOS-only, 1 iOS-only)
• New in 26.0 callouts (7 components)

Also includes:

• RCP development notes — PR-driven documentation of Reality Composer Pro authored behavior (USDA schema internals, field matrices). Browse at /research on the site.
• Static schema API — Build-time JSON/CSV exports for all documented RCP components. Aggregate exports live at /data/schemas/; per-component artifacts live at /api/components/<slug>/.

All data is extracted from RealityFoundation.swiftinterface files in the Xcode 26.3 SDK and from binary string analysis of RealityToolsFoundation.framework. macOS versions are inferred from SDK era — verify against Apple documentation.

• Astro 5 — static site generation
• Tailwind v4 — via @tailwindcss/vite
• SF Mono — system font, zero network requests
• Dark mode default + prefers-color-scheme light mode

uncannyuse ships a build-time static data layer. There is no runtime backend today.

Aggregate exports:

• /data/schemas/index.json
• /data/schemas/fields.csv
• /data/schemas/matrix.csv

Per-component exports:

• /api/index.json
• /api/components/index.json
• /api/components/<slug>/schema.json
• /api/components/<slug>/fields.csv
• /api/components/<slug>/matrix.csv
• /api/components/<slug>/fixtures.csv

fixtures.csv is the rawest useful export for large components such as particle-emitter-component: one row per authored USDA field observed in a fixture file, including fixture path, UI section, struct scope, and authored value.

• ARKit — session configs, anchor types, hardware tiers (LiDAR, chip generation)
• Metal — GPU feature sets, ray tracing, mesh shaders per Apple GPU family
• Hardware tier dimension (A-series chip, LiDAR, camera)
• Compare view
• Stabilize and version the static schema API shape (see #12)
• Interactive schema lookup page

npm install
npm run dev           # localhost:4321
npm run build         # Build site
npm run build:all     # Regenerate schema/API artifacts, then build site
npm run generate:schemas  # Regenerate fixture schemas from Deconstructed fixtures
npm run generate:csv      # Generate aggregate + per-component JSON/CSV exports
npm run preview

Use Markdown note entries under src/content/rcp-claims/ with strict frontmatter validation.

See docs/rcp-research-notes.md.

If this saves you time, buy me a coffee ☕