Not fully. MacOS applications are nothing more than _APP_NAME_.app directory with an internal structure and manifest files that denote it is an application so when double clicking on the directory Finder knows to run the actual application binary located with-in the directory. This allows for decoupling the resources from the binary. Had to place multiple 3rd party binaries here in case the end-user didn't have them installed and used them as a fallback.

Most 3rd party applications are actually an installer script that places the contents into /opt/_APP_NAME/ or where ever the end-user requests they be placed.

The closest I'm come to mimicking Mac style on Windows to create an installer that does not actual install but extracts the contents to user's temp directory and executes the application. Needed a simple solution so the end-user just had to download and double click to run the application since they might not have admin rights to install the application.

I actually prefer the MacOS style since installing and backing up applications or moving to a new computer is the same process.