First, a “bit verbose?” Just a bit? Cairngorm introduces monstrous boilerplate into the application — not just a bit.

Second, the Singleton model is not an ideal pattern. For every component that references the Singleton, that code is no longer reusable wither (A) outside of the app (B) or within the app when the singleton reference is not desired.

Third, Mate has the Command pattern, it’s the MethodInvoker. In fact, it’s better because you can name the methods, so you can group them better than one-class-per-Command.

Fourth, the Delegate pattern can be used freely in Mate, too. It’s not part of Cairngorm.

Fifth, the Event Maps can be separated into multiple MXML, reducing bloat. In fact, you can make local event maps that encapsulate a subset of your functionality (by module, view, etc.)