# Desktop releases now carry their own update path.

Canonical URL: https://www.iagenify.com/news/iagenify-desktop-updates-follow-the-release

IaGenify Desktop is built as an installable workspace with architecture-specific releases and an in-app route for checking, downloading and applying updates.

## Key points
- The desktop app checks a release feed for the build architecture it is running on.
- People can check for an update in the app, review its version and download it before installing.
- Release preparation now stages Windows x64, ARM64 and 32-bit installers with matching update manifests.

A desktop application is not finished when the first installer is uploaded. People need a dependable way to discover a later version from the app they already installed, and the release process needs to publish the right package for each supported machine. IaGenify Desktop now treats those as part of the product rather than a separate manual step.

## The app checks the feed for its own architecture

At startup, a packaged app checks the update feed associated with its platform architecture. The updater can report that a version is available, show download progress, and tell the app when the package is ready to install. This lets an existing installation find a compatible build without asking its user to search the downloads page first.

## An update is visible and user controlled

The app exposes a manual check as well as its automatic check. When a newer release exists, the interface can show the version and progress; when the app is current, the routine update notice stays out of the way. Downloads do not silently replace an open workspace: the user can see when an update is ready, and installation occurs as the app closes.

## Three Windows architectures, one release routine

The release preparation script builds and stages x64, ARM64 and 32-bit Windows packages. Each architecture's installer is placed beside the manifest and block map that its updater expects. Keeping those files together reduces the chance that the download page advertises a version whose in-app update feed is still pointing at an older build.

The release page and updater still serve different jobs: the page is the direct install route, while the manifest lets an installed copy discover a compatible release. Publishing both from the same versioned build makes them easier to keep aligned.

> A release is complete when both a new user and an existing installation have a clear path to it.

That is the practical change: IaGenify Desktop's update experience is now part of its release contract. Future releases can follow the same architecture-aware path, so improvements reach people who already use the app as well as those installing it for the first time.

## FAQ
### Does the desktop app install an update without telling me?
No. It can check automatically and prepare a download, then shows when an update is ready; installation is applied when the app quits.

### Can I check manually?
Yes. The app exposes a check-for-updates action.

### Which Windows architectures are prepared?
The release routine stages x64, ARM64 and 32-bit Windows packages with matching updater metadata.

### Do I have to use the downloads page?
No. The downloads page remains available for direct installation, while the in-app updater can find a compatible release.