MAD Designer iconMAD

MAD Designer for Windows iconMAD Designer for Windows

MAD Designer for Windows is a native Windows Presentation Foundation (WPF) desktop application on .NET 10 for creating, querying, laying out, refreshing, and exporting Mobile Analytics Documents (.mad). It runs the same first-party Objective-C engine (mad.exe) as the macOS application and the headless Linux mad CLI, so every document it writes is compatible with the iPad/iPhone apps, the mad CLI, and the mad-action GitHub Action.

This 0.7 build is unsigned. It is built and published from the public source, but it carries no commercial code-signing certificate, so Windows SmartScreen will warn on first launch. Nothing is hidden: review the build, verify its SHA-256 checksum, and run it.

Download & Install

  1. Download the .zip and extract it to a folder of your choosing. Keep the folder structure intact: the application, the engine, and the licences belong together.
  2. Run Mad.Designer.Windows.exe from the top of the extracted folder.
  3. On first launch, Windows SmartScreen may say “Windows protected your PC”. Choose More info, then Run anyway — the build is unsigned by design (see below).

What is in the archive

MAD-Designer-Windows-0.7/
  Mad.Designer.Windows.exe   the WPF application (self-contained)
  ...                        the application's own files
  CLI/Fixtures/              London.portable.mad (a sample report) and
                             chinook.sqlite3 (the sample data it refreshes from)
  Windows/Engine/build/mad.exe       the headless engine
  Windows/Engine/build/*.dll         the engine's GNUstep/ObjC/VC runtime
  Windows/Engine/build/fonts/        the Liberation fonts used by PDF export
  ThirdParty/Licenses/       every third-party licence and notice
  LICENSE, NOTICE, README-Windows.txt

Where the engine sits: Windows/Engine/build/mad.exe, next to its runtime DLLs and fonts folder. The application finds it through the same repository-relative layout the source tree uses; it does not use a system-wide GNUstep install. Leave the folders where the archive put them.

Verifying the download

The release page publishes a SHA-256 checksum for the archive. Compare it after downloading:

Get-FileHash .\MAD-Designer-Windows-0.7.zip -Algorithm SHA256

The extraction can also be reviewed file by file: the archive contains only the published application, the engine built by Windows/Engine/build.ps1, the sample document, and the licence texts. mad.exe is the same command-line engine documented in the Linux guide and the Windows build record.

Reviewing and self-signing this build

You can run mad.exe directly to inspect a document without opening the GUI:

.\Windows\Engine\build\mad.exe inspect .\CLI\Fixtures\London.portable.mad

If you want Windows to stop warning about your own copy, create a local code-signing certificate and sign the executable yourself. This is a local trust decision — it does not make the public download trusted by anyone else:

$cert = New-SelfSignedCertificate -Type CodeSigningCert `
    -Subject "CN=MAD Designer (local review)" `
    -CertStoreLocation Cert:\CurrentUser\My
Set-AuthenticodeSignature -FilePath .\Mad.Designer.Windows.exe -Certificate $cert

To trust that certificate on this machine, export it and import it into Trusted Root Certification Authorities with certmgr.msc or Import-Certificate; only do that for a certificate you created and control.

Workspaces

The application has the same three reporting stages as the macOS app:

The Viewer exports PDF, HTML, HTML Flow, CSV, JSON, JSON Full Report, and Plain Text, in the macOS viewer’s order. The PDF is written by the engine itself (the same exporter mad export --format pdf uses), so a large report exports without blocking the window: the status bar shows an indeterminate progress bar and an “Exporting…” line until the file is written, then reports its size.

Building from Source

The application builds with the .NET SDK pinned in Windows/global.json (10.0.404):

dotnet publish Windows\App\Mad.Designer.Windows\Mad.Designer.Windows.csproj `
    -c Release -r win-x64 --self-contained true

The engine is the harder half. Windows\Engine\build.ps1 reproduces the native build (Clang 20.1.8, the pinned Visual Studio MSVC toolchain, NASM, Strawberry Perl, Meson, Python, and GNUstep built from seven pinned revisions into C:\GNUstep). It must run from an elevated PowerShell prompt:

pwsh -File .\Windows\Engine\build.ps1                 # full toolchain bootstrap and build
pwsh -File .\Windows\Engine\build.ps1 -SkipToolchain  # rebuild after the toolchain exists

The two .NET suites run against the built engine:

dotnet test Windows\App\Mad.Designer.Windows.slnx

Windows/Engine/build.ps1 also runs the ported native suites, and Windows/package.ps1 assembles the unsigned release archive and the engine-only CI asset once the engine and app are built. The full recipe, the Windows-only runtime fixes, the licence obligations, and the supported OS matrix are recorded in docs/project/MAD_WINDOWS.md.

Licence

MAD is MIT-licensed (see LICENSE); the names “MAD”, “MAD Designer” and “MAD Viewer” and the app artwork are excluded (see NOTICE). The engine adds the GNUstep runtime (LGPL-2.1-or-later) and the C libraries; every component, its licence, and the written relink offer are in the archive’s ThirdParty/Licenses/ folder and in docs/project/THIRD_PARTY_LICENSES.md.