Comment by skurilyak

For iOS compatibility, consider this architecture:

- Swift UI layer for Apple-compliant UI/UX

- Zig core library (as XCFramework) for watch communication

- Data processing WebAssembly runtime for watchface interpretation

This avoids Pebble's original JS compiler workaround while still enabling customizable watchfaces within Apple's restrictions

The WASM engine stays within App Store guidelines by interpreting watchfaces as data rather than executable code

TL;DR to avoid this:

iOS App (Swift UI) <-> Zig Core Library (XCFramework) <-> WebAssembly Runtime (for watchfaces)