> In contrast, Apple only follows the convention that a package's assets should be in /Applications/AppName.app... but apps are completely free to ignore that a

> In contrast, Apple only follows the convention that a package's assets should be in /Applications/AppName.app... but apps are completely free to ignore that and install to anywhere If you can't install a normal Mac app via drag and drop, I'm not installing it. It's a great signal that you're dealing with an inexperienced Mac developer. I absolutely refused to install Chrome for Mac, for instance, until they rewrote it to install via normal drag and drop after their custom installer/update workflow rendered computers unbootable. > A wave of reported Macs being no longer able to boot was caused by a recent Google Chrome update that was corrupting a necessary operating system folder. Once the update was installed, affected users found they were no longer able to boot into macOS. https://www.bleepingcomputer.com/news/security/buggy-google-chrome-update-behind-recent-unbootable-macs/ https://www.bleepingcomputer.com/news/security/buggy-google-...