What exactly is Application Enhancer? It is a combination of a Framework (a collection of commonly used code that can be re-used across different Application Enhancer modules) and a system daemon (faceless background application). Application Enhancer performs its task by loading plugins (Application Enhancer modules, or APE's for short) containing executable code into the running applications. Once loaded, the APE module performs the needed modifications (such as redefining the minimize window action, or customizing the standard Apple menu) on the launched application memory space, never touching any files on disk, utilizing set of functions defined in the Application Enhancer framework. To help the APE modules to be loaded into newly launched applications, the Application Enhancer daemon (aped) is used.

Can Application Enhancer or its modules crash your system? Due to the nature of the method, Application Enhancer or its modules potentially can crash individual applications if there is a bug in the module or in the application being modified (sometimes APE modules expose "hidden" bugs in the applications).

If you suspect Application Enhancer or its modules cause crashes, you can always temporarily disable the Application Enhancer system.

There are a number of technologies incorporated into our products that attempt to make sure your applications are safe: Haxie CrashGuard makes sure the application is not modified if it has recently crashed; APE Check makes sure no damaged APE modules are loaded; moreover, all of our products are going through a tedious beta testing process to make sure it runs as expected.

However, even if an individual application crashes, this cannot bring down the whole system due to the fact it has the protected memory and the Application Enhancer operates in user memory space, which means it cannot affect the system itself or processes belonging to other users (in this regard, Kernel Extensions (kext) are much more dangerous as they operate on the lowest possible level and have access to all memory and processes; because of that, Kernel Extensions can cause "kernel panics", while Application Enhancer cannot, as they don't have access to the kernel memory space).

Does Application Enhancer slow down the system? Due to the fact that more code has to be loaded at the application launch time, Application Enhancer can increase the application launch time (usually in the range of 40-60 ms per Application Enhancer module loaded on a modern Mac). Once loaded, most Application Enhancer modules stay latent and will not hog your processor. We are constantly working on improving the situation, so please make sure you always run the latest versions of our products.

The technology behind Application Enhancer system has been in research and development for more than 2 years now, and many of our products are using it.


- Provides capabilities to use Application Enhancer modules.
- Completely free of charge.

What's New:

* You may have to restart after installing.
* Updated to support Mac OS X 10.6 Snow Leopard v10.6.x
* Now supports only Mac OS X 10.5 Leopard v10.5.8 and Mac OS X 10.6 Snow Leopard v10.6.x
* Adds support for 64-bit processes (x86_64 only, ppc64 is not support)
* Supports architectures ppc, i386, and x86_64 on Mac OS X 10.5 Leopard v10.5.8 and Mac OS X 10.6 Snow Leopard v10.6.x
* Dropped support for Mac OS X 10.4.x
* Addresses an if statement that did nothing.
* Compiled with Clang/LLVM and GCC-LLVM.
* Analyzed with the clang static analyzer.
* Only APE Modules with all three architectures (ppc, i386, and x86_64) will load on Mac OS X 10.6 Snow Leopard v10.6.x
* Will not work with G3s again.