App Group and the Windows taskbar grouping problem it solves

Groups hold launch shortcuts, not running windows

The first thing to understand about App Group is what a group actually contains. A group is a named collection of application entries that you launch, not a container for windows that are already open. The project description says it lets you organize, customize and launch your apps, and the feature list is entirely about creating, editing, duplicating and reordering groups.

That distinction decides who finds the tool useful. Windows 11 still refuses to let a user pin an unlimited number of items to the taskbar, and once you have thirty or forty shortcuts the taskbar turns into an unreadable strip of overlapping icons. App Group is a workaround for that specific limit. You make a group per activity, give it one icon, and the taskbar holds a handful of group icons instead of a hundred app icons.

The grouping is nested to an unlimited depth. An existing group can be added as an item inside another group, which the documentation calls a subgroup, and the same launcher therefore handles a three-level structure without a separate mechanism for it.

Dragging a group icon onto the taskbar is the whole pinning trick

Pinning is what gives a group its value, and the project offers two routes. The first is direct: drag the group icon onto the taskbar. The second goes through the file system. Open the app menu, choose Open File Location, then right-click the shortcut and select Pin to Taskbar.

Both routes exist because the second one is the only one that works when the taskbar refuses a programmatic pin, and it also gives you a shortcut file you can move or inspect. The README does not describe a command line or a configuration file for pinning, so this is a mouse-driven tool in that respect.

A group icon is not a passive picture. The jumplist attached to a pinned group offers two actions, Edit this Group and Launch All, so the pinned icon opens into a launcher popup rather than launching a single application. Launch All is the useful one for a group of related tools, and Edit this Group saves a trip back to the main window.

Group icons can also be dragged to the Desktop, and the utility maintains a system tray presence alongside that.

A group icon can be a picture, a generated grid, or an executable

The icon system has three sources, and this is where the customization options concentrate. A group can use a single icon file you pick, or it can use an auto-generated Grid icon assembled from the icons of the apps inside it, which means a group of design tools gets a composite tile for free. A third option lets you use an .exe file as the custom icon, so you can point at a program without extracting anything from it.

The Grid icon is not configurable in detail, but the layout around it is. A group can use the Default layout or the Card layout, and the grid column count is adjustable, so a group of twelve apps can be a four by three block rather than a thin column. Accent-colored group backgrounds are supported, and the group name header can be shown or hidden and positioned at the Top or the Bottom.

Dark Mode and Light Mode are configurable independently for the main window and for the popup, which matters for anyone who runs a dark shell and prefers a light taskbar popup, or the other way round. Window and content animations are toggleable, and a hybrid in-memory and persistent icon cache is used for faster load times, with the utility auto-refreshing taskbar icons when a group icon changes.

UWP and PWA apps need a shortcut created by hand

Not every app can be dropped into a group. UWP apps such as Calculator and Settings do not exist as regular files on disk, so there is nothing to drag. The project documents a manual procedure for them: open the Run dialog with Win + R, type shell:AppsFolder and press Enter to open a folder listing all installed applications, then find the app, right-click it and choose Create shortcut. If prompted, confirm with Yes, and the shortcut lands on the Desktop, ready to be dragged into a group.

It is a small thing, but it is the sharpest edge in the whole workflow. The first attempt at using the tool with a modern Windows app ends at a Create shortcut prompt, and the shortcut it produces is a normal desktop link rather than a first-class app entry.

The rest of the app coverage is broader. PWA apps work through shortcuts, .lnk shortcuts are supported without the arrow overlay where the platform allows it, and Steam shortcuts arrive as .url entries. Apps can be launched as Administrator, and per-app launch arguments and custom tooltips are supported, so a group can carry a shortcut to one program with a specific switch set.

The .agz archive moves groups between machines, and imports never overwrite

Group definitions are portable through a format the project calls.agz, an AppGroupZip archive used for import, export, backup and sharing. The import path is the more interesting half, and it carries two rules that protect an existing setup.

The first is that a preview is always shown, listing the groups to be imported, and each one is individually checkable before you confirm. The second is that imported groups are always appended, and never overwrite existing ones. Combined, those mean a bad archive cannot destroy a configuration you already have, which is a reasonable design for a tool whose whole job is mutating a taskbar.

Import also understands the TaskbarGroups format, so an existing setup from that tool can be migrated directly. The documentation also notes that the project itself is a C# solution with an AppGroup.sln and an AppGroup/ directory at the root, and the code is MIT licensed, so a.agz file is not an opaque binary in the sense that matters for trust.

Four download variants and a warning about copies

Installation is a download and a run, and the choice of package is the part that trips people up. The project publishes four variants, distinguished along two axes: whether an installer is included, and whether the .NET 8 runtime is bundled.

Setup includes the installer but not .NET 8, so a machine without the runtime installed will need it. Setup (Bundled) includes the installer and the runtime, and the documentation recommends this variant for anyone unsure. Portable has no installer and no bundled runtime, so the archive is extracted and AppGroup.exe is run directly. Portable (Bundled) is the same without the installer but with the runtime included.

The practical advice is to pick deliberately. A locked-down corporate machine that forbids installers still works with a portable build, but only if that build bundles .NET 8, and a home machine with the runtime already present can take the smaller Setup package.

There is a second caveat, and it is unusual to see. The README asks users to make sure they download from the official repository, stating that an infringing copy has been published on GitHub and on the Microsoft Store with no attribution, in violation of the MIT licence, and that DMCA notices have been filed. Taking the release from the official releases page avoids that problem entirely.

Release cadence, licence and where the maintenance claim stops

The release history shows a steady line. v1.3.0 came on 2025-08-21, v1.4.0 on 2026-01-23, and v1.5.0 on 2026-04-23, and the last push to the repository was on 2026-10-11, so development on the default master branch is current.

The README states that App Group is actively maintained and asks users to consider supporting development through a Ko-fi donation link. Nothing in the repository contradicts that, and the MIT licence is a permissive one that allows commercial redistribution and modification provided the notice travels with the code. For a taskbar utility the licence is not the constraint on adoption; the constraint is that it is a Windows only tool written in C#, with the taskbar positions it supports being Top, Bottom, Left and Right.

Two smaller features round out the system. A built-in update notifier tells you when a new build is available, which matters for a utility that runs at startup and sits in the system tray, and a run at startup option keeps the groups available without a manual launch. A grayscale taskbar icon option is also included for anyone who wants the pinned group icons to blend into a monochrome taskbar.

Editorial conclusion

App Group is a good fit for a Windows 11 user whose taskbar has filled up with shortcuts for tools that only need launching occasionally, and for anyone migrating from TaskbarGroups who wants a preview before importing. It is a poor fit for anyone hoping to arrange open windows, since the groups hold launch shortcuts rather than running instances, and it is a poor fit for a shared or locked-down machine where the portable variant cannot be extracted or the installer cannot be run. Before downloading anything, pick the variant deliberately, since the two Setup packages differ on whether .NET 8 is bundled, and take the release from the official repository, whose own README warns that an unattributed copy has been published on GitHub and the Microsoft Store.

Frequently asked questions

Official sources

1. iandiv/AppGroup on GitHub
2. License: MIT
3. Project website
4. README
5. Releases