I wrote my first line of code for an iOS app in 2009 (yes, Objective-C back in the days). I've worked at an agency where we did many releases every month. Some of them were automated, but most of them we released manually.
You'll not be surprised to hear that I've got many examples of releases that went wrong: - Using the wrong commit for the release - Releasing with a debug scheme - Targetting staging instead of production
And so on!
What you might expect is that these failures no longer happen in a team of primarily experienced engineers. Though, for those just getting started with iOS development: we still make mistakes!
We did a release manually this time since our CI didn't work. Suddenly, our local configuration was used for delivering a new App Store build. In this case, we forgot to update our local private keys file, which resulted in us releasing an outdated tracking identifier.
The mistake is not the critical part here; it can happen. It's much more important how you deal with these events. For us, this meant writing down a manual for performing releases manually. The first thing this manual states is to make sure our local keys are up to date before performing the release.
You might already be familiar with guard statements, but there's still an interesting point to discuss! When should you use a guard statement over an if let statement? In my opinion, this is one of the most opinionated parts of Swift since it has often been a discussion in pull request reviews I did. New to guard statements? I got you covered.
Increase your application's performance with rich context about errors and slowdowns in your iOS applications. Get started with 2 free months of Sentry’s Business Plan (the best one) with code: SWIFTLEE
If you’re looking for a color system in SwiftUI, this article by Rudrank Riyam might be a great read. The solution uses an asset catalog as a backing store for defined colors and describes how you can write a simple test to ensure colors exist. To make it complete, use some useful SwiftUI extensions to access your defined colors easily. Oh, and if you need the same for fonts, Rudrank got you covered as well!
I guess it depends on what you’ll be doing, but Ben Sandofsky at least shows us a real-world example of using Computer Science to speed up a blur. I loved the explanation, learned how blurs work and enjoyed watching a great developer explain.
The syntax described by Alejandro Martinez always fascinated me. I’ve never used a framework like Then, simply because I like to stay close to default Swift APIs, but the syntactic sugar it brings is indeed inspiring!
I stumbled upon this page by accident, but I was thrilled to find it! Being able to filter on proposals that got accepted can be an excellent way to look forward to what’s coming up in the next version of Swift.
If you’ve been asking this question to yourself, you might be happy to bookmark this website by James Dempsey. It’s straightforward and shows the latest available version of Xcode, including the Swift version. Yet, I genuinely believe some of you might be happy to have such a website at hand when needed.
Have you ever thought about the carbon footprint of the apps you create? How many emissions in kg CO2/month your app increases when you increase the size of your app by 1MB? I certainly did not! This article by Emerge Tools explains the impact of the size of the apps that we write today.
Paper® is the immersive sketching app for capturing ideas anywhere. Over 30 million people have found their personal creative space in Paper—handwriting notes, drafting, diagramming, sketching, and giving form to...