DescriptionThe QVAC SDK (@qvac/sdk) currently exposes a single JavaScript client that supports Node.js, Bare, and Expo (Hermes) through runtime-specific IPC bridges selected via dynamic imports. The client communicates with a Bare worker process over an RPC protocol — the SDK spawns the Bare worker, establishes the RPC server, and the client connects as a consumer.
There is no native Swift client. iOS and macOS applications that want to use QVAC must go through the Expo/React Native bridge, adding an entire JavaScript layer and its associated overhead. A native Swift client that speaks directly to the Bare worker over IPC would allow Swift applications to use QVAC with native type safety, lower latency, and no JavaScript runtime dependency at the call site.
This grant funds the implementation of a Swift client for the QVAC SDK. The client is not a rewrite of the SDK — the Bare worker remains responsible for spawning, model management, and addon orchestration. The Swift client implements only the RPC consumer side: IPC connectivity to the Bare worker and a type-safe Swift API surface that mirrors the existing JavaScript client.
There is no native Swift client. iOS and macOS applications that want to use QVAC must go through the Expo/React Native bridge, adding an entire JavaScript layer and its associated overhead. A native Swift client that speaks directly to the Bare worker over IPC would allow Swift applications to use QVAC with native type safety, lower latency, and no JavaScript runtime dependency at the call site.
This grant funds the implementation of a Swift client for the QVAC SDK. The client is not a rewrite of the SDK — the Bare worker remains responsible for spawning, model management, and addon orchestration. The Swift client implements only the RPC consumer side: IPC connectivity to the Bare worker and a type-safe Swift API surface that mirrors the existing JavaScript client.