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.

Minimizing network activity improves your build times, speeds up builds, and reduces costs. With ARC, you rely on multiple Actions steps in your workflow. What if you could avoid needing to download your most frequently used Actions? This post walks you through creating images with an Actions archive cache to eliminate those downloads.

If you’re going to build custom images for ARC or standalone VM runners, then you probably want to take some time to preload it with the tools that matter to your builds. If you want that process to work well for the GitHub-provided tools and actions/setup- Actions, then you’ll want to know how to prepopulate the runner’s tool cache.

Understanding ARC begins with understanding what it does (and does not do) to create runners on Kubernetes. The process is surprisingly straight-forward, and understanding it is key to mastering ARC.