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.

When working with offset pagination, the page is often thrown away. Losing that content to page relationship can make merging new content into existing cached content tricky. Here, we look at how to keep the page around and simpilify things.

Working with stringy APIs is prone to runtime errors, as the compiler can only enforce that a string is there or not, rather than if the value is correct or not. Core Data loves a stringy API. Here, we look at how to enhance the compiler's involvement with Core Data by de-stringifying the API.

Manually scrolling through a list of information to find what we need can be time-consuming, even for modestly sized lists. Here, we look at how to search through a list to find what we need using `UISearchBar`.