Swizzling? Why not just override the event method in a class derived from UIApplication? That's what I do if I want to see all user events, works just fine.
Which is fine if you're adding automatic event-tracking directly to your own app. But for a third-party library (like our own), it exacerbates the integration process. Method swizzling allows for a purely drop-in solution.
For example, you lost me. Having stumbled on it, I couldn't bring myself to finish the piece. I actually do need an analytics solution for our iOS app, but this blog post just fell into "I will read it later" category, out of "I will read it now".
Noted, though, that we lost you with the piece's verbosity.