Having two similar languages on different platforms isn&#x27;t as useful as having the <i>same</i> language on both platforms, though.<p>So, you can have Kotlin on iOS via RoboVM. But that&#x27;s kind of expensive. Also, RoboVM brings its own heavy runtime environment with its own class hierarchy, garbage collector, and the need to bridge between that world and the ObjC runtime.<p>Or you can have RemObjects&#x27;s almost-Swift (<a href="http:&#x2F;&#x2F;www.elementscompiler.com&#x2F;elements&#x2F;silver&#x2F;" rel="nofollow">http:&#x2F;&#x2F;www.elementscompiler.com&#x2F;elements&#x2F;silver&#x2F;</a>) on Apple platforms, Android&#x2F;JVM, and .NET as well. I call Silver almost-Swift because some permanent differences from real Swift are documented here: <a href="http:&#x2F;&#x2F;docs.elementscompiler.com&#x2F;Silver&#x2F;DifferencesAndLimitations&#x2F;" rel="nofollow">http:&#x2F;&#x2F;docs.elementscompiler.com&#x2F;Silver&#x2F;DifferencesAndLimita...</a> For that reason, though I like the Elements compiler&#x27;s approach of targeting each platform in the most native possible way, I&#x27;d recommend using their C# front-end or even their Oxygene language (a Pascal derivative) instead.