core data

There are very few certainties in app development, but one is that once your app is released, it will change in unexpected ways. Meeting those changes can be painful. Here, we look at how to ease the pain of Core Data migrations.

Core Data and Unit Testing haven't always been the best of friends ⚔️. Core Data is all about persisting. Unit testing is all about forgetting. Here, we look at how they can work together with the help of UIKit to ensure that we gain the confidence we need to ship an app.

People really care about their possessions. They hate when change breaks those possessions 😡. This is as true of digital possessions as physical possessions. Your data model will change, but it doesn't need to break anything. Here, we look at how to migrate a Core Data model step-by-step.

Social networks work on the basis of presenting a feed and allowing the user to interact with the content contained in the feed in (hopefully) novel and interesting ways that the user derives usefulness (joy?) from. The presentation of the feed varies greatly from social network to social network bu

Application requirements evolve, which require us to refactor existing features. For the most part, Xcode's built-in refactoring tools work well; however, an area where the refactoring tools can't help is with stringy APIs. Core Data seems to be full of stringy method parameters - in this ar

I'm often asked to explain Core Data to the new joiners. I thought I'd share what I tell them about the components that make up Core Data: 1. Persistent store - is where Core Data stores its data, more often in a form of a SQLLite database but can be Atomic (binary store) or In-Memor

Adding search functionality to your UITableView can be achieved using the built in UISearchBar object and implementing the UISearchBarDelegate protocol. I am going to take us through an example that searches an Article instances (data object) properties for the users entered search string, displayin