William Boles

When building the registration section of our apps, many of us will have heard that seductive whisper: "These fields are so alike.

As a project grows, modularisation becomes a valuable tool for managing that growth.

In the distant past, when dinosaurs still roamed the land, iOS focused solely on what the user was doing, ensuring a responsive user experience on performance-constrained devices.

Dealing with a JSON network response in iOS projects used to be a pain - you would have to manually parse the response, extract the required values, ignore those that weren't needed, and build your model instances 🤮.

UIAlertController alerts form the backbone of many interactions between our users and our apps.

Being British, queuing is essential to me.

Many of us feel nervous when meeting a group of people for the first time.

People really care about their possessions.

In our day-to-day life, dates are pretty straightforward - we read them all the time, make plans around them, and share them with other people.

Ask any iOS developer about DateFormatter and one of the first things you will hear is that creating a DateFormatter instance is an expensive operation.

Sometimes the tools that make our lives easier also make our architecture worse.

The example in this post is built using GCD to control access to shared mutable state.

It's 17:00 on a warm Friday evening.

Recently, I've been experiencing the iOS equivalent of the movie Inception - putting a collection view inside a collection view.

Core Data and Unit Testing belong to the same friend group, but they've never really hit it off.