Applite brings its own Homebrew. Every other Homebrew GUI expects brew to already be on the machine, which means the user has opened a Terminal and installed the Xcode Command Line Tools first. Applite downloads a Homebrew tarball into its own Application Support directory on first launch and runs it from there, in API mode behind a git shim.
No Terminal, no Command Line Tools. Applite can be the first app on a fresh Mac.
Brewfile import and export, so restoring your apps on a new machine is a file and a checklist.
Casks only, by design. No formulae, no services, no CLI surface. Apps in categories, with icons and a search field.
Uses your existing Homebrew if you have one. Point it at any prefix in Settings.
Comparison
Three actively developed alternatives worth knowing about. All of them are good software solving a slightly different problem.
Minimum OS version: macOS 14+. Universal binary, Apple Silicon and Intel.
Built With
Swift and SwiftUI, targeting macOS 14 so @Observable and NavigationSplitView are available without back-deployment shims. No Combine. The cask catalog is a local SQLite database (GRDB.swift, WAL mode) synced from the Homebrew JSON API, with FTS5 and BM25 ranking for full-catalog search. Loading is two-stage: SQLite paints the UI immediately, then brew list --cask and brew outdated --cask fill in installed and outdated state reactively, so nothing blocks on the brew CLI.
I'm the sole maintainer of Applite. Starting with version 1.4, I use Claude Code as part of my development workflow, and I'd rather state that plainly than leave people to guess.
The reason is capacity. This is a side project maintained by one person, and the realistic alternative to AI-assisted development is not hand-written code, it's a much slower release cycle or no releases at all. Several things that shipped recently, the SQLite migration and the six-language localization among them, would have sat in the backlog indefinitely otherwise.
Scope of what that actually means:
The core of the app was written by hand, before any AI involvement.
AI assistance is used for refactoring and reorganization work, and for small to medium sized new features.
Architecture decisions, code review, and what does and doesn't go into the app are mine. Nothing merges that I haven't read.
If you object to AI-assisted code on principle, that's a legitimate position and Cork is explicitly developed without it.
Contact
If you have any questions, feel free to e-mail me: [email protected]
For typos and minor bugs, open a PR directly. For anything larger, open an issue or bring it up on Discord first, so we don't both spend time on something that doesn't fit the project's scope.
Packages Used
Homebrew - the package manager everything is built on
GRDB.swift, Gwendal Roué - SQLite database and FTS5 search
App icons are sourced from CaskFlow by Ali Elsokary (MIT), a metadata pipeline that extracts icons from vendor .icns files. Casks without a CaskFlow icon fall back to a generated monogram tile.
License
Applite is licensed under the MIT License. See LICENSE for more details.
Alternatives
Compared above:
CaskHub - cask-focused app store with strong discovery features
BrewUI - Homebrew's official GUI, in early development
