3 ms·

I didn't know the state of Qt on mobile was so abysmal. Good to know.

• pjmlp 3y ago
  All frameworks beside the native ones on mobile are abysmal, people delude themselves thinking that they don't need to master the underlying stack as well. On the Android side it is even more difficult, because the NDK as matter of principle only exposes APIs for games and implementing native methods, so anything else has to be full of JNI calls into Java, even if those Java classes are mostly composed by native methods.
  • ngrilly 3y ago
    Are you saying that all the non-native mobile frameworks are abysmal because they have to map to JNI calls on Android and Objective-C/Swift on iOS?
    • pjmlp 3y ago
      They are abysmal, because they are leaky, yes. The dream of one code base to rule them all, can easily turn into a nightmare when going outside the golden path. And really, a large majority of apps are doing basic CRUD stuff, easily doable as mobile Web.
      • ngrilly 3y ago
        Agreed. Yet, I think the one code base approach gives better results on desktop (Windows/macOS/Linux) than mobile. VS Code for example is quite nice. Do you think this is because there are more OS and UI differences between Android and iOS than between Windows/macOS/Linux? Desktop is more "standardized"?
        • pjmlp 3y ago
          Desktop is also as different, most people sidestep it by only caring about POSIX, or shipping a Web browser with the application.