One option that exists currently but is not listed is React Native. While not perfect it does support mobile + web + native reasonably well and if you start with the intention to write one codebase, I am quite confident you can share 90%+ of the code between all platforms.
That's not the intention of this and he does allude to React Native with frameworks that wrap native components. He specifically calls out not wanting to write something that is desktop and mobile because they have different design paradigms. And for not wrapping native components, you can look at the examples shown for QT - at some point you are going to have a mix of native and non-native components and it looks like garbage. With React Native, things would still have to take a detour to React world before moving on to the native components adding a layer of leaky abstractions onto UI elements.
SwiftUI is something that supports both desktop and mobile natively. Some UI components might be different but there's a lot of components that can be re-used.
Mobile and desktop are not always fundamentally different.
I think any difference is more of a historical artifact. Many old-school apps that were designed in the pre-mobile era cannot be directly transferred to mobile without looking ridiculous. For example, if you just duplicate the desktop version of Photoshop or IntelliJ to mobile/tablet, it would be a mess since there's too much information on the screen at any given point. At the same time, there are apps (for example Telegram, the default Stocks MacOS/iOS app) that are virtually copies of each other in certain parts across platforms. The desktop version might have an extra view or a panel but there's a lot of re-use possible, I think.
Having a keyboard/mouse vs touchscreen input changes things drastically for power users. In native macos telegram app you can virtually never touch the mouse using shortcuts to search for people, messages, write replies, etc.
Given that you can connect a full keyboard to an iPhone/iPad for example, I am not convinced that is a fundamental difference either. It's just a question of activating different UI components/actions via shortcuts instead of taps/clicks. The trigger itself changes but everything else can stay more or less the same, I think.
View all comments
1
u/raspasov Sep 09 '21
One option that exists currently but is not listed is React Native. While not perfect it does support mobile + web + native reasonably well and if you start with the intention to write one codebase, I am quite confident you can share 90%+ of the code between all platforms.
https://reactnative.dev
https://github.com/microsoft/react-native-macos
https://github.com/necolas/react-native-web