We keep trying to get rid of those android and ios references on the
easyrtc.com page, but they keep coming back somehow. it's very aggravating. I've just asked our web guy to kill them.
At one point, we were going to licence some native api's, but when we analysed how much we could charge versus how much it would cost us to support them, it was a money losing proposition, so we gave it up as a product.
If you want to build build some api's and license them yourself, I suggest start with
https://github.com/pristineio/webrtc-build-scripts. From there, it's a matter of porting the easyrtc.js clientside to Java or Objective C. Unless you've got some experienced android or ios developers with C++ background, I wouldn't suggest going down that path. The languages are easy, the development ecosystem can have a steep learning curve, in particular ferreting out memory leaks on the iOS side (multihreaded code in multiple languages and multiple memory management schemes).
I'm not aware of anybody who has developed easyrtc native libraries that is licensing them.