On some other systems, such as Microsoft Windows, these resources are usually included directly in the executable file itself at compile time.
On older Macintoshes, a similar technique is used, where additional metadata can be added to a file's resource fork.
Similar in concept are the application directories used in RISC OS and on the ROX Desktop.
[3] Among other things, the Resources folder contains localized versions of the application's nib files.
By default, the Finder displays application bundles, which can also be referred to as packages, as opaque files with no underlying structure; the contents of the bundle can be shown with the "Show Package Contents" context menu item.
An alternative is to name them by the computer architecture and OS the code is intended for to form a fat binary, so the application can be opened on many platforms.
By default, the Finder displays loadable bundles, which can also be referred to as packages, as opaque files with no underlying structure; the contents of the bundle can be shown with the "Show Package Contents" context menu item.
There are many macOS applications which utilize their own custom bundle format (e.g. CandyBar .iContainer, Aperture .aplibrary, VMware Fusion .vmwarevm, etc.).