skip VS Alamofire

Came across this on GitHub (https://github.com/skiptools/skip), thought it was interesting.

The docs go into a bit more detail of how this works: https://skip.tools/docs/

Seems notable that the transpiler is free during the tech preview, but pricing will be announced later. While the generated Kotlin code is probably not 1:1 with what a human would write, at least it seems you aren't completely locked in to it if you decide to leave.

Interesting idea– definitely a lot of surface area to cover and I am curious to see how it does. I personally love native app development, but wonder how big the downsides are once you start getting into detailed UX designs/architecture patterns...

Maybe using this for UI only and using Kotlin Native would be a better middle ground, but with Compose Multiplatform for iOS in development that might be an overall safer bet for native shared codebases.

Alamofire is a swift http request lib. By default, we need use completion handler to handle response. Today we are going to find out how to use it with async and await.

Looks like your Alamofire tutorial is out of date. I suggest you read the current documentation and update your code. For instance, you can update your example to:

Alamofire - Elegant HTTP networking

Alamofire - Alamofire is an HTTP networking library written in Swift. (de facto standard library for network) Language: Swift.

You can find an example using Alamofire, the most commonly used network framework, here.

https://github.com/Alamofire/Alamofire/blob/master/Documenta...

To add Alamofire, we'll be using Swift Package Manager. Xcode comes with built-in support for it and we'll not have to use external package managers like Cocoapods or Carthage. Click on File → Add Packages...