AppKit: a shared foundation for Windows applications
Shared application infrastructure for identity, logging, settings and secrets, with UI support for WinUI3 and WPF and a Velopack update path.
in progress
A desktop application needs more than its primary feature. Identity, settings, logs, secrets, updates and failure reporting are part of the experience people depend on. AppKit gives those responsibilities a shared foundation across Windows applications.
CTO to Human: repeat the product idea, not its plumbing
When every application solves these concerns separately, maintenance grows with the number of products. A shared foundation makes a useful improvement reusable: a clearer log viewer or a safer settings write can benefit more than one application.
The public repository describes AppKit as extracted from GCLO’s application infrastructure. That gives the abstraction a concrete source: responsibilities already needed by a real application, rather than a framework designed around hypothetical consumers.
Engineer to Engineer: separate state from the UI toolkit
The package design separates a UI-free Core from Updates and the WinUI/WPF adapters. Core includes application identity, per-user paths, settings storage, logging and a Credential Manager-backed secret vault. Updates coordinates Velopack behavior and GitHub feeds; stable and development channels are distinct concerns. UI packages provide the splash, About, log and failure surfaces appropriate to each toolkit.
The documented UI construction approach uses code rather than sharing compiled XAML between packaged and unpackaged distribution paths. That is a concrete response to deployment constraints, not a requirement that every application adopt the same visual design.
The AppKit repository contains the package contracts and samples. This hub will connect those contracts to consumer applications and changes that improve their operational behavior.