Hello Radu,

the main new feature of version 3.0.1 is support for WebSocket, but it also adds numerous minor improvements and fixes, compared to version 2.x. Moreover, as you already know, compared with 1.x it adopts the "Unified API" model: a common API shared by clients of all major platforms (in particular Java/Android and JavaScript/Web).

Regarding J2ObjC, iOS Client 3.0.1 uses version 2.0.3 of J2ObjC. Anyway, theoretically, it should not interfere with your app, since the iOS Client is packaged as a framework (not a static library). We haven't tried it, so let us know if any issue should arise.

At the moment we don't have a version of the iOS Client that supports both the Unified API and doesn't use J2ObjC. The latest version that doesn't use J2ObjC is 1.4.5, as you noted.

Trans-compiling the source code of the Java client on your own is discouraged. We make heavy use of dependency injection to add features like native network transport, WebSocket support, network status monitoring, etc. Bare transpilation can only provide an incomplete and underperforming product.

Hope this helps. Let us know if you need further information.
Best regards,

Gianluca