swift-win32 VS Vapor

For jumping abord, there are not very many frameworks for UI development. There is https://github.com/compnerd/swift-win32 which is less WinForms and more Common Control based. There were a couple of different attempts for WinRT to get XAML based UI systems. There was no official support for UWP, and that would likely require some tweaks to the runtime.

Even Microsoft has someone dedicating their time to building Win32 support.

Swift does run on windows now. There’s also a package that lets you use Win32 to write GUI apps (https://github.com/compnerd/swift-win32). The core code (data models, networking, etc) can be common, but UI will have to be different (Win32 on windows and AppKit/Catalyst/SwiftUI on Mac)

As others have mentioned, UIKit is an Apple framework and not available on Windows, though you should be able to use the Win32 APIs to build out UI interfaces. Alternatively, you can experiment with https://github.com/compnerd/swift-win32 for a nice layer on top which abstracts out some of the details of the Win32 API. Unfortunately, that is not as fleshed out as one would like to build complex applications, but that is something which more usage and work on library should be able to resolve.

For native apps, there's this, which gives an AppKit-like interface to build GUIs.

If you’re looking for Windows first projects with Swift, https://github.com/compnerd/swift-win32 is pretty cool.

Also check out this project by a member of the Swift core team, which is a set of bindings for the Win32 API for Swift on Windows.

Botter works in tandem with Vapor, which handles the server-side functions of your project. This powerful combination allows you to focus on what matters most - creating an engaging and effective chatbot.

// swift-tools-version: 5.8 // The swift-tools-version declares the minimum version of Swift required to build this package. import PackageDescription let package = Package( name: "MyServer", platforms: [.macOS("12.0")], products: [ // Products define the executables and libraries a package produces, and make them visible to other packages. .executable( name: "MyServer", targets: ["MyServer"]), ], dependencies: [ .package(url: "https://github.com/vapor/vapor.git", .upToNextMajor(from: "4.70.0")), // Dependencies declare other packages that this package depends on. // .package(url: /* package url */, from: "1.0.0"), ], targets: [ // Targets are the basic building blocks of a package. A target can define a module or a test suite. // Targets can depend on other targets in this package, and on products in packages this package depends on. .executableTarget( name: "MyServer", dependencies: [ .product(name: "Vapor", package: "vapor") ]), .testTarget( name: "MyServerTests", dependencies: ["MyServer"]), ] )

Otherwise there's https://github.com/vapor/vapor

The Swift/Vapor project is a relatively easy way to do it.

Opening this webpage (https://vapor.codes) cranks my CPU (5800x3d) to 100% instantly. Why?

Vapor is the most popular non-Apple-ecosystem Swift project. There have been a few others, but none particularly popular.

Server-side apps (typically via Vapor)

My first option other than PHP was using Swift and Vapor. I have made some projects with iOS and Objective-C, maybe I could also learn Swift and create both native iOS apps and backends with the same language.

StreamCam is written 100% in Swift, SwiftUI & Combine. The serverside is handled with Vapor.