I used this tool 2-3 years ago (back when it was still hosted on Google Code!). It does what it says on the box (converts code from Java to Obj-C) - the problem

I used this tool 2-3 years ago (back when it was still hosted on Google Code!). It does what it says on the box (converts code from Java to Obj-C) - the problem is all about expectations. In a way, this being an "official" tool from Google makes it more confusing for non-technical folks. When you read that Google has released a tool for converting Java to Obj-C, many assume it's now trivial to get an Android app converted to iOS. This tool will not translate an Android app into iOS code. It won't really even help that much unless you've made a deliberate effort to isolate code so that a conversion could happen. Most of the time, the business logic for mobile apps is fairly simple so you aren't saving much time. In my experience, the difficulty in shipping cross platform mobile apps is dealing with platform specific conventions (e.g. what is the iOS equivalent of a Fragment?) and libraries (RestKit on iOS, Retrofit on Android, etc); not the conversion of basic Java class into their Obj-C equivalents.