macOS · Apple silicon
Macs with an M-series chip.
Disk image (.dmg)
Desktop client
The same Mirket LMS, in a window of its own
All enabled roles use Mirket LMS in the browser. Students and instructors can also use a published optional desktop build connected to their organization’s installation. Android is planned for the first production release but is not currently downloadable. iOS publication is undecided; no iOS app is available to download.
BrowserDesktop releases
Browser first. Desktop when published.
Check actual release availability below. Mobile apps are not currently downloadable.
Recommended for this computer
Checking which build fits this computer
Desktop client
All builds
Choose your operating system and processor. Published builds show their version, file size and download link.
macOS · Intel
Macs with an Intel processor.
Disk image (.dmg)
Windows · 64-bit
Almost every Windows PC.
Installer (.exe)
Windows · ARM
Windows on ARM, such as Copilot+ PCs.
Installer (.exe)
Desktop client
Before you install
- An installation to connect to
- The client is a shell, not a service. It needs the web address of the Mirket installation your organization runs — your administrator has it. There is no Mirket account to create and nothing to sign up for here.
- macOS 13 or later, or Windows 10 or later
- On a Mac, Apple silicon and Intel are separate downloads. On Windows, so are 64-bit and ARM. If you are unsure, the recommended build above is chosen from what your browser reports.
Desktop client
What the client adds
The optional desktop app opens the same Student and Instructor web interfaces and adds these four operating-system capabilities.
- Screen sharing that lists your windows
- Presenting in a live session opens the client’s own picker of screens and windows, instead of the browser dialog that leads with a list of tabs.
- Notifications while the windows are closed
- The client asks your installation how many notifications are unread and tells you the count. It never puts a message title or a sender on your lock screen.
- It still opens when the server does not
- After the first connection the client keeps a copy of the interface. On a dropped network it opens and says it cannot reach your installation, rather than failing like a browser tab. Course data is never served from that copy — stale course work read as current is worse than none.
- Updates come from your organization
- The client asks the installation you connect to whether a newer version is published, and never contacts Mirket to do it. An installation with no route to the internet keeps working.
Desktop client
Opening it the first time
These builds are not yet signed with a developer certificate, so both systems stop the first launch and ask you to confirm. Each asks once. Signed builds are coming, and this step disappears with them.
- macOS
- Open the disk image and drag Mirket to Applications. The first launch is refused with a message saying macOS cannot verify the developer. Open System Settings, go to Privacy & Security, scroll to the note about Mirket, and choose Open Anyway.
- Windows
- Run the installer. SmartScreen shows “Windows protected your PC” because it does not recognize the publisher yet. Choose More info, then Run anyway.
Desktop client
Where updates come from
This page is where a person downloads the client the first time. After that the client checks your own installation, not this site. That keeps a client on an isolated network working exactly like one with internet access, and it means your client version tracks the installation it belongs to.
No installation to connect to yet?
The client connects to your organization’s Mirket LMS installation. If you do not have one yet, schedule a demonstration to explore the product and discuss deployment.