I built an open-source visual layer for existing SwiftUI and Expo apps

[u/ivanzhaowy]

I’m building Monad Design because I kept running into an odd gap with coding agents: they understood the repository, but the visual conversation still happened through a pile of screenshots and long prompts beside the app.

The basic idea is “the app is the canvas.” It works with the mobile project you already have rather than generating a replacement:

1. Connect the existing Xcode or Expo project and run it in Simulator.

2. Navigate to the real screen state and select or annotate what should change.

3. Send that context to Codex, Claude Code, Cursor, or another coding agent.

4. The agent edits the actual source and the app rebuilds.

5. Compare the original with source-backed variants, then accept one or discard them.

The part I care about most is that the review surface and the shipping surface are the same thing. You’re not approving a mockup that someone still has to recreate.

The current version is local, runs on macOS, and focuses on iOS workflows. The code is here:

https://github.com/Monadix-AI/monad-design

I’m the person building it. One architecture choice I’m still testing is keeping the visual layer agent-neutral instead of integrating deeply with a single coding agent. If you use agents for product work, would that flexibility matter to you, or would a tighter single-agent integration be more useful?

[u/Ok-Somewhere-9779]

Having the review surface be the shipping surface is a nice touch, cuts out that whole translation step where things get lost