If we’re going to build a Bluetooth app for WatchOS and iOS, we need at least one additional primitive to be available – a 24-bit unsigned integer. Since Swift doesn’t provide that, we’ll just have to create it ourselves. This post will dive into how to create a custom numeric data type in Swift (and how to overcome some limits of the platform in the process).

If we’re going to build a Blutooth-enabled application, the first step is understanding the basics of how data is provided to clients. In this post, I’ll explore some basic terminology and concepts. We’ll then look at how the data is structured so that we can interpret it in our application.

I decided that it was time to improve the integration between my treadmill and my watch. First, I upgraded my treadmill with a smart device that provides standardized services using Bluetooth Low Energy. Next, I created an application that integrated everything together. After that, I began this series to make it easier for you to build a Bluetooth-integrated application in Swift.

Continuing with our exploration of macOS notarization, today we’ll explore how to sign and notarize .NET console applications. Along the way, I’ll also show you the secret to making universal (“fat”) binaries for your application.

With the release of Apple Silicon came new requirements for distributing console applications. If you want to get past Gatekeeper, your console applications will need to be notarized. Today we’ll explore how you setup your environment to be able to notarize applications to support signing console applications (including .NET).