寫mobile app

咁唔知而家做app
如果一定要iOS Android兩邊都要有

係咪一定用rn 果類
而唔會考慮用native language 呢

睇下AirBnB 點解當初㨂RN 然後又回歸native

https://blog.oursky.com/2018/08/08/airbnb-sunsetting-react-native-for-mobile-and-web/

然後諗下點解 Uber Deliveroo Foodpanda Gogox lalamove hktvmall lihkg 都係native app.

不過銀行業的確朝向RN, 香港主要銀行仍然係native 既只剩BOC, HSBC, 行山。虚銀多數係 RN。不過唔同國家既HSBC app 有全球single code base 既優勢。

但睇英國既銀行就主要係native app (咁解釋到HSBC 係native)

Game 就當然無RN 既空間。

RN有啲嘢的確無Native咁好 啲人只係想慳錢整app

係，純貪玩，過下寫alps癮就hybrid 玩住先
flutter都係唔錯選擇

但for長遠搵食或搵工freelance 又好
native android 或ios ，react native一定冇死

Kotlin 寫ios Android 既business logic

KMM

https://kotlinlang.org/lp/mobile/

覺得幾正

想睇下從iOS dev 角度點睇呢壇嘢

c++ 又要寫一堆JNI code, 結果又要map 一層變番做java/kotlin, 用黎做serialization.
以前試過用go 寫native library 放落android, 不過有哂用C++ 寫既所有問題，外加Go 個runtime library 勁大，不過呢點唔知而家有無改變 。

我唔介意shared code 係 java 定 swift, 不過我希望係code generation 而唔係native share library. 即例如swift 通過某種gradle plugin 變成kotlin code, 又或直接generate byte code 都OK.

用React撐fb

OS specific API is too hard to maintain with shared code base, won’t work unless iOS open up (in terms of working with other platforms)

KMM is not going to let you "write once deploy twice" in react native sense. It just make Kotlin Native work with iOS API interface. So platform specific code still needs to be implemented twice. Platform netural code can be shared.

行山同boc 個app 好垃圾又樣衰又難用

最靚既banking app我覺得係citibank 同hsbc

flutter 新手friendly好多

多謝

So why not RN?

因為真係compile binary, 真係直接call api. 理論上obj c, swift 做到既嘢都可以直接做到。
所以目標係用同一種language 寫兩個native app, 唔係加多層嘢嘢abstract 兩個platform 既分野。

Then why not flutter

Flutter 都係在native 系統上加多一層abstraction，又在Kotlin/Swift 之外又加多一種language.
KMM 完全無。

補充番，唔係話RN 同 Flutter 無用，而係話佢地同KMM 係用唔同approach 面對cross platform 問題，無話互相取代。

UI Kit 全部要俾錢買🤌

我意思係我睇唔出 KMM 嘅優勢，除咗唔駛學多一種 Language

呢D留番俾茶水阿姐用