Open sourcing our Swift bindings generator for WinRT - and an end-to-end sample application for anyone looking to build a modern Windows application in Swift.
1. How to accomplish SwiftUI like declarative programming here? I guess that you use TCA for whole architecture, but for View- Model biding, I wonder how to handle this.
2. Dd you simplify the API for real use? I mean that sample code seems to be a little verbose, because it uses th C++/WinRT as it is.
3. Is there any issue for real use? I found the repository that shows similiar approach in c++ - "WinUI 3 in C++ Without XAML".
This is not about porting SwiftUI or other designs from the Apple world to Windows, this is about making the native Windows APIs available to Swift. Yes, Windows platform APIs look very different from Apple's platform APIs - because they are different platforms with different historic backgrounds.
As helpful as this is, I'm not optimistic about this solution ever replacing frameworks like Electron because it still requires you to implement two completely separate UIs and corporations clearly have no qualms about saving money at the expense of high-quality UX.
I think this effort only caters to people who have already decided they _want_ to build a native Windows app, because any cross-platform solution like Electron wouldn't let them get the fastest launch times, best memory-efficiency, best overall performance, or maximum use of platform APIs.
This is amazing 👏🏻 Native WinUI apps with Swift - finally a viable path to porting my Swift Mac app to Windows.
I have a few questions about implementation.
1. How to accomplish SwiftUI like declarative programming here? I guess that you use TCA for whole architecture, but for View- Model biding, I wonder how to handle this.
2. Dd you simplify the API for real use? I mean that sample code seems to be a little verbose, because it uses th C++/WinRT as it is.
3. Is there any issue for real use? I found the repository that shows similiar approach in c++ - "WinUI 3 in C++ Without XAML".
https://github.com/sotanakamura/winui3-without-xaml
4. Do you have any plan to provide SwiftUI-ish implementation?
This is not about porting SwiftUI or other designs from the Apple world to Windows, this is about making the native Windows APIs available to Swift. Yes, Windows platform APIs look very different from Apple's platform APIs - because they are different platforms with different historic backgrounds.
As helpful as this is, I'm not optimistic about this solution ever replacing frameworks like Electron because it still requires you to implement two completely separate UIs and corporations clearly have no qualms about saving money at the expense of high-quality UX.
I think this effort only caters to people who have already decided they _want_ to build a native Windows app, because any cross-platform solution like Electron wouldn't let them get the fastest launch times, best memory-efficiency, best overall performance, or maximum use of platform APIs.