Developing for Android with Objective-C and Apportable

When developing for iOS, you can take most any open source library and drop it into your application, and within a few minutes have something working. With Java Android development, this is of course more difficult. When you realize that the NDK isn’t nearly as supported as its Java counterpart—and that creating a rapid prototype, and transitioning into a releasable candidate takes considerably more time and effort—there’s been no easy road on Android.

Apportable was designed to do all of the heavy lifting that application developers do for any top-notch title on Android, and is designed for companies big and small. The basic idea of compiling native code for Android is not a new one, of course; the hard part is making it all work seamlessly.

Rolling Our Own

Cross-platform development can mean a few approaches. You can create an environment that defines a common API for both platforms; you can create a “lowest common denominator”-based solution; you can create a shared implementation backend and multiple frontends; or you can flat out re-write from scratch for each platform. 

Solutions like Unity require developers to re-write their app against Unity's API. We think that if you’re going to “buy in” to a given strategy, it might as well be one that you’ve already made a commitment to. And lets face it—iOS isn’t going anywhere. 

Freshly ground

Over 95% of our platform is not Java. We emit native machine code that’s executed directly on bare metal—no re-interpretation, no transliteration. Just raw, native power. We’ve even re-implemented the parts of Android’s native toolchain that we felt needed it.

Superpowering the Future

We’ve got a new build system that’s orders of magnitude faster at creating incremental builds. We’ve added features to conditionally link jars so that applications built with our SDK are smaller and leaner. 

Try out the SDK for yourself—for free—at