3 ms·
It doesn't. For me, it works only if you have an OpenGL game and use a few of the native API. If you're building a UIKit app, it doesn't work at all: broken su
by funkaster 13y ago
It doesn't. For me, it works only if you have an OpenGL game and use a few of the native API.
If you're building a UIKit app, it doesn't work at all: broken support for almost everything.
To be fair, I think they are rewriting the UI layer, but after working almost two years in several cross-platform projects, I decided that for anything that's not a game (no custom UI), it makes no sense if you want your app to look "good" in all platforms. Just rewrite it (at least the UI layer).
- chrisdevereux 13y agoDid the Foundation-level stuff work ok for you? Did you try to use many third-party libraries? Being able to keep all the logic and networking stuff intact would be a big win when porting iOS -> Android even if the UI needs rewriting.
- zbowling 13y agoIt's one of the things we are working on by making the UIKit layer is optional. There is a library called BridgeKit that makes dealing with Java <->Objc easy without JNI so making code go back and forth is trivial. We are also building a version of the platform that even trims off Obj-C as a better NDK for C++ developers that want to target Android from Xcode.
- funkaster 13y agoYes, the foundation part is fairly complete. Like I said: if your game/logic is written in Obj-C and it's in OpenGL, it should be ok. If you have a lot of UIKit-intense parts (semi-complex xibs, anything related to Autolayout or Storyboards), then you might need to rewrite them. NOTE: my comments are based on what I experienced with a UIKit only app a few months ago.