Kotlin & Swift
4 likes594 views
The talk discusses the evolution of mobile development through the comparison of Kotlin and Swift, focusing on languages, architecture, layouts, and their similarities and differences. It highlights the challenges faced over time in both iOS and Android development, emphasizing the shift towards functional programming and modern architectural patterns. The presenter advocates for becoming proficient in both platforms to enhance collaboration and streamline development processes.
Kotlin & Swift
- 1. KOTLIN & SWIFT THE EVOLUTION OF MOBILE DEVELOPMENT
- 3. WHAT THIS TALK IS ABOUT? ▸ Languages ▸ Architecture ▸ The Big Picture ▸ Layouts ▸ Why is it interesting? ▸ References
- 4. WHAT THIS TALK IS NOT ABOUT ? ▸ Application Lifecycle ▸ Networking ▸ Security ▸ Storage ▸ Continuos Integration ▸ Distribution ▸ Soft Skills ▸ Platform specific Frameworks ▸ IDE’s
- 8. TEXT KOTLIN &SWIFT ▸ Similar Philosophy: ▸ Pragmatic ▸ Concise ▸ Safety ▸ Interoperability
- 9. Swift Android Disclaimer: Both platforms have additional ways of defining and initializing a class
- 10. Swift Android Disclaimer: Both platforms have additional ways of defining and initializing a class Immutable
- 11. Swift Android Disclaimer: Both platforms have additional ways of defining and initializing a class Optionals
- 12. Swift Android Disclaimer: Both platforms have additional ways of defining and initializing a class Initializers
- 13. Swift Android Disclaimer: Both platforms have additional ways of defining and initializing a class Default Values
- 20. Swift Android
- 24. Swift Android Optionals and Null Safety Value Type Reference Type
- 25. Swift Android Optionals and Null Safety Value Type Reference Type
- 26. Swift Android Optionals and Null Safety Value Type Reference Type
- 29. Swift Android Interfaces/Protocols and Default Implementation
- 30. Swift Android Interfaces/Protocols and Default Implementation
- 31. Swift Android Interfaces/Protocols and Default Implementation
- 32. Swift Android Type Casting/ Type Checks
- 33. Swift Android Type Casting/ Type Checks
- 34. Swift Android Type Casting/ Type Checks
- 35. MORE……
- 36. ARCHITECTURE
- 37. SHARED ARCHITECTURES ▸ Platform agnostic:MVP, MVVM, Clean Architecture, etc…. ▸ Protocol Oriented Programming
- 38. BIG PICTURE
- 39. BIG PICTURE KOTLIN ▸ Statically Typed ▸ Supports Type Inference ▸ Type Checks when compiling ▸ Null Safety (Billion Dollar Mistake) ▸ Supports Object Oriented Programming and some Functional Programming ▸ Statically Typed ▸ Supports Type Inference ▸ Type Checks when compiling ▸ Null Safety ▸ Supports some Functional Programming Encourages Protocol Oriented Programming SWIFT
- 40. BIG PICTURE KOTLIN ▸ Higher Order Functions ▸ Any and Any? Is similar to Object in java ▸ Lambdas as Parameters and return values ▸ Generics ▸ Higher Order Functions ▸ Any and AnyObject ▸ Closures ▸ Generics SWIFT
- 41. BIG PICTURE KOTLIN ▸ Immutability is not forces but strongly encouraged ▸ Extensions to add new Functionality ▸ Interoperability with java ▸ Semi automatic conversion Java-> Kotlin ▸ Immutability is not forces but strongly encouraged. ▸ Extensions to add new Functionality ▸ Interoperability with Objective-C ▸ Manual conversion Obj-c ->swift SWIFT ▸ This are some commonalities there are more…
- 42. LAYOUTS
- 43. TEXT AUTOLAYOUT VS CONSTRAINT LAYOUT ▸ Similarities: ▸ Precise: Adaptive ▸ Design via GUI ▸ Based on Cassowary Algorithm ▸ Differences: ▸ Default Behavior ▸ Fallback Handling
- 44. TEXT UISTACKVIEW VS LINEAR LAYOUT ▸ Similarities: ▸ Maintainable ▸ Orientation Control ▸ Graceful Dynamic behaviors ▸ Differences: ▸ Weighting
- 45. CONSTRAINT LAYOUT VS AUTO LAYOUT
- 46. CONSTRAINT LAYOUT VS AUTO LAYOUT https://developer.apple.com/library/content/documentation/DeveloperTools/Conceptual/ debugging_with_xcode/Art/dwx-sw-dvh-1_2x.png
- 47. CONSTRAINT LAYOUT VS AUTO LAYOUT
- 48. CONSTRAINT LAYOUT VS AUTO LAYOUT https://www.bignerdranch.com/blog/constraintlayout-vs-auto-layout-how-do-they-compare/
- 50. CHALLENGES OVER TIME ▸ Challenges 1: • iOS: Obj-C Syntax, Memory Management, Pointers, etc. • Android: Java a language well known to a lot of people, very stable. Lifecycle Management (Activities) was the challenge, Eclipse ▸ Challenges 2: • A new language. Constant changes on the language. Interoperability with Obj-C. • Android: Introduced Fragments, Life Cycle Management, Multiple Device screens. Support for different API’s, Gingerbread. My Perspective
- 51. CHALLENGES OVER TIME ▸ Challenges 3 • iOS: New programming paradigm: Functional Programming, Protocols and Protocol Oriented Programming, Generics. Constant evolution of the language. Auto Layout. Automatic Reference Counter. • Android: Migration from Eclipse to Android Studio. Maven vs Gradle. More strict patterns to follow in Android. Multiple devices. Gingerbread. ▸ Challenges 4 • iOS: More language changes. Stack Views. • Android: Compatibility with Java 8. Start to consider a more functional approach. Constraint Layout. Both Auto Layout and Constraint Layout are based on Cassowary algorithm. My Perspective
- 52. CHALLENGES OVER TIME ▸ Challenges 5 • iOS: Breaking changes in the language. Keeping code base up to date. Removing old Obj-C Code • Android: New Language Supported by Google. Will have similar problems that what happened when swift was introduced. (Opportunity to learn from previous experiences.). More opinionated about architecture. My Perspective
- 53. • Learning Curve in knowing two languages has declined over time • Learning curve in platform specific things is reducing and becoming more opinionated. • Increased Team Collaboration. • We still need to learn the specifics about each platform like lifecycle, best practices, frameworks, threads, permissions. E.g: Core Data, Room. • Similar implementation. • Layouts follow a similar approach. CONCLUSIONMy Perspective
- 54. WANT TO BECOME PLATFORM BILINGUAL
- 55. YOU ARE ANDROID ENGINEER WHO WANT TO BECOME IOS PROFICIENT • Learn Kotlin • Then Learn iOS platform specific things. The language will be easier.
- 56. YOU ARE IOS ENGINEER WHO WANT TO BECOME ANDROID PROFICIENT • First learn the basics of Kotlin. • Then focus mostly in learning Android Specific things using Kotlin.
- 57. REFERENCES
- 58. REFERENCES ▸ https://building.coursera.org/blog/2016/03/16/becoming- bilingual-coursera/ ▸ https://gist.github.com/cbruegg/ d982a4bdc47757633f5355d4f1252d0e#who-is-using-kotlin ▸ https://medium.com/@Pinterest_Engineering/the-case- against-kotlin-2c574cb87953 ▸ http://nilhcem.com/swift-is-like-kotlin/ ▸ https://www.youtube.com/watch?v=_DuGaAkQSnM&t=215s