Content pfp
Content
@
https://opensea.io/collection/dev-21
0 reply
0 recast
2 reactions

pal 🟪 pfp
pal 🟪
@pal
If you were to build a mobile app today, would you build it in Swift or React Native (or other)? What are the current trade-offs?
7 replies
0 recast
3 reactions

Justin Hunter pfp
Justin Hunter
@polluterofminds
If cross-platform is no issue, I’d build it in Swift. I prefer it over React Native plus there’s less build and distribution headaches. Tradeoff is obviously that it’s iOS only.
1 reply
0 recast
2 reactions

NCOOKIΞ pfp
NCOOKIΞ
@ncookie
Unless you really have a need for native-only features, build a PWA.
1 reply
0 recast
1 reaction

raquo pfp
raquo
@raquo.eth
Build RN for both platforms to ship fast, plan to write a Swift version for iOS once you have traction and need that sweet performance and aesthetics. Then keep RN as single platform for android, deeper talent pool than native android
0 reply
1 recast
1 reaction

Alex Loukissas 🍉 pfp
Alex Loukissas 🍉
@futureartist
Unless you have very specific use cases (e.g. A/V or gaming), RN (Expo specifically) will get you really far and give you x-platform reach, as well as over-the-air updates.
0 reply
0 recast
1 reaction

limone.eth 🍋 pfp
limone.eth 🍋
@limone.eth
flutter, but doesn’t have much support for web3 stuff rn i believe
0 reply
0 recast
0 reaction

Rafi pfp
Rafi
@rafi
Swift if iOS is your main target If you have an experience with C/Java/similar, it's easier to learn and use than RN
0 reply
0 recast
0 reaction

Omar pfp
Omar
@omarperacha.eth
These days the default option would be to built natively (swift for iOS, kotlin for Android). It simply keeps your options much more open to evolve long term. If you’re confident the lifetime scope of your app is limited, e.g. in a way that doesn’t need thread-level control, hybrid is the faster approach for you!
1 reply
0 recast
0 reaction

j3 pfp
j3
@j3
Flutter
1 reply
0 recast
0 reaction