3 ms·
Desktop crossplatform development is a weird beast. Yeah you get to share a lot of code between platforms and it's easy to get 80% there, but getting a polished
by pier25 8y ago
Desktop crossplatform development is a weird beast. Yeah you get to share a lot of code between platforms and it's easy to get 80% there, but getting a polished UI is a lot of work.
In some cases such as using JUCE for making audio plugins it's even desired to not have a native UI since users expect each plugin to have its own UI. But unless you are huge, like say Adobe, having a nice and polished cross platform UI for application development is simply not feasible.
After years I've come to the conclusion that the proper way of supporting multiple platforms is having native UIs and sharing application logic in any way you can between platforms. I think that's the idea behind Xamarin.
- inspector-g 8y agoEven Adobe has bungled its cross-platform UI support/tooling a number of times. I think the reduced scope definitely helps though, but even in that scenario some problems seem to unavoidably surface. Source: have written plugins for Adobe products for many years.
- pier25 8y agoWhat do you mean by "reduced scope"?
- tomcam 8y agoActually JUCE has deep coverage of highly portable UI concepts as well. I think it compares favorably with QT.
- c-smile 8y agoI like JUCE architecture as probably more than other library. I actually even considered JUCE as a backend for my Sciter: https://sciter.com/sciter-on-mac-with-juce-backend/ https://sciter.com/sciter-on-mac-with-juce-backend/ But the problem is that JUCE uses pure software rasterizer. That unfortunately does not work for high-DPI monitors. GPU acceleration is required for almost all modern UI applications.