Phone companion for the CMF Watch Pro 2 and the FMC watch face store. MIT.
ios/: Swift/SwiftUI app (tools.fmc.companion).android/: Kotlin/Compose app (tools.fmc.companion), same scope as iOS.
Both apps check their watch protocol against the same test vectors (ios/WireKit/Tests/WireKitTests/vectors.json,
from the Python host of cmf-watch-sdk). A change to a vector is a change for both apps.
cd ios
swift test --package-path WireKit # transport: frames, K session, install, App Loader INFO
xcodebuild -project FMCCompanion.xcodeproj -scheme FMCCompanion \
-destination 'platform=iOS Simulator,name=iPhone 17e' buildproject.yml generates the project (xcodegen generate); the generated FMCCompanion.xcodeproj is committed.
The watch connection uses the link Nothing X already holds and the channel key K (cmf-watch-sdk docs/abi-1.4.md, "Writing a host"): no pairing popup, Nothing X keeps working. The app only reads the watch for now.
cd android
./gradlew testDebugUnitTest # transport: frames, K session, install, App Loader INFO, watchface upload, links, miniapp RPC
./gradlew assembleDebugJDK 17 and the Android SDK (ANDROID_HOME). The transport is a port of WireKit in
app/src/main/java/tools/fmc/companion/wire; its tests read vectors.json and watchface-vectors.json from
ios/WireKit/Tests/WireKitTests in place, so both apps always run the same vectors.
Android 12+. Debug builds take adb shell am start -n tools.fmc.companion/.MainActivity --ei tab 1 --ez check true.
The watch connection is a second GATT client on the link Nothing X holds; on Android this is not yet tried on a real
watch. Watch faces need Nothing X closed first, as on iOS.