Over the last 15 years, CPU clock rate has plateaued due to thermal limitations in processors. As a result, CPU manufactures have instead chosen to add more cores or processing units. Therefore nearly every device has multiple cores: from a Mac Pro to the Apple Watch. For this reason, Swift developers should take advantage of asynchronous methods.
In the development of my latest app which is an Independent Watch App that uses HealthKit, I ran into an issue with App Store Connect. App Store Connect will complain about missing Purpose Strings, that is the messages display to the user when access permission is asked for health information.
Last month I spoke at SwiftTO in Toronto, a great conference with some great speakers. If you get a chance, check out all the talks here. My topic of choice was Vapor and how to get started. Here is the talk description:
While Swift has been on Apple devices such as the iPhone, iPad, Apple Watch, Mac, and Apple TV, in the last few years it has started to reach the Linux Operating System. This has allowed Swift to move from client devices to servers. Now we have several server side frameworks such as Perfect, Kitura, and Vapor. In this talk, Leo Dion goes into the details of developing with Vapor on the Mac to deploying onto the server. We talk about managing multiple process in Swift-NIO, the Fluent ORM, serialization of data, and the setting up of routes and authentication. If you are interested in taking a deep dive into Vapor, you’ll want to check out this talk.
WWDC 2019 was a major year with Catalyst, Apple Watch, iCloud and of course SwiftUI. After WWDC 2019 this summer, I did three podcast episodes highlighting some of the important new lessons we learned.
For beginners learning Swift, it can be a challenge to find the right Mac for developers. As with many things, I strongly believe you shouldn’t spend too much money until you know you will be making a real commitment to a project. Rightfully, this includes Swift and iOS development.
It can be a real challenge picking the right back end for your mobile app. For instance, Swift developers don’t have anything without needing to run on another language. Therefore, I decided to do a review of Vapor and whether it is really a right choice.
In this episode, Leo talks different backend technologies to use when building an iOS app or any other Apple device: when you need a cloud service, running on your own server, cloudkit, firebase, and more…