[cwizou]

To be fair, this is a long standing issue between how Apple wants people to uninstall their app (by throwing them in the trash) and how modern apps really work in practice (some apps need/generate temp data in AppSupport, and sometimes it's a non trivial amount).

As a developer the best you can usually do is put some instructions somewhere (website, somewhere in a menu in UI), or do a package install that puts an uninstaller somewhere (more of the Windows way, but it breaks many expectations from users like having your app be one icon in `Applications`, and not it's own folder with your app and maybe a "Uninstall" app there too). For Aerial I give uninstall instructions on the website, but there's not much of a standard on how to handle this (that I know of, at least).

[Angostura]

Not quite sure why this couldn't sit in the Application bundle itself.

[cwizou]

As far as I understand this is downloaded data and they may offer model selection later on? If so they have little choice and putting your data in the user `/Library/Application Support` (or maybe `/Library/Caches` but that's a mess in itself) is what you're supposed to do.

With the various security changes in "recent" macOS, you can't modify your bundle and download files inside it, as it would change its signature and break the notarisation system.

[remram]

Do you mean that it should be distributed with it, or that it should write it in there when it downloads it at runtime?

[Angostura]

The latter. A model update would then just be an application update. To answer my own question - if they want to allow a choice of downloadable models, then Application Support is the perfect place.

[Reason077]

And also to allow updating the app independently of the model, without a 4GB download every time.