Product breakdown · RunnerKit
How RunnerKit ships updates outside the Mac App Store
RunnerKit helps developers build and run Xcode projects. Shipping RunnerKit itself is a different job: existing users need a trustworthy way to receive new app versions. RunnerKit uses Sparkle for update checks and is one of the apps shipped with HarborPilot.
By Francisco Cantu ·
What RunnerKit does
RunnerKit is a native macOS companion for Xcode projects, with a menu-bar app and a bundled command-line interface. It saves build-and-run decisions so developers can return to a project without repeating the same setup.
The product’s site describes the division clearly: Xcode builds the project; RunnerKit handles installing, launching, observing, and stopping the resulting app. That is the developer’s day-to-day workflow, not the update delivery system for RunnerKit itself.
RunnerKit and HarborPilot are both developed by Francisco Cantu. This is a first-party product breakdown, not an independent customer testimonial.
What is documented about its distribution
- RunnerKit is available through its own website.
- Its public privacy policy says it uses Sparkle to check for app updates.
- Its pricing page describes a trial and one-time RunnerKit 1.x licensing, with checkout handled by Polar.
- RunnerKit is featured in HarborPilot’s Showcase as an app shipped with HarborPilot.
These facts establish the direct-distribution and updater relationship. They do not establish RunnerKit’s private project configuration, exact release commands, download storage provider, or time saved per release. This article does not invent those details.
See RunnerKit in the HarborPilot Showcase, or visit RunnerKit’s pricing page for its current offer.
Three tools, three different jobs
- RunnerKit: the product being delivered
- Helps its users build and run their own projects. It also needs releases of its own.
- HarborPilot: release preparation
- Provides the build, Developer ID signing, Apple notarization, stapling, Sparkle signing, and appcast generation workflow for outside-store Mac apps.
- Sparkle: update delivery inside the app
- Checks the appcast, discovers a compatible newer version, downloads and verifies the archive, and installs the update.
HarborPilot does not run an update server for the app. The developer publishes the prepared files on their own host. The particular host used for RunnerKit is not identified in the public material cited here.
The release workflow HarborPilot provides
For a connected Xcode project, HarborPilot’s release workflow follows this sequence. This describes the tool’s capabilities, rather than a reconstruction of private RunnerKit release logs:
- Write release notes. Explain the changes users will receive.
- Build & Release. Build the app and sign it with Developer ID.
- Notarize with Apple. Submit for Apple’s automated check and staple the accepted ticket.
- Prepare Sparkle files. Sign the update archive and write the appcast.
- Publish and verify. Upload the finished files to the developer’s host and confirm they are reachable.
This keeps release preparation on the developer’s Mac and keeps hosting under their control. Apple’s checks, valid signing credentials, and a tested updater remain necessary.
What an existing user’s update depends on
A working Sparkle integration needs a reachable HTTPS feed, valid update metadata, and an archive signed with the key the installed app trusts. The update must also meet the app’s version and compatibility requirements.
For an existing RunnerKit user, the documented role of Sparkle is checking for app updates. The site does not establish every updater preference or user-interface detail, so this article does not assume a particular checking schedule or automatic-install behavior.
For any app using this stack, test a real upgrade from an older shipped build. A release archive that launches on the developer’s machine does not by itself verify the hosted update path.
What you can apply to your own Mac app
- Separate product development from release preparation. Your app’s main job and the process of shipping it are different concerns.
- Use a proven updater. Sparkle covers discovery, signature verification, and installation; integrate it deliberately.
- Keep distribution choices independent. Your host and checkout do not need to be the same service as your release tool.
- Automate repeatable steps, then test the outcome. Signing and notarization automation does not eliminate end-to-end upgrade checks.
Start with setting up Sparkle. If you are still choosing a channel, read Developer ID versus the Mac App Store. The R2 guide shows one hosting option; it is not a claim about RunnerKit’s host.
Simplify your next release with HarborPilot.
RunnerKit is one of the apps shipped with HarborPilot. If your Mac app also ships outside the store, HarborPilot can take the repeated build, signing, notarization, and Sparkle packaging work off your release checklist—while you keep your own hosting and customer relationship.
Sources and further reading
- RunnerKit: product and download website
- RunnerKit privacy policy: developer and Sparkle update checks
- RunnerKit pricing and licensing
- HarborPilot Showcase
- Sparkle documentation
Service limits and Apple requirements can change. Check the linked documentation before publishing. HarborPilot is not affiliated with Apple, Cloudflare, or the Sparkle project.