Custom components support only 'simpler data' types — scalars, strings, SIMD values, and enums — with Xcode build-time errors for unsupported types.

Details

Source

WWDC 2023 session “Work with Reality Composer Pro content in Xcode” (wwdc2023-10273).

At 22:31:

“Design-time components are for housing simpler data, such as ints, strings, and SIMD values, things that 3D artists and designers will make use of.”

And:

“You’ll see an error in your Xcode project if you add a property to your custom component that’s of a type that Reality Composer Pro won’t serialize.”

Example from the Session

The session demonstrates a PointOfInterestComponent example:

public struct PointOfInterestComponent: Component, Codable {
    public var region: Region = .yosemite  // Custom enum (serializes as string/token)
    public var name: String = "Ribbon Beach"
    public var description: String?        // Optional String
}

Supported Type Categories

What to Avoid

The session’s “simpler data” constraint explicitly excludes:

Build-Time Validation

Unlike runtime errors, RCP provides compile-time feedback through Xcode:

RCP generates Swift code from the USD schema
        ↓
Xcode attempts to compile the generated code
        ↓
Build fails with clear error for unsupported types

This makes custom components self-documenting — the supported types are exactly those that survive the codegen → compile pipeline.

Inspector-Safe Type Palette

For custom component field editing in Deconstructed, use these verified types: