Skip to content

(Cross Multi) Platform

LeoTM edited this page Feb 27, 2023 · 36 revisions

Native vs Cross-Platform

  • Less people, reduced org scaling problems

Eventually - you will hire half somebody

React Native (RN)

  • js/ts
  • js VM (debug: V8, prod: JSC/Hermes)
  • js<->native bridge (soon JSI)
  • js-only (logic) updates pos (CodePush)
  • UI: js (soon Fabric)
    • native Android/iOS
    • RN Paper (Material Design Android/iOS)

Flutter

  • Dart
  • no VM (prod)
  • Dart<->native bridge
  • UI: canvas (component updates have no effect)
    • Material Design (Android/iOS)
    • Cuptertino (native iOS)

same design/UI for Android/iOS

Kotlin Multiplatform Mobile (KMM)

  • write native ez
  • no VM
  • business logic, no UI
  • keep native UI
    • no eco, works w native platform eco's
    • SwiftUI / Jetpack Compose
  • no intermediate layer
    • no interop bottlenecks

lots of business logic and the design is easy to achieve


More