Swift on Android has been done already, by multiple independent groups:<p><a href="http:&#x2F;&#x2F;arctouch.com&#x2F;2014&#x2F;10&#x2F;swift-make-android-app&#x2F;" rel="nofollow">http:&#x2F;&#x2F;arctouch.com&#x2F;2014&#x2F;10&#x2F;swift-make-android-app&#x2F;</a><p><a href="http:&#x2F;&#x2F;romain.goyet.com&#x2F;articles&#x2F;running_swift_code_on_android&#x2F;" rel="nofollow">http:&#x2F;&#x2F;romain.goyet.com&#x2F;articles&#x2F;running_swift_code_on_andro...</a><p>It&#x27;s not exactly easy though, and I doubt that a single WORA language will <i>ever</i> become the preferred way to do mobile development.  (It already exists, anyway, in the form of Xamarin.  Neither Xamarin or Java on the desktop became all that popular, though, because the apps you can write with them just aren&#x27;t as good.)  A native platform is a moving target: by the time your cross-platform abstraction layer catches up, new features will have been introduced.<p>It&#x27;s more likely that a single app will become ubiquitous enough that you can count on it being on every platform, and then develop a programmable layer on top (a la the web).  Either that, or everyone will continue developing native clients with a shared data&#x2F;logic layer abstracted behind RPC calls.  That&#x27;s how we used to do networked applications back in the desktop days.