Spec iOS client: SwiftUI app on a documented API

Spec work, not commissioned. A native SwiftUI iPhone client written against a messaging platform's published Web API, built only from that API's documentation and the lines of a listing. No account of the platform's is behind it: a small local server implements the same routes and JSON shapes, so the same client code applies when pointed at the production API with a real key.

Live demo: https://demos.mc.mightyhouseinc.com/fmsg-ios/

What it shows

A 60-second recording that is an automated UI test on the iPhone 17 Pro simulator (iOS 26.5), not a mock-up: inbox with unread state, a thread with an attachment, a reaction from the native long-press menu, a draft-then-send reply, a reply from another participant arriving live over the WebSocket, and four themes.

Token handling: the API key is sent once, the 12-hour access token is cached, renewed before expiry, and renewed once on a 401.

Inbox and sent merged into conversations by following each message to its root; reaction messages kept out of the lists; threads marked read when opened.

New messages and replies addressed to everyone on the message except the sender, with address validation.

A live connection handling new-message, reaction, delivered and participant-added events, backing off and re-listing the inbox after a drop.

Five unit tests that decode the JSON examples copied from the platform's own reference, plus the passing UI test that produced the recording.

The full source, as an XcodeGen project with the app, the tests and the local server.

Every address in it is an example.com placeholder.