Use AvatarKit clients to render messages produced by your Backend Mode.
The Client SDK side of Backend Mode Integration renders encoded audio payloads and motion data payloads from your backend. The client does not connect directly to Motion Server. Instead, it receives those payloads over your chosen transport and feeds them into AvatarKit.
Configure the client with App ID, avatar, region, and the Backend Mode client setting for your SDK.
Connect to your backend
Join your WebSocket, RTC room, or other downstream transport.
Consume encoded payloads
Receive encoded audio payloads and motion data payloads provided by the Server SDK.
Render locally
Feed messages into AvatarKit with yieldAudioData() and yieldFramesData().
Do not call start() and send() for the Backend Mode client path. Those are Direct Mode methods. Backend Mode clients receive messages from your backend and call the yield* methods.
