跪拜 Guibai
← All articles
Frontend · Android · iOS

iOS for Web: Run and Edit Native UIKit Apps in the Browser, Simulator Optional

By 恋猫de小郭 ·
Read original on juejin.cn ↗ Google Translate ↗ Alt translation

Running native iOS UIs in the browser without a device cuts the UI iteration feedback loop from minutes to under a second, and lets AI agents modify real UIKit code directly. It also signals that the simulator may not remain the only preview surface for mobile development.

Summary

Dessn's iOS for Web claims to turn native Swift and Objective-C projects into browser-rendered, interactive UIs. It operates as a code-based Figma: load a real Xcode project, and the UI appears in the browser with working navigation, gestures, and constraint layout. Developers can duplicate the same project into multiple independent design versions, tweak each one, and see results in under a second, without going through the full IPA build, link, and install cycle.

The implementation is closed-source, but Dessn says it relies on a Rust compiler and renderer. The author speculates the actual pipeline uses WebAssembly plus an intermediate representation, possibly with a custom canvas backed by WebGPU. The core problem is mapping UIKit semantics to the browser: event delivery, state storage, and routing have to be reimplemented for every UIViewController interaction.

Because the tool syncs UI changes back to source code, a coding agent can edit the real project in the browser and have those edits land directly in the codebase. This inverts the usual Figma-first flow, where design is translated into code later.

Takeaways
— Dessn has not open-sourced the project; it only describes a Rust compiler and renderer.
— The tool accepts Swift and Objective-C projects and renders them in the browser without an iPhone or simulator.
— Multiple independent design versions can be created from a single project in a canvas.
— UI modifications sync back to the source code, and most changes take under a second without a full IPA build.
— A page interaction requires mapping events, state, and UIKit routing to the browser.
— The likely implementation uses WebAssembly, an intermediate representation, and possibly WebGPU for a custom canvas.
— The demo shows basic interaction, but third-party UI components and complex view controller navigation remain a challenge.
Conclusions

Treating source code as the single source of truth in a design canvas inverts the Figma-to-code workflow, which could shift how AI coding agents prototype user interfaces.

Closed source leaves the runtime mapping unverified, so the demo's breadth is hard to confirm beyond the shown interactions.

Rewriting UIKit semantics for the browser is the hard part; simple buttons are easy, but real apps rely on gesture recognizers, constraint layouts, and third-party components that demand a full runtime.

Concepts & terms
Objective-C Runtime
The dynamic runtime that underpins Objective-C and UIKit on Apple platforms; it handles method dispatch, key-value coding, and object introspection. Dessn needs to emulate this behavior in the browser to execute UIKit code.
WebAssembly (Wasm)
A binary instruction format that runs in browsers at near-native speed. Swift can officially compile to Wasm, but Apple frameworks like UIKit still require the Objective-C runtime, so a parser is needed.
WebGPU
A modern browser graphics API. The author suspects Dessn uses Rust with WebGPU to build a custom canvas that renders the iOS UI instead of relying on DOM-based rendering.
From the discussion

Awe at AI's capability collides with skepticism about the closed-source approach. AI and WASM are credited as the enablers, yet the lack of open source is seen as a limit on reach. A question about Swift cross-platform acceleration also surfaces.

— Closed source caps the project's reach; adoption will founder without open licensing.
— AI has made development barriers nearly vanish, enabling such tools.
— WASM is the technical core that makes the browser-based UI possible.
— Swift cross-platform development might get faster as a result.
Featured comments
爱梦梦真是太好了

AI is now so incredibly powerful that the barrier to programming languages has almost disappeared.

zhao1zhihui

Without open source, it's destined not to go far.

zhao1zhihui

So will Swift cross-platform development eventually become faster?

See top comments, translated →
Source: juejin.cn ↗ Google Translate ↗ Backup ↗