iOS for Web: Run and Edit Native UIKit Apps in the Browser, Simulator Optional
iOS for Web: Running native iOS apps in the browser
Recently, iOS for the Web came out, which seems interesting. They run iOS apps in the browser, without needing to start an iPhone or iOS Simulator:
The interesting part is that it aims to be a code-based Figma, which can be run directly from Swift and Objective-C projects, then rendered and interacted with in the browser. You can also create multiple independent design versions from the same project, meaning you don't need an iPhone or simulator to preview and interact with iOS projects. For example, a Coding Agent can directly modify the UI around a real project without first drawing a Figma and then translating the design into code.
For example, a simplest UIKit code:
let button = UIButton(type: .system)
button.setTitle("Send", for: .normal)
button.addTarget(self, action: #selector(sendMessage), for: .touchUpInside)
On iOS, the creation, layout, and tap dispatch of UIButton rely on UIKit and the system runtime. Although Swift can compile to WebAssembly officially, Apple frameworks like UIKit still need the Objective-C Runtime, so a parser is needed to support it.
For example, for the button above to actually be clickable in the browser, the converted runtime must at least know:
This is a button, what text it displays, which callback its tap corresponds to, and how the UI should update after the callback changes state. More complex things like
UIViewControllernavigation, gestures, constraint layout, and third-party UI components all need corresponding support.
Dessn's project is not open source; it only says it built a Rust compiler and renderer. So we don't know how the intermediate representation and execution backend from Swift/Objective-C to the browser are implemented. Based on its demonstrated capabilities, I think completing a page interaction requires roughly the following layers working together:
For instance, when you click a chat record in the web, the browser needs to find the hit list item, let the corresponding callback change the navigation state, and finally redraw the chat page.
If Dessn retains this logic from the original project, it also has to solve how events are passed to Swift/Objective-C, where state is stored, how UIKit routing maps to the browser, and so on.
I think WASM and an intermediate representation are more likely; it might be a custom canvas using Rust with WebGPU.
A more concrete example: if you want to modify the iOS chat list, Dessn lets you directly copy three versions A, B, and C in the canvas. One adjusts message spacing, one modifies the input bar, one changes the navigation layout. After changes, you can interact and view each version directly in its own page:
This means AI can adjust UI in parallel lines, and "most modifications take less than a second" without going through the full IPA build, link, and install process. Changes can also sync back to the code, similar to accelerating multi-line AI development.
Indeed, with AI, human imagination becomes rich.
Top 5 of 6 from juejin.cn, machine-translated. The original thread is authoritative.
Telegram really shows sincerity, always finding ways to improve to attract more users.
The technical core is WASM.
AI is now so incredibly powerful that the barrier to programming languages has almost disappeared.
Without open source, it's destined not to go far.
So will Swift cross-platform development eventually become faster?
Before AI, I couldn't even dream of this. It's all thanks to the divine power of AI-sama.