this post was submitted on 26 Dec 2023
127 points (96.4% liked)

Programming

17316 readers
61 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities [email protected]



founded 1 year ago
MODERATORS
 

it seems ridiculous that we have to embed an entire browser, meant for internet web browsing, just to create a cross-platform UI with moderate ease.

Why are native or semi-native UI frameworks lagging so far behind? am I wrong in thinking this? are there easier, declarative frameworks for creating semi-native UIs on desktop that don't look like windows 1998?

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 52 points 10 months ago* (last edited 10 months ago) (2 children)

Ha! I'm partially looking at this issue in my bachelor's thesis.

It's not at all necessary to embed a browser, but it's really easy to transfer your web app to a "near native" experience with stuff like electron, ionic, cordova, react native or whatever other web stuff is out there. The issue is mostly that native APIs are complicated and relying on web views or just providing your own "browser" is a relatively easy approach.

Stuff like Flutter, Xamarin or .NET MAUI compile depending on the platform to native or are interpreted by a runtime. There's a study I use that compares Flutter to React Native, native Java and Ionic on Android and finds that unsurprisingly the native implementation is best, but is closely followed by Flutter (with a few hiccups), with the remainder being significantly slower.

The thing is. I don't think these compiled frameworks lag behind in any way. But when you have a dev team, that's competent in web development, you won't make them learn C#, Xaml, Dart or C++, just to get native API access - you'll just let a framework handle that for you because it's cheaper and easier.

Edit: To add some further reading. This paper and this one explore the different approaches out there and suggest which one might be "the best". I don't feel like they're good papers, but there's almost no other write up of cross-platform dev approaches out there.

Edit2: I also believe that the approach "we are web devs that want access to native APIs" may be turned around in the future, since Flutter and now also .NET offer ways to deploy cross-platforn apps as web apps. I'll get back to writing the thesis now and stop editing.

[–] [email protected] 4 points 10 months ago

You may also want to checkout xilem

[–] [email protected] 4 points 10 months ago (1 children)

I remember thinking that Qt seemed like a really good approach that should be more widely adopted...until I actually had to use it.

Not that it's terrible; it's really not. But C++ is just not at all a good language for anything UI stuff.

[–] [email protected] 4 points 10 months ago

QML on the other hand is awesome imo.