Currently we expose about 5 or 6 live cycle methods as events in the application module. For advanced scenarios (like push notifications) the clients will need to get the rest of the notifications.

IMO apple choose a terribly poor API design here.

As a side note, if we are not comfortable exposing like 30+ events on the application we can implement a chain-of-command. This would involve exposing for iOS an "addDelegate" and "removeDelegate" pair in the application module that can be used to add an instance of client implementation of the UIApplicationDelegate in an internal list. Our own UIApplicationDelegate will delegate all its implementation to the members of the internal list of UIApplicationDeleages. This way if new interfaces appear in future we won't have to bother changing the public JavaScript API. Also the development of modules may be somewhat easier since the developers won't have to memory map methods to event names and event args to actual arguments.