Download
Free, for Windows, Mac, iPhone and iPad, Android and Linux. Choose your device: the newest build, and where a store carries GroupLab, the copy it keeps up to date.
grouplab-setup-win-x64.exe
Nightly 222, built 2026-10-26 from commit c3bd808.
Windows 10 and 11. Installs into your own user account, with an entry in Add or remove programs.
Honestly: it passed the tests, which is not the same as somebody having used it.
The Store keeps GroupLab up to date itself and installs it without the "Windows protected your PC" warning. It gets every nightly too, once Microsoft has certified it, usually a day or so after it is published.
Not sure? Take the Microsoft Store copy if you want GroupLab to look after itself. Take the newest if you want each fix the day it is made and do not mind the odd broken build.
grouplab-win-x64.zip
Windows 10 and 11. Unzip it anywhere and run GroupLab.App.exe.
The Windows and Linux builds are unsigned, because signing costs money the project has not spent. Windows says this about any program nobody has paid to sign. The source of every build is public, at the commit the download names.
GroupLab.App.exe.The Microsoft Store copy does not show this warning.
grouplab-macos-arm64.tar.gz
Nightly 222, built 2026-10-26 from commit c3bd808.
For any Mac with Apple silicon. Self-contained, built on macOS, and tested by the suite on every change.
Honestly: it passed the tests, which is not the same as somebody having used it.
GroupLab is not in the Mac App Store. Every Mac download is the newest build, and GroupLab tells you when a newer one exists; you download it yourself.
Not sure? Apple menu, then About This Mac. A chip whose name begins with M is Apple silicon, and this is its download; Which Mac have I got, below, says more.
grouplab-macos-x64.tar.gz
For a Mac with an Intel processor. Self-contained, built on macOS, and tested by the suite on every change.
Apple menu, then About This Mac. A line saying Chip and a name beginning with M is Apple silicon. A line saying Processor and Intel is the Intel one.
Taking the wrong one gives you an application that will not open, with no useful message about why.
From nightly 135, the macOS build is signed with a Developer ID, notarized by Apple and stapled. Move GroupLab.app into your Applications folder and open it; the first time, macOS checks it with Apple and opens it.
GroupLab for iPhone and iPad is in a public beta through Apple's TestFlight. Install TestFlight from the App Store first, then open the invitation on the iPhone or iPad. Each new beta build arrives through TestFlight.
Not sure? Install TestFlight from the App Store first, then open the invitation on the iPhone or iPad.
grouplab-android-dev.apk
Nightly 222, built 2026-10-26 from commit c3bd808.
For testing GroupLab on Android until it is published on the Play Store. An arm64 phone or tablet with Android 10 or later and 4 GB of memory. After the first install it keeps itself on the newest nightly, and fixes reach you the same day they are made.
GroupLab's internal test on Google Play receives every nightly through Google Play, which updates your copy as it does any app. It is open by invitation: ask on the Discord, then opt in at the internal test's page.
Take either the Play copy or the APK, not both: remove one before installing the other. GroupLab Dev is different: it installs beside either.
Not sure? Take GroupLab Dev: it keeps itself on the newest build and installs beside the Play copy. The Play copy gets every nightly through Google Play, the plain APK keeps itself current as GroupLab Dev does, and GroupLab Dev installs beside either with no uninstall.
grouplab-android.apk
The same app under GroupLab's own name, signed, with a different key from the Google Play copy. It keeps itself on the newest nightly, as GroupLab Dev does. An APK from before nightly 177 has no updater, so install one newer plain APK by hand once; it keeps itself current after that.
In Brazil, Indonesia, Singapore and Thailand, certified Android phones have refused apps from outside Google Play since 30 September 2026 unless their developer has registered them with Google; GroupLab Dev and the plain APK were registered with Google on 7 October 2026; if a phone there still refuses one, ask on the Discord for the Google Play internal test instead. The rest of the world follows in 2027.
Android asks to scan an app installed from outside the Play Store, the first time you install it and when it updates. It is Google's own check, it takes a few seconds, and the scan is expected: let it finish, then carry on.
grouplab-linux-x64.tar.gz
Nightly 222, built 2026-10-26 from commit c3bd808.
Self-contained, built on Ubuntu, and tested on every change.
Honestly: it passed the tests, which is not the same as somebody having used it.
Not sure? What each device needs, under Everything else below, lists the oldest distributions it runs on.
The moving release on GitHub always carries the newest build under these names, so a link to one of them never goes stale. The Android files join it when their own build finishes, usually some minutes after the others; until then a phone is offered the newest earlier build that has an Android file. Nightly 222, built 2026-10-26 from commit c3bd808.
| File | What it is |
|---|---|
grouplab-setup-win-x64.exe | Windows, the installer |
grouplab-win-x64.zip | Windows, the zip |
grouplab-linux-x64.tar.gz | Linux, the tarball |
grouplab-macos-arm64.tar.gz | Mac with Apple silicon |
grouplab-macos-x64.tar.gz | Mac with an Intel processor, untested |
grouplab-android-dev.apk | Android, GroupLab Dev |
grouplab-android.apk | Android, the plain APK |
grouplab-android.aab | Android, the bundle Google Play takes |
update-manifest.json | what the updater in GroupLab reads, nothing to download by hand |
update-manifest-2.json | the same, for nightly 45 and after |
The same build with its number in every file name, and the notes it was published with: GroupLab 0.2.0-nightly.222 on GitHub. What changed in it: its release notes.
What each device needs, what is supported and tested, how updating works, and every file of the newest build.
The lowest each platform needs. The operating system floor is .NET 10's own support list, which nothing can go below; memory, disk and screen are GroupLab's measurements; nothing is listed for a platform that has no published build.
| Operating system | Built and published | Memory | Disk | Screen | |
|---|---|---|---|---|---|
| Windows | Windows 10 version 1607 or later; version 1809 or later for the Microsoft Store copy | x64 only; Arm64 and 32-bit x86 are not built | 4 GB, 8 GB recommended | 270 MB installed | a window about 1060 wide for the analysis screen |
| macOS | macOS 14 or later | Apple silicon and Intel | 4 GB, 8 GB recommended | 240 MB on Apple silicon, 270 MB on Intel | as Windows |
| Linux | Ubuntu 22.04, Debian 12, Fedora 42, RHEL 8 or later; glibc 2.27 or later | x64 only; Arm64 is not built | 4 GB, 8 GB recommended | 260 MB installed | as Windows |
| iPhone and iPad | iOS and iPadOS 26 or later; an iPhone 11 or newer | arm64, through TestFlight's public beta; not in the App Store yet | not measured yet | not measured yet | as Android |
| Android | Android 10 or later | arm64 only: an APK with every nightly, and Google Play's internal test by invitation | 4 GB | under 100 MB installed | 360 dp wide; a rear camera of 8 MP or more with autofocus |
Where the figures come from:
release-notes/10.0/supported-os.md). For Android, .NET lists
Android 14 and later as what Microsoft tests; GroupLab's minimum of Android 10 rests on GroupLab's own testing instead, because Android
14 and later is only about half the phones in use.Windows is the supported platform. It is where GroupLab is developed and tested by hand, and the installer and automatic updates are built for it.
Linux builds are published and are worth trying. The download is a self-contained 64-bit tarball, so it runs on most desktop distributions without anything else being installed alongside it. The test suite runs on Linux on every build. Hands-on testing has not started yet. Linux can be tested here on virtual machines under VMware Workstation, and there is no bare metal Linux machine, but the real reason is that the application is still under heavy development, with features, layouts, appearance and internal workings changing daily. Testing a moving target on a second platform would mostly produce findings that are obsolete a week later.
macOS builds are published, and the Apple silicon build has been run on two Macs. Two testers have run it. The first ran nightly 93 on a MacBook Pro with an M5 Max, under macOS 27, natively rather than under Rosetta. macOS blocked the first launch of that unsigned build, and a Terminal command cleared it; builds from nightly 135 on are signed and notarized by Apple. Opening, detecting and analyzing the published sample, saving a session, printing a target to PDF, quitting with Command Q and sending the diagnostics report all worked, and text was sharp on the Retina display. Command shortcuts such as Command Z did not work, and pinch zoom had not been built on any platform; both are fixed in builds after nightly 94, and neither fix has been checked on a Mac yet. The second ran nightly 190 on a Mac with Apple silicon, opened flatbed scans, marked holes with the Impact and Select tools, dropped several scans in at once and pooled sheets in Session records. The Intel build has never been run on a Mac. The tests run on macOS on every build. These builds are an experiment rather than a release. The updater does not install them, and the developer still does not own a Mac.
Other platforms get proper attention once the pace of change slows and the Windows application is generally working the way the developer wants it to.
Android is built and in testing, because that is the mobile platform in daily use here. Every nightly carries a signed APK, it runs on a Galaxy Z Fold 7 and a Galaxy Tab S8 Ultra, and Google Play's internal test is open by invitation, with a closed test to come. It photographs or opens a sheet in Guided or Manual mode and checks every picture, reads it with the same engine as the desktop, shows every figure the desktop does with a tap to say what each means, takes how you shot the sheet, works out Shots Needed to Zero, compares loads, gives the dope, the chance of a hit and Point blank, prints targets and keeps sessions; it also marks any target by hand, under a fixed crosshair. docs/PHONE-PARITY.md lists what the phone does, feature by feature. docs/ANDROID.md has the plan and what each stage found. Hands-on Linux testing follows, on virtual machines. More macOS testing depends on somebody with a Mac running the signed builds.
From nightly 135, the macOS build is signed with a Developer ID, notarized by Apple and stapled. Move GroupLab.app into your Applications folder and open it; the first time, macOS checks it with Apple and opens it.
Signing the Windows build needs a code signing certificate, which has not been bought, and Windows says "Windows protected your PC" about any program nobody has paid to sign. The Microsoft Store copy is signed through the Store and does not show that warning. Linux does not ask for a signature at all.
The macOS build is different: it is signed and notarized by Apple, using the Apple developer program the project joined to put GroupLab on iOS (Apple mobile, below). Running the macOS build, above, says what that means for opening it.
The one-off 25 dollar Google Play developer fee has been paid. A signed Windows version is in the Microsoft Store, and a code signing certificate for the direct downloads may be bought if the price turns out to be reasonable.
GroupLab for iPhone and iPad is in a public beta through TestFlight. It is tested on an iPad Mini, sixth generation, and built and signed on GitHub's Mac machines, because the developer still does not own a Mac and does not need one for this. Testers get it through TestFlight. It is not in the App Store yet; the plan is docs/IOS-PLAN.md.
The published Linux build is x86-64. Other targets can be added to the nightly builds on request: Arm64 for a Raspberry Pi or an Arm laptop, or a package built for a particular distribution rather than a tarball. Adding one is a line of configuration rather than a project. The reason a dozen are not published already is simply that nobody has asked for them.
Requests go to [email protected], naming the distribution and the architecture.
A report is useful even when the answer is that it crashed on startup. "It opened and the buttons are the wrong size" is a useful report, and so is a crash report: Report a problem in the settings, or Make a report on an error's banner, sends it from GroupLab when you press Send. The Discord's bug-reports forum works too, and [email protected] is for anything private.
The newest build is rebuilt automatically after every change that passes the tests on Windows, Linux and macOS, and published within minutes. It may be broken: passing the tests is not the same as somebody having used it. There is no full release yet.
Of the computer downloads, only the Windows installer updates itself. It asks first, then updates in the background.
The zip, the Linux tarball and both macOS builds tell you when a newer build exists and leave the downloading to you. There is no silent update on those platforms, and GroupLab will not pretend otherwise: it says so on the Settings screen rather than offering an update it cannot apply.
The Microsoft Store copy is updated by the Store, GroupLab Dev and the plain Android APK update themselves from every nightly, the Google Play copy is updated by Google Play, and TestFlight installs each new iPhone and iPad beta build.
%APPDATA%\GroupLab on Windows, and under your home folder elsewhere. An update check sends nothing about you.The moving release on GitHub always carries the newest build under these names, so a link to one of them never goes stale. The Android files join it when their own build finishes, usually some minutes after the others; until then a phone is offered the newest earlier build that has an Android file. Nightly 222, built 2026-10-26 from commit c3bd808.
| File | What it is |
|---|---|
grouplab-setup-win-x64.exe | Windows, the installer |
grouplab-win-x64.zip | Windows, the zip |
grouplab-linux-x64.tar.gz | Linux, the tarball |
grouplab-macos-arm64.tar.gz | Mac with Apple silicon |
grouplab-macos-x64.tar.gz | Mac with an Intel processor, untested |
grouplab-android-dev.apk | Android, GroupLab Dev |
grouplab-android.apk | Android, the plain APK |
grouplab-android.aab | Android, the bundle Google Play takes |
update-manifest.json | what the updater in GroupLab reads, nothing to download by hand |
update-manifest-2.json | the same, for nightly 45 and after |
The same build with its number in every file name, and the notes it was published with: GroupLab 0.2.0-nightly.222 on GitHub. What changed in it: its release notes.
Each of the newest thirty builds keeps a release of its own, so a bug report names something that still exists; older ones are removed with their tags, and their notes stay on the Release notes page. If something does not work, the Discord is somewhere to ask.
What changed in each build Every build on GitHub