What is the reality of writing an app in HaxeUI and delivering for both web and desktop?

I’m investigating the age-old question of what tech to use to develop a UI app without being limited to a single destination platform. In particular, I care about being able to deploy something to the web and for desktop, and I’m wondering about the realities of doing this in HaxeUI.

I like the look of the language, and so in that sense, I’d much prefer Haxe to something like flutter. But I’m well aware that delivering to both web and desktop tends to be full of gotchas, even with a tech that can compile to both.

So, I’m looking for some realistic descriptions of what it’s like to develop in Haxe for multiple, and highly different, UI platforms.

Hi, sorry, I thought i replied to this :slight_smile:

So, if you are targeting native (haxeui-hxwidgets) and web (say haxeui-html5) then there are certainly limitations, mainly on the native side. You cant be so “creative” with native toolkits since the OS simply wont allow certain levels of customization. Obviously on the web (or actually any of the composite haxeui backends) you can customize till your heart is content. Another option for targeting desktop would be to use haxeui-html5 and electron (if you dont mind the weight). I use haxeui for a number of production apps, but obviously, im the author so im biased :slight_smile:

Im not really sure if that helps… … …


(sorry for the super late reply!)