QuartzControl 1.0.0-beta.1

The first public build. Beta: it runs, it is used daily by its author, and it has not been through
anyone else's hands yet. Feedback is welcome — an issue is the easiest way.

Which file

System	File
macOS, Apple Silicon	QuartzControl-1.0.0-beta.1-arm64.dmg — or .zip
macOS, Intel	QuartzControl-1.0.0-beta.1-x64.dmg — or .zip
Linux, x86_64	QuartzControl-1.0.0-beta.1-x86_64.AppImage or quartzcontrol_1.0.0-beta.1_amd64.deb
Linux, arm64	QuartzControl-1.0.0-beta.1-arm64.AppImage or quartzcontrol_1.0.0-beta.1_arm64.deb
Flatpak	QuartzControl-1.0.0-beta.1-x86_64.flatpak or …-aarch64.flatpak

Every file names its architecture, including the Intel and amd64 ones — no file here is ambiguous
about what it runs on.

Before the first start

macOS. The app is unsigned; there is no Developer ID certificate. Gatekeeper refuses the first
launch. Either open it once from the context menu (right-click → Open), or clear the quarantine
flag:

xattr -dr com.apple.quarantine /Applications/QuartzControl.app

Linux. Make the AppImage executable and run it, or install the deb with
sudo apt install ./quartzcontrol_1.0.0-beta.1_amd64.deb. For the Flatpak:

flatpak install --user QuartzControl-1.0.0-beta.1-x86_64.flatpak

--filesystem=home is set, so projects under your home directory work as they are. A content
folder on another drive needs a one-off flatpak override --filesystem=<path>.

What is inside every package

• Node and npm — Electron's own runtime, exposed as three shims on the PATH. Nothing to install.
• git 2.53.0 — used only when the machine has none that answers; otherwise the system's own wins.
• The user handbook — 453 files in two languages, readable offline, linked from every screen. In
  the Linux packages this is new: the builds from 2026-09-08 shipped without it.
• An example template — for creating a project when there is no network.

Known limits

• Unsigned on macOS, as above. Notarisation needs a certificate this project does not have yet.
• No self-update. The start screen reports when a newer version exists and links to it; the
  download and the replacement are yours to do. What updates inside the app is the Quartz core and
  the plugins of a project — that is the website, not the program.
• No Windows. Deliberate, and the reasons are in the README.
• On a machine without a working GL context — a VM, typically — the window appears through a
  fallback path a moment later than usual, and the console says so. The app works; the message is
  the app telling you which path it took.

How this was built

Three machines, because the Flatpak is the one target that cannot be cross-built: it needs the
runtime, SDK and BaseApp of its own architecture. macOS packages on a Mac, AppImage and deb for both
architectures in one pass on an x86_64 machine, and one Flatpak on a machine of each architecture.

Checksums (SHA-256)

a8d50854779cfe4624783e91ae989459d3927b1c15713f769170b7d02fcfea39  QuartzControl-1.0.0-beta.1-arm64.dmg
5135bba0ecb748efd58b267550a64592a6c50617a51bbaeb16cf85bec881fb2a  QuartzControl-1.0.0-beta.1-arm64.zip
f7e89fb712f4658cf9296648d3a561df87cea615232f73cf0176f20aec97ba83  QuartzControl-1.0.0-beta.1-x64.dmg
ce9a61dfef39d05f31cd97884701de294dd39b38d0059a9248ce914b86846f77  QuartzControl-1.0.0-beta.1-x64.zip
5b185dffc559a187f34c3e6d3b9f79dbd5a50c3c845f8877479bc9b11bfc253e  QuartzControl-1.0.0-beta.1-arm64.AppImage
5b3e8a4f42ba03feef4c53f9d0b28f7cba7d53dcc5a8bae17ae6e23bab5e84f8  QuartzControl-1.0.0-beta.1-x86_64.AppImage
1ae628e0569b65aad6f9c84bbe4dad8b46103787cc0bf8afe001a990b33498f4  quartzcontrol_1.0.0-beta.1_arm64.deb
65ffc54003e5ceda7d07655ed090e0fb5b87b10c34ae130d399b5bf1d1b0eabb  quartzcontrol_1.0.0-beta.1_amd64.deb
8687792c16b867ca8266d2ab2d0798a0ad0d47696054e4fdd41695dd8c0e2ee2  QuartzControl-1.0.0-beta.1-aarch64.flatpak
1fb843316cc646688f690b65b72cdef7b179d39808664b1e38463119b65342a5  QuartzControl-1.0.0-beta.1-x86_64.flatpak