[mft_]

This is always the piece that disappoints me when seeing this and other similar tools.

Surely it is an obvious next step to offer export to e.g. React, React Native, SwiftUI…?

Otherwise you spend days, weeks, months crafting your perfect design down to the pixel, and then someone else has to start again from scratch with a totally different approach. Maybe I’m missing something, but that feels incredibly inefficient and regressive.

[gyomu]

> your perfect design down to the pixel

> Surely it is an obvious next step to offer export to e.g. React, React Native, SwiftUI…?

These UI frameworks do not really operate in a "down to the pixel" way and so getting correspondance between a bitmap design and a representation in the UI framework is far from an "obvious next step" (if it were trivial to add such a feature, then of course the developers of these tools would add it).

Various concerns that aren't captured in the bitmap design - like how your screens transition from one to another, etc - can dramatically affect how the UI is implemented in a target framework. This is the job of UI engineers.

Well, used to be. Now it's vibe code all the way down.

[mft_]

Sure, I understand the going from a raster design image to a working prototype in one of the frameworks is not easily automated.

However, I would’ve thought it would be feasible to create a design tool with this in mind, so the same fundamental design structure could be output either to the internal preview, or (any?) one of the target frameworks.

[lylejantzi3rd]

Wouldn't that be more of a RAD tool, like Lazarus[0]? Or are you suggesting you could do both in the same tool? I'm not doubting it's possible, but those are two very different (and large!) products from a functional standpoint. Combining them is going to be quite the undertaking.

[0]: https://www.lazarus-ide.org/