Know how to safely run concurrent Swift code — When the first time I saw the WWDC presentation about actors, I was thrilled with what it is capable of and how it will change the way we write asynchronous code in the near future. By using actors, writing asynchronous code that is free from data races and deadlocks has…

When creating widgets for your apps, sometimes it might be sufficient to just display data that is locally generated. However, in most cases, we will want our widgets to display data that is fetched from a remote server. In this article, let’s explore this topic. We will create a sample…

Updating widgets with Timeline Provider — Due to the always-on nature of a widget, Apple has introduced a way for developers to refresh a widget to ensure its power efficiency and prevent developers from exploiting the processing power of a device. In this article, I would like to show you what it takes to refresh your…

This article is originally published at swiftsenpai.com Having multiple widgets with various functionalities is quite a common feature for apps nowadays. For example, a shopping app can have a widget that shows today’s promotion and another widget that shows the user’s order status. Apple has given us 2 ways to…

This article is originally published at swiftsenpai.com In iOS 16, Apple has given the Lock Screen a massive overhaul. One of the most anticipated features that come along with the overhaul is the Lock Screen widgets. As the name implies, Lock Screen widgets are widgets that display glanceable content that…

All you need to know to create your first Home Screen Widget — This article is originally published at swiftsenpai.com WidgetKit was first introduced in iOS 14 as a simple framework whereby developers can leverage to create a Home Screen Widget. Since then, it has slowly evolved into a framework that powers some of the most anticipated features in iOS 16, namely Lock…

What I discovered is quite fascinating! — A few weeks back, I read an article by Wojciech Kulik, where he talks about some of the pitfalls in the Swift Concurrency framework. …

It is easier than you think — Prior to iOS 16, having a collection view or table view that will display placeholder cells while waiting for data to load is somewhat troublesome to implement. We will have to define 2 separate custom cells (the placeholder cell and the actual cell) and manually handle the UI logic based…

Nope… indexPathsForVisibleRows is not the solution — Imagine you are given a task to find out which table view cells are currently fully visible on screen. So you fire up Xcode, access the UITableView’s indexPathsForVisibleRows and expect that to get the job done. Very soon, you will notice that something is not right. The result you get…