We looked into adding Fiji, but unfortunately we can’t support it in App Catalog. The main reasons:
Not a self-contained app.Fiji.app is just a small launcher that depends on many folders next to it (a bundled Java runtime, jars, plugins, scripts, etc.). It doesn’t work on its own, so it can’t be deployed like a regular app.
No usable version number. The app reports the launcher version ( e.g. 2.0.2), not the actual Fiji version. New builds are published several times a month without version numbers, so we can’t reliably tell whether a Mac is up to date.
Built-in updater. Fiji updates its own files and plugins, and users often add their own update sites and plugins. A managed deployment would conflict with this and could remove user-installed plugins.
We recommend letting users install Fiji themselves (e.g. in ~/Applications), so the built-in updater can keep it up to date.
Log in to comment and vote
Comments2
Vincent
Oct 30
Thanks for the request!
We looked into adding Fiji, but unfortunately we can’t support it in App Catalog. The main reasons:
Not a self-contained app.
Fiji.appis just a small launcher that depends on many folders next to it (a bundled Java runtime, jars, plugins, scripts, etc.). It doesn’t work on its own, so it can’t be deployed like a regular app.No usable version number. The app reports the launcher version ( e.g.
2.0.2), not the actual Fiji version. New builds are published several times a month without version numbers, so we can’t reliably tell whether a Mac is up to date.Built-in updater. Fiji updates its own files and plugins, and users often add their own update sites and plugins. A managed deployment would conflict with this and could remove user-installed plugins.
We recommend letting users install Fiji themselves (e.g. in
~/Applications), so the built-in updater can keep it up to date.John Moore
Oct 30
No worries, thanks for checking.