Objective-C's delegate pattern isn't flexible and spreads out one particular concern into multiple areas. Here's a way to replace it using ReactiveCocoa.
The memory semantics in Objective-C are not available in RubyMotion, so extra care needs to be taken when dealing with lambdas and cyclical references.
I had an opportunity to truly leverage the power of ReactiveCocoa when I found myself facing a complex user interface that took a multitude of user inputs.
