The Google Play store will accept multiple build types and will deliver the correct builds to the correct phones automatically, no need for a fat binary. While

The Google Play store will accept multiple build types and will deliver the correct builds to the correct phones automatically, no need for a fat binary. While NativeActivity is interesting, for LOB apps we're much more likely to stick to native Android UI components, which means Android/Java activities. However, Loaders might then in turn use JNI as a model layer. I'm still working out the details myself, but I feel there should be a way for shared, cross-platform C or C++ code even if it relies on platform-specific UI and localization. The alternative, rather than JS, is probably Java2objc, used by Google for new developments.