Thanks for the answer. Sorry I wasn't clear... I was referring to this part of the article, in which you describe how the HTML / JavaScript communicates with Objective C on the iPhone:
>> We then make a request to a fake URI (forge://…) which we intercept in native code
Have you tried doing the same for Android? Do you have any numbers that compare the performance of this method with the JS -> Java bridge?
Ok, that makes sense, the JS -> Java communication in Android is already very fast as it is something that can be done as part of the WebView. The fake URI request is a workaround on iOS as this feature doesn't exist. I don't have any numbers offhand, but the JS -> Java communication is definitely a very quick part of the bridge.
>> We then make a request to a fake URI (forge://…) which we intercept in native code
Have you tried doing the same for Android? Do you have any numbers that compare the performance of this method with the JS -> Java bridge?