Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Kotlin or Swift, why not both?

Bas Broek
November 14, 2019

Kotlin or Swift, why not both?

On Kotlin, Swift, and how we work together across and within teams at XING.

Given at a Google Developer Group meetup in Valencia with Laura Oran (twitter.com/sastresa)

Bas Broek

November 14, 2019
Tweet

More Decks by Bas Broek

Other Decks in Programming

Transcript

  1. 2 Meeting point func makeIncrementer() -> ((Int) -> Int) {

    func addOne(number: Int) -> Int { 1 + number } return addOne } let increment = makeIncrementer() increment(7) fun makeIncrementer(): (Int) -> Int { val addOne = fun(number: Int): Int { return 1 + number } return addOne } val increment = makeIncrementer() increment(7) Similar syntax Kotlin Swift
  2. 5 1. XING Android app: 70% of the code 2.

    XING iOS app: 50% of the code Kotlin & Swift our current status
  3. 8 • Platform-focused "core" teams • Includes user experience design,

    product owners, tester • Coordinate and help the wider iOS "Community" • App-wide improvements and architecture • High-level overview of the product Platform teams
  4. 9 • Tooling • Continuous Integration • Release Management •

    Main coordination with Platform teams Mobile Releases Team
  5. 14 Access Token Alignment - Unified experience across platforms -

    ... both technical and for the user - Faster improvements going forward - Exchange between platforms
  6. 15 XING Design System • Cross-platform - iOS, Android and

    Web • Shared design language • Accessibility 15
  7. 17

  8. 17 Conclusion - It's not just about the language -

    Communication is important - Figure out how to work together
  9. 17 Conclusion - It's not just about the language -

    Communication is important - Figure out how to work together - Keep improving the technical landscape
  10. 17 Conclusion - It's not just about the language -

    Communication is important - Figure out how to work together - Keep improving the technical landscape - Consider shared patterns to ease knowledge sharing
  11. 17 Conclusion - It's not just about the language -

    Communication is important - Figure out how to work together - Keep improving the technical landscape - Consider shared patterns to ease knowledge sharing - Learn from each other's challenges & solutions