<story><title>Swift Ported to Android</title><url>https://github.com/apple/swift/pull/1442</url></story><parent_chain><item><author>Fargren</author><text>I love Kotlin, but being able to develop libraries in one language and use them in both Android and iOS is huge. I have been using J2Objc for this until now, and while it&amp;#x27;s a great tool, it forces me to use Java, which I don&amp;#x27;t love. I would prefer being able to use Kotlin on iOS, but using Swift for Android development is a great boon.</text></item><item><author>V-2</author><text>Surprised noone mentions Kotlin. It&amp;#x27;s quite Swift-like, backed by JetBrains (Android Studio is based on their IntelliJ Idea), and 1.0 has only just been released. It has full interoperability with Java.&lt;p&gt;Given the above, I don&amp;#x27;t see much point in using Swift, unless it&amp;#x27;s one of these projects that are about proving a point (nothing wrong with that and often very interesting).</text></item></parent_chain><comment><author>josephearl</author><text>AFAIK there&amp;#x27;s nothing stopping you using Kotlin on iOS with RoboVM since it is a JVM language - &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;robovm.com&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;robovm.com&lt;/a&gt;.</text></comment>
<story><title>Swift Ported to Android</title><url>https://github.com/apple/swift/pull/1442</url></story><parent_chain><item><author>Fargren</author><text>I love Kotlin, but being able to develop libraries in one language and use them in both Android and iOS is huge. I have been using J2Objc for this until now, and while it&amp;#x27;s a great tool, it forces me to use Java, which I don&amp;#x27;t love. I would prefer being able to use Kotlin on iOS, but using Swift for Android development is a great boon.</text></item><item><author>V-2</author><text>Surprised noone mentions Kotlin. It&amp;#x27;s quite Swift-like, backed by JetBrains (Android Studio is based on their IntelliJ Idea), and 1.0 has only just been released. It has full interoperability with Java.&lt;p&gt;Given the above, I don&amp;#x27;t see much point in using Swift, unless it&amp;#x27;s one of these projects that are about proving a point (nothing wrong with that and often very interesting).</text></item></parent_chain><comment><author>untog</author><text>Could you develop libraries that way, though? It would have to be absolutely pure Swift, not using any iOS libraries, like NSURL etc. etc. - surely incredibly limiting.</text></comment>