LaunchNext tackles a problem macOS users face with the removal of the classic Launchpad experience in macOS 26 (Tahoe). Instead of reinventing the wheel with a new app launcher, it reads directly from the macOS internal Launchpad database to reconstruct your app layouts, folders, and positions exactly as they were. This approach dives under the hood of Apple’s proprietary system to deliver a familiar user experience lost in recent macOS updates.
how LaunchNext restores the classic Launchpad experience
LaunchNext is a macOS app written entirely in Swift, targeting macOS 26 and later. It works on both Apple Silicon and Intel Macs thanks to universal binary builds generated with Xcode 26. What sets it apart architecturally is its direct interaction with the system Launchpad SQLite database located under /private$(getconf DARWIN_USER_DIR)com.apple.dock.launchpad/db/db. This database holds all the user’s app organization details — the layouts, folder structures, and app positions.
By reading this database, LaunchNext can import existing setups rather than forcing users to reconfigure their launchers. It offers two rendering engines: a Legacy Engine that mimics the classic UI and a Next Engine built on Core Animation for smoother performance and more modern visuals.
The app also supports fuzzy search, command line and terminal user interface (CLI/TUI) modes for automation, hot corner activation for quick access, and multi-display positioning to work seamlessly in multi-monitor setups. The project is released under GPL-3 license and distributed via a Homebrew cask, with its own updater to keep the app current.
what makes LaunchNext technically interesting
The standout technical aspect here is the decision to reverse-engineer and utilize Apple’s internal Launchpad SQLite database. This approach is both clever and risky: it relies on private system data structures that Apple could change without notice in future macOS releases. But it also means LaunchNext can replicate user layouts with precision, something few alternatives manage.
The Swift codebase is surprisingly clean and leverages modern macOS frameworks like Core Animation to optimize UI rendering. Supporting both Apple Silicon and Intel with a universal binary is a practical choice given the diverse Mac hardware in use today.
The CLI/TUI support is a nod to power users who want to script or automate their launcher experience, which is rare in GUI-focused macOS utilities. It also includes a hot corner activation feature, which integrates well with macOS’s native interaction patterns.
Tradeoffs include the need to bypass macOS’s app quarantine restrictions due to the lack of an Apple developer certificate. This requires users to manually remove the quarantine flag using terminal commands — a friction point but understandable given the cost barrier for open-source maintainers.
Overall, the architecture reflects pragmatic engineering: direct database access for fidelity, two rendering engines for flexibility, universal builds for compatibility, and CLI modes for automation.
quick start
Installation with Homebrew is straightforward:
brew tap RoversX/homebrew-tap
brew install --cask launchnext
Because LaunchNext is unsigned, macOS may block it. To run the app, you might need to execute:
sudo xattr -r -d com.apple.quarantine /Applications/LaunchNext.app
Building from source requires macOS 26, Xcode 26, and either Apple Silicon or Intel hardware:
- Clone the repo:
git clone https://github.com/RoversX/LaunchNext.git
cd LaunchNext
- Open the project in Xcode:
open LaunchNext.xcodeproj
- Build and run via Xcode or use the command line:
Regular build:
xcodebuild -project LaunchNext.xcodeproj -scheme LaunchNext -configuration Release
Universal binary (Apple Silicon + Intel):
xcodebuild -project LaunchNext.xcodeproj -scheme LaunchNext -configuration Release ARCHS="arm64 x86_64" ONLY_ACTIVE_ARCH=NO clean build
At first launch, LaunchNext scans installed apps, lets you select and organize them, supports drag-and-drop folder creation, and enables CLI workflows through settings.
verdict
LaunchNext fills a niche for macOS users who miss the classic Launchpad experience and want to restore it without losing their existing layouts. Its direct use of the Launchpad SQLite database is a technically interesting approach that offers precision but carries the risk of breakage with future macOS updates.
It’s relevant for enthusiasts who appreciate open-source macOS utilities, developers curious about macOS internals, and power users who value CLI automation alongside a native GUI. However, it requires macOS 26 and some manual intervention due to the lack of an Apple developer certificate.
If you value exact layout restoration and are comfortable with the occasional manual step, LaunchNext is worth exploring. For others, it demonstrates a solid example of macOS native app development that interacts deeply with system internals while balancing compatibility and user experience.
Related Articles
- Navigating NixOS and Flakes with a community-driven beginner’s guide — A practical look at the “NixOS & Flakes Book,” an unofficial, community-driven guide demystifying NixOS and its experime
- nix-darwin brings declarative NixOS-style system management to macOS — nix-darwin adapts NixOS’s declarative system configuration model to macOS, enabling reproducible, version-controlled sys
- Vaultwarden: a resource-efficient Rust implementation of the Bitwarden server API — Vaultwarden is a lightweight, Rust-based server compatible with the Bitwarden API, optimized for self-hosting with low r
→ GitHub Repo: RoversX/LaunchNext ⭐ 2,478 · Swift