Flurry: Created page with "If you've used macOS/MacOSX and never poked around the structure of an App, I have some mind-blowing information for you: it's just a folder. A folder with more folders, in fact! == How macOS Apps Work == The basic structure of a macOS app is a-like so: - MyCool.app/ + Contents/ + Info.plist + MacOS/ + CoolApp + Resources/ + AppIcon.icns + SomeOtherJunk.txt This isn't just specific to a..."

2023-04-17T05:10:08Z

Created page with "If you've used macOS/MacOSX and never poked around the structure of an App, I have some mind-blowing information for you: it's just a folder. A folder with more folders, in fact! == How macOS Apps Work == The basic structure of a macOS app is a-like so: <syntaxhighlight lang="text"> - MyCool.app/ + Contents/ + Info.plist + MacOS/ + CoolApp + Resources/ + AppIcon.icns + SomeOtherJunk.txt </syntaxhighlight> This isn't just specific to a..."

New page

If you've used macOS/MacOSX and never poked around the structure of an App, I have some mind-blowing information for you: it's just a folder. A folder with more folders, in fact!

== How macOS Apps Work ==

The basic structure of a macOS app is a-like so:

<syntaxhighlight lang="text">
- MyCool.app/
+ Contents/
+ Info.plist
+ MacOS/
+ CoolApp
+ Resources/
+ AppIcon.icns
+ SomeOtherJunk.txt
</syntaxhighlight>

This isn't just specific to applications! Kernel extensions, some plugins, and frameworks also follow this "actually a directory" format. These are called Bundles.<ref>[https://developer.apple.com/library/archive/documentation/CoreFoundation/Conceptual/CFBundles/AboutBundles/AboutBundles.html ''About Bundles''], from the Bundle Programming Guide by Apple.</ref>

== Components of an App Bundle ==

=== Info.plist ===

The core component to a bundle is its <code>Info.plist</code>. All usable keys are provided in Apple Developer docs<ref>[https://developer.apple.com/documentation/bundleresources/information_property_list/bundle_configuration ''Bundle configuration''], from Apple Developer Documentation.</ref>, but these should get you started:

<syntaxhighlight lang="xml">
<?xml version="1.0" encoding="UTF-8">
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>CFBundleIdentifier</key>
<string>xyz.datagirl.cool-app</string>

<key>CFBundleInfoDictionaryVersion</key>
<string>6.0</string>

<key>CFBundleName</key>
<string>CoolApp</string>
<key>CFBundleVersion</key>
<string>1.0.69</string>

<key>CFBundleIconFile</key>
<string>AppIcon.icns</string>
<key>CFBundleIconName</key>
<string>AppIcon</string>

<key>CFBundleExecutable</key>
<string>CoolApp</string>

<key>CFBundlePackageType</key>
<string>APPL</string>

<key>NSHighResolutionCapable</key>
<true/>
</dict>
</plist>
</syntaxhighlight>

=== The program itself ===

Make a program named the same as what you set <code>CFBundleExecutable</code> to in your Info.plist. This can be a macOS binary, or interpreted code, such as a shell script. You'll need to make sure it's executable, of course. Save it to the <code>Contents/MacOS</code> directory in your app.

=== App Icon ===

Generating an ICNS file is an exercise left to the reader.<ref>But [https://gist.github.com/jamieweavis/b4c394607641e1280d447deed5fc85fc this gist] worked well for me.</ref> Once you have it, save it with the same name you set as <code>CFBundleIconFile</code> in the <code>Contents/Resources</code> directory in your app.

== Notes ==
<references />

Make Anything Into an App on macOS - Revision history