Product infrastructure · Swift
ForgeKit
The repeated work behind more than 60 product launches, turned into reusable Mac app building blocks.
Problem
Repeated settings, onboarding, updates and diagnostics work slowed every Mac product and multiplied inconsistencies.Solution
Eighteen modular Swift packages with shared conventions, injectable services and limited dependencies.Impact
449+ tests across 83 suites protect reusable foundations that make every new app faster to build.
The problem
Every Mac app needs settings, onboarding, permissions, shortcuts, updates, diagnostics and monetisation. Rebuilding them app by app slows delivery and multiplies inconsistencies.
The solution
ForgeKit turns that work into 18 Swift modules. An app can use the whole package or only the parts it needs, while keeping native Mac behaviour.
Built around jobs every Mac app needs
ForgeUI provides the shared interface foundation. ForgeCore brings common modules together, while optional services such as Sparkle updates and TelemetryDeck analytics remain separate.
The evidence
Settings and onboarding are described in a short format instead of rebuilt screen by screen. Shared styles align the apps, while replaceable services make analytics, permissions and review prompts easier to test.
Modern foundations, limited dependencies
ForgeKit uses Swift 6 concurrency and modern state observation. AppKit and Carbon remain where the Mac requires them, including status items, panels and global hotkeys. Sparkle and TelemetryDeck are the only external dependencies.
The impact
More than 449 tests across 83 suites protect the shared foundation. Improvements can reach the next product and the existing portfolio instead of being rebuilt repeatedly.
The result