Here's a trick I've been experimenting with lately - try making a GUI in some high level and English-like but formal language. FXML works well (the description language of JavaFX) probably because it's relatively noise-free, but XAML would probably also work.
Then ask GPT-4 to convert it to SwiftUI. It actually does it. Or try Jetpack Compose: same thing.
This leads to an obvious thought - part of why people use heavy abstractions is because the cost of native development is too high. You could pay development teams to write a WPF UI, a Cocoa UI, a GTK UI, an Android UI and a UIKit UI for your app but even VC funded firms flush with cash can't justify that level of extravagance. It's too hard and expensive to hire devs, so when you do, the opportunity cost of them porting stuff between endless UI native APIs just can't make sense. AI changes that equation completely. GPT-4 is cheap for what it does. Suddenly, auto-porting your app into 5 different native APIs simultaneously and then assigning the resulting bugs to a bug-fixing bot doesn't seem unimaginable.
Now, for better or worse, even if AI reaches the point where it can do that, it doesn't mean Teams won't be slow. People use Electron for a lot of reasons, not just cost of duplicated development (skills, libraries, Windows lacking a competitive and non-deprecated UI toolkit etc). But it's interesting to think about ideas that we instinctively write off today due to the massive cost of software developer time.
Then ask GPT-4 to convert it to SwiftUI. It actually does it. Or try Jetpack Compose: same thing.
This leads to an obvious thought - part of why people use heavy abstractions is because the cost of native development is too high. You could pay development teams to write a WPF UI, a Cocoa UI, a GTK UI, an Android UI and a UIKit UI for your app but even VC funded firms flush with cash can't justify that level of extravagance. It's too hard and expensive to hire devs, so when you do, the opportunity cost of them porting stuff between endless UI native APIs just can't make sense. AI changes that equation completely. GPT-4 is cheap for what it does. Suddenly, auto-porting your app into 5 different native APIs simultaneously and then assigning the resulting bugs to a bug-fixing bot doesn't seem unimaginable.
Now, for better or worse, even if AI reaches the point where it can do that, it doesn't mean Teams won't be slow. People use Electron for a lot of reasons, not just cost of duplicated development (skills, libraries, Windows lacking a competitive and non-deprecated UI toolkit etc). But it's interesting to think about ideas that we instinctively write off today due to the massive cost of software developer time.