Microsoft Store package
The Microsoft Store is a second way to install Keymotion, beside the installer on GitHub. Microsoft signs every package it publishes, so Windows trusts the Store copy without a warning. The program is the same in both: the Store package holds the keymotion.exe that tauri build makes, and nothing in the GitHub release changes.
What the Store build does differently
Section titled “What the Store build does differently”The app tells the two apart while it runs, by the package identity Windows gives a program installed from an MSIX (crates/kb-winsys/src/package.rs, app/src-tauri/src/channel.rs). Only a package that holds the running keymotion.exe counts, so a development build started from another packaged app never takes that app’s package for its own.
| GitHub (installer, development build) | Microsoft Store | |
|---|---|---|
| Updates | The app’s updater, from GitHub releases: Settings › About › Updates chooses update automatically, let me know or off | The Store. The updater stays off; Settings › About opens the Store’s updates page. The app registers with RegisterApplicationRestart, so it opens again, hidden, after Windows closes it to install a Store update. |
| Notification buttons | Open the app’s own keymotion: addresses (crates/kb-winsys/src/protocol.rs), registered per user at start and removed by the uninstaller |
No keymotion: address; a click starts the app the package’s way |
| Start with Windows | A value in the per-user Run key, with --hidden |
The package’s startup task (KeymotionStartup), also with --hidden. If the user turns it off in Windows’ settings, only they can turn it on again there; Settings › Background then links to that page. |
| Notification name and logo | Registered at start under the app id dev.keymotion |
The package’s own |
| Data folders | %APPDATA%\dev.keymotion, %LOCALAPPDATA%\dev.keymotion |
The same paths, as the app sees them. Where the folders were not there before, Windows keeps them in the package’s own folder (%LOCALAPPDATA%\Packages\<package family>\LocalCache\…) and removes them with the app; “Open folder” opens that folder. |
| Privacy text in Settings | Mentions the update check on GitHub | Says the Store brings updates |
Both builds share one rule: only one Keymotion runs at a time, whichever way it was installed, since two would talk to the keyboard at once.
If Keymotion from GitHub was installed before, its folders are already there, and the Store build reads and writes them as they are: the settings carry over, and both builds share them. Windows moves only folders a package makes from nothing into the package’s own place.
Both installed
Section titled “Both installed”Left alone, both copies would start with Windows and whichever came first would run: one day the GitHub copy its updater raised, the next day the Store’s. So the GitHub copy steps aside once the Store copy is installed (app/src-tauri/src/handoff.rs), as Microsoft advises for moving users to a Store-packaged app:
- When the installed GitHub copy starts (the program in the folder its installer recorded, never a development or repository build), it looks for the Store package (
GetPackagesByPackageFamily). If it is there, it starts the Store copy withIApplicationActivationManagerand ends. - If the GitHub copy was set to start with Windows, it removes its
Runvalue and passes--take-startup: the Store copy turns its startup task on, unless the user or a policy turned it off. - A start with Windows that finds a copy already running ends quietly, and a second launch with
--hiddendoes not bring the window forward. - The Store copy’s Settings › About shows a “GitHub copy” row while the GitHub copy is installed, with a button to Windows’ Installed apps, where the user can remove it. The settings stay, as both copies share them, unless Also delete my settings and saved data is ticked in the uninstaller.
GitHub copies older than this change (1.0.0) do not step aside; their next update brings it.
The package
Section titled “The package”| File | What it is |
|---|---|
app/src-tauri/store/AppxManifest.xml |
The package manifest, with places for the identity and the version. Full trust (runFullTrust): the program runs with the user’s normal rights, as it does from the installer, which HID, the gauges and the tray need. |
app/src-tauri/store/Assets/ |
The logos in every size Windows asks for, drawn from app/src-tauri/icons/icon.png by tools/store/make-assets.py. Run it again when the icon changes. |
tools/store/msix.mjs |
Fills the manifest, indexes the logos (makepri) and packs the MSIX (makeappx). Needs the Windows SDK. Tests: node --test "tools/store/*.test.mjs". |
.github/workflows/store.yml |
Builds the package of a released version. |
The package is not signed: the Store signs what passes certification. CI packs a test package on every change, so a manifest or logo Windows’ tools would refuse shows up before a release.
Version numbers
Section titled “Version numbers”There is one version number and one changelog for both channels. A Store package has four version parts: the fourth belongs to the Store and is always 0, and the first must be above 0. Keymotion 1.2.3 becomes package 1.2.3.0, and that is the only difference users see (in Windows’ list of installed apps).
msix.mjstakes the version fromtauri.conf.json.--versionworks only for test packages, so a Store package can never carry another number than the GitHub release of the same code.store.ymlpacks only a release tag that is onmain, so the Store never gets a version that isn’t on GitHub.- The Store has no room for test versions (
1.3.0-rc.1): they stay on GitHub. - Both channels publish a version the same day: the GitHub release waits as a draft until the Store’s copy passes certification (see Making a release). The release notes describe both; a change that concerns only one channel says so.
- A number the Store has received is never used again: if the Store turns down a package, the fix comes as the next patch version in both channels.
- Diagnostics and support requests show where the copy came from:
App version: 1.0.0 (Microsoft Store),(GitHub)or(development build).
Try the package on your computer
Section titled “Try the package on your computer”A package with a made-up identity (“Keymotion (test)”) installs without a certificate when Windows’ developer mode is on (Settings › System › For developers). It never mixes with the Store’s package.
-
Build the program and pack it:
Terminal window pnpm --dir app tauri build --no-bundlenode tools/store/msix.mjs --exe target/release/keymotion.exe --out target/store-test --test -
Quit Keymotion if it is running (tray icon › Quit), then install the package from its folder, in PowerShell:
Terminal window Add-AppxPackage -Register target\store-test\layout\AppxManifest.xml -
Open Keymotion (test) from the Start menu.
-
Remove it when you are done. This also removes the files it created:
Terminal window Get-AppxPackage Keymotion.StoreTest | Remove-AppxPackage
Making a release
Section titled “Making a release”A version comes out on GitHub and in the Microsoft Store the same day, so that a number is either everywhere or nowhere (owner’s decision, 2026-11-16).
-
Tag the version on
mainas usual.release.ymlbuilds the installer and drafts the GitHub release; its Microsoft Store package job (store.yml) builds the.msixfrom the same tag and keeps it as the run’s artifact. Pre-releases skip that job. -
Leave the GitHub draft unpublished. In Partner Center, start a new submission for Keymotion: under Packages, upload the
.msixand remove the previous one; fill in “What’s new” from the changelog; under Submission options, choose “Don’t publish this submission until I select Publish now”. Submit it. -
When it passes certification (Microsoft allows up to three working days), publish the GitHub draft and select Publish now in Partner Center, together.
- The Store turns down the package. Fix it in the next patch version and release that in both channels. The turned-down number is published nowhere; its changelog section moves to the new number. A rejection about the listing only (text, screenshots) needs no new package.
- An urgent fix (a crash, a security problem) may be published on GitHub first; its release notes say the Store follows.
- The Store job can also be run by hand: GitHub › Actions › Microsoft Store package, with the release tag (
v1.2.3).
The workflow needs three repository variables, copied exactly from Partner Center › Keymotion › Product identity: STORE_IDENTITY_NAME, STORE_PUBLISHER and STORE_PUBLISHER_DISPLAY_NAME. They are not secrets; every package shows them.
Submitting from the workflow (Microsoft’s msstore tool) is possible once the app is live, but it needs a Microsoft Entra app registration with access to the Partner Center account. An individual developer account can create or associate a Microsoft Entra tenant for it (Partner Center › Account settings › Tenants). Setting that up is still an open topic, so the upload is done by hand for now.