At this year’s WWDC, Apple announced that they would be open sourcing Swift. Now that the code is available, we can finally see what they’ve been working on.
With ever more devices and new multitasking features supported by iOS, it’s important to create user interfaces that scale gracefully to different screen sizes. Size classes are the most effective tool for tackling this problem. In this post, we’ll look at what size classes are and how to use them.
Software development is notoriously counterintuitive, especially if you’ve never written any code. In this post, we’ll explore some common misconceptions along with pieces of wisdom from experts in the field.
This is a continuation of a previous post discussing language features in Swift. In this post, we’ll look at a few additional examples.
In a previous post, I started going over some useful Auto Layout tricks that every iOS developer should know. In this post, I’ll continue with a few more ideas of greater complexity.
With iOS now available on more screen sizes, proficiency with Auto Layout has become a necessity. Unfortunately, I’ve observed many novice iOS developers whose first reaction to Auto Layout is to shy away. It can be intimidating, so in this post I’ll show a few common tricks that show the power and ease of use of Auto Layout.
I recently released my new app, Chess Clock Plus, which I wrote entirely in Swift. This was my first all-Swift app. It was also my first iOS 8-only app, so it was a chance to explore the new APIs. In this post, I’ll discuss the new tricks I’ve discovered.
I am infatuated with chess. I’ve known the basic rules for as long as I can remember, but had not gained an appreciation for the game’s nuances until recently. The game designer in me was hooked by the game’s endless complexity, and how it arises out of a set of simple rules. The software developer in me was intrigued by the game’s algorithmic nature.
This post is a follow-up to my earlier post about the life cycle of UIViewController. In this post, we’ll look at the logic behind UIView, another class that every iOS developer will inevitably subclass.
When programming in iOS, it’s inevitable that you’ll need to subclass UIViewController. These subclasses contain all the logic that makes your apps look and behave as they should. It’s hard to set up a subclass without knowing which overridden methods will get called and when. To remedy this potential confusion, this post will take a look at the life cycle of a UIViewController.