iOS & Android & Swift & Kotlin

Google+ Pinterest LinkedIn Tumblr +

Video is ready, Click Here to View ×

Android and iOS development tools have consistently converged over the past few years. The arrival of Kotlin as a second officially supported language for Android development is perhaps the most significant example of this to date.

Kotlin and Swift were designed independently but share many foundational principles. In this talk, I compare and contrast these exciting languages and show you just how similar their implementations are. I also demonstrate how shared architectures and layout design tool evolution have further aided cross platform parity.

If you’re a cross-platform curious iOS developer, then this talk’s for you! There’s never been a better time to widen your horizons.

Venue: Motor City CocoaHeads


About Author


  1. For computed read only properties in Kotlin (using a custom getter) the type can be omitted (type inference is applied on the last line in the custom getter).

  2. In Kotlin if a function is only returning the result of a "when" then the return type can be omitted, and the function brackets replaced with a "=", eg:

    // …

    fun getUrl(t: Type) = when(t) {
    VISA -> "/visa"
    MASTERCARD -> "/mc"
    DISCOVER -> "/disc"

    Kotlin doesn't use the "switch" keyword because the things that can be done with a "when" aren't what you would expect to find with the "switch" statement in other languages. Switch statement has a standard set of behaviours/functionality. Any language implementing "switch" which doesn't stick to the standard behaviour isn't implementing the feature properly.