# LaunchNext: restoring the Launchpad on macOS 26 Tahoe

> LaunchNext is a Swift launcher that rebuilds the classic Launchpad on macOS 26 and later, importing your old layout from Apple's own database. It is GPL-3.0, installable with Homebrew, and honest about its code signing limits.

**RoversX/LaunchNext** — Bring your Launchpad back in MacOS26+ ,highly customizable, powerful, free.

- Repository: https://github.com/RoversX/LaunchNext
- Website: https://closex.org/launchnext/
- Stars: 3,053 · Forks: 148
- Language: Swift
- License: GPL-3.0
- Published: 2026-09-24 · Updated: 2026-09-24 · Language: en
- Canonical page: https://hysenlabs.com/projects/roversx-launchnext

## The gap LaunchNext fills on macOS 26 Tahoe

macOS Tahoe removed Launchpad. The README lists what went with it: no custom app organization, no user-created folders, no drag-and-drop customization, no visual app management, and forced categorical grouping. For anyone who had spent years arranging apps into folders on the old grid, that is a workflow deletion, not a redesign.

LaunchNext is a replacement launcher for exactly that group: people who upgraded to macOS 26 and want the old interaction model back. It is not a general-purpose launcher for older systems. The stated requirement is macOS 26 (Tahoe) or later, on Apple Silicon or Intel. The project is a Swift application, licensed GPL-3.0, and it is built on LaunchNow by ggkevinnnn, which the README credits directly and which chose the same licence.

The pitch is deliberately narrow. The README frames the project as a stopgap: "Before that, here is LaunchNext," written in the hope that Apple restores an option to switch back. That framing matters when you decide whether to depend on it.

## Importing your old Launchpad layout from Apple's SQLite database

The most concrete mechanism in the project is the importer. LaunchNext reads the native Launchpad database at the path the README gives:

```bash
/private$(getconf DARWIN_USER_DIR)com.apple.dock.launchpad/db/db
```

That path is resolved per user through getconf, so the importer does not hardcode a home directory. From that database it recreates folders, app positions and layout, according to the README. In practice this means the migration cost is close to zero: your previous arrangement is the starting point rather than something you rebuild by hand.

Everything else is stored separately, in the app's own container:

```
~/Library/Application Support/LaunchNext/Data.store
```

So there are two data sources with different lifetimes. The system database is read for import; LaunchNext's own store holds your working state afterwards. If you later delete or reset the app's data, the original Launchpad database is still the fallback as long as macOS keeps it around, which the README does not promise either way.

The rendering side has two engines. Legacy Engine and Next Engine + Core Animation are selectable in Settings. The README ties drag-to-Dock and paged or vertically scrolling folder contents to Next Engine + Core Animation, which suggests the two engines are not feature-identical and that the newer one is where continued work goes.

## Installing LaunchNext with Homebrew and importing your layout

The README gives Homebrew as the install path. Two commands, run in Terminal:

```bash
brew tap RoversX/homebrew-tap
brew install --cask launchnext
```

The cask is described as being mainly for installation and manual upgrades, because LaunchNext ships its own updater. If you prefer to let the app update itself, install once and stop using brew upgrade for it.

If macOS refuses to open the app, the README gives a quarantine removal command:

```bash
sudo xattr -r -d com.apple.quarantine /Applications/LaunchNext.app
```

That command strips the quarantine flag from the whole app bundle. The README's own guidance is to only use it on apps you trust, which is the right instinct: you are disabling a Gatekeeper check, not fixing a bug.

Once it opens, the first launch scans installed applications automatically. Then open Settings with the gear icon and click Import Launchpad. Your existing folders and positions are imported. From there, drag apps to create folders, type to filter, and enable CLI in Settings if you want terminal access to the layout.

For source builds, the README requires Xcode 26. The signing instructions are unusual and worth following exactly: set Team to None and choose Sign to Run Locally, keep Hardened Runtime on, and do not commit signing-only changes. It also warns that ⌘+R only works when the run destination is My Mac, not Any Mac.

## Code signing: the notarization promise and its one-year horizon

This is the part of the project most likely to affect you in a year. The README states that, after considerable effort, releases from LaunchNext 2.4.2 onward are signed and notarized by Apple. It then says the membership lasts a year, keeping it active is not cheap, and if it lapses, future releases will go back to unsigned or ad-hoc builds.

Read that as a maintenance risk rather than a flaw. A signed build opens without the quarantine workaround. An unsigned build does not, and the xattr command becomes part of your install routine again. The project is not hiding this; it is telling you the arrangement is temporary.

The release list you can see tops out at 2.4.1, dated 2026-05-01, which is before the 2.4.2 signing cutover the README describes. So the signing status of the exact build you download is something to check on the release page, not assume from the README.

One more constraint: the README notes that if you change local signing settings, Xcode may mark the project file as modified. Contributors are told not to include signing-only changes in a pull request. Small thing, but it will trip up a first-time contributor who commits everything.

## Where LaunchNext is the wrong choice

The requirement line is macOS 26 (Tahoe) or later. If you are on macOS 15 or earlier, you still have Launchpad and LaunchNext adds nothing except a second launcher to maintain. The project exists because of a removal that has not happened on your machine.

Second, this is a GUI replacement for a system feature, which means it depends on a private, undocumented Apple database for its best feature. The README gives the path but no compatibility statement. If Apple changes that schema, the importer is the first thing to break, and the README does not describe a fallback import format. Manual organization would still work; one-click migration might not.

Third, the README does not document rollback. There is no stated procedure for returning to the stock macOS 26 behaviour beyond quitting the app, and no statement about what happens to your imported layout if you remove the app. The Data.store path is given, so you can back it up yourself, but nothing in the README tells you to.

Finally, if you need a signed, notarized binary as a hard requirement, the signing section is a warning, not a guarantee. The project says it may not renew.

## LaunchNext vs LaunchNow and the other launcher options

LaunchNext is a fork of LaunchNow by ggkevinnnn, and the README credits it prominently, even asking readers to star it. Both are GPL-3.0. That shared licence is the practical difference between them and most of the other names that show up in searches: with a GPL-3.0 launcher you can read the source, build it yourself with Xcode, and fork it if the maintainer stops.

Compared with LaunchNow specifically, the README's feature list is where LaunchNext differentiates: CLI and TUI support, hot corners and four or five finger gestures, Core Animation folders with paged and vertical scrolling, drag-to-Dock in Next Engine, an update tab rendering Markdown release notes, and a broader set of interface languages. Whether those matter depends on whether you work from the terminal and use gestures, or just want the grid back.

The other alternatives people search for, such as LaunchOS, BuhoLaunchpad, LaunchMe and Launchie, are not described in this material, so I cannot compare their mechanisms. What can be said is structural: LaunchNext's distinguishing move is reading Apple's own Launchpad database for import rather than asking you to rebuild folders by hand. If a competing tool does not do that, migration is the difference you will feel on day one.

## Licence, maintenance and upgrade cost

LaunchNext is GPL-3.0, inherited from LaunchNow, and the README states that plainly. For end users installing the Homebrew cask, the practical effect is that the source is available and forks are permitted under the same terms. If you embed LaunchNext in a product you distribute, GPL-3.0 obligations apply to that distribution. That is a summary of what the README says, not legal advice; talk to someone qualified before shipping it inside something else.

The repository is not archived, and the last push was on 2026-09-21, three days before this writing. Releases visible here are 2.4.1 on 2026-05-01, 2.4.0 on 2026-03-13 and 2.3.0 on 2026-03-01, so the release cadence over that window was roughly every six to eight weeks, with commits continuing between them.

Upgrade cost is low by design. The app carries its own updater, and the README says the Homebrew cask is mainly for installation and manual upgrades, so you pick one path. The thing to budget for is not upgrades but the signing question: at some point you may be running the xattr command again, and you should decide now whether that is acceptable on the machines where you install it.

## Conclusion

Adopt LaunchNext if you are on macOS 26 or later and miss folders, drag-and-drop arrangement and the old Launchpad layout; the Homebrew cask plus the Import Launchpad button gets you back to your previous setup in two steps. Skip it if you are on an older macOS, since the README lists macOS 26 as a requirement, or if you need a signed build today and cannot wait for a notarized release. Before installing, check the release notes for 2.4.2 or later to see whether the build you are downloading is signed, and confirm whether the quarantine removal command is still needed for that version.

## FAQ

### What is LaunchNext used for?

It replaces the Launchpad that macOS 26 Tahoe removed, restoring custom app organization, user-created folders and drag-and-drop layout. It can also import your previous Launchpad arrangement from Apple's own database.

### Does LaunchNext work on macOS versions before Tahoe?

No. The README lists macOS 26 (Tahoe) or later as the requirement, on Apple Silicon or Intel. On earlier systems you still have the built-in Launchpad.

### How do I install LaunchNext?

The README gives Homebrew: tap RoversX/homebrew-tap and install the launchnext cask. If macOS blocks the app, the README provides an xattr command to remove the quarantine flag, with the warning to only use it on apps you trust.

### Is LaunchNext signed and notarized by Apple?

The README states that releases from 2.4.2 onward are signed and notarized, but that the membership lasts a year and may not be renewed, in which case releases would go back to unsigned or ad-hoc builds. Check the release page for the build you are downloading.

### Where does LaunchNext store my layout?

Application data lives at ~/Library/Application Support/LaunchNext/Data.store. Imports come from the system Launchpad database at /private$(getconf DARWIN_USER_DIR)com.apple.dock.launchpad/db/db.

## Sources

- [License: GPL-3.0](https://github.com/RoversX/LaunchNext/blob/main/LICENSE)
- [Project website](https://closex.org/launchnext/)
- [README](https://github.com/RoversX/LaunchNext/blob/main/README.md)
- [Releases](https://github.com/RoversX/LaunchNext/releases)
- [RoversX/LaunchNext on GitHub](https://github.com/RoversX/LaunchNext)

---

Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/roversx-launchnext