Hey nostr:nprofile1qqs04xzt6ldm9qhs0ctw0t58kf4z57umjzmjg6jywu0seadwtqqc75spz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsz9mhwden5te0wfjkccte9ec8y6tdv9kzumn9wshszxnhwden5te0wpuhyctdd9jzuenfv96x5ctx9e3k7mf0dv4ph5 what are the advantages of going for react native? Aren't web apps equally equipped to perform as apps nowadays? 🤔
As a solo Nostr developer, it’s becoming hard for me to justify continuing to develop Comingle using native frameworks. I’m normally a proponent for native frameworks for the look and feel, but that can arguably scale well only with a team of developers, which I don’t have. I shipped the iOS app (backed by Nostr SDK for Apple Platforms) a couple months ago, but it’s very difficult for me to spend time to write a duplicate version in Android and Web, especially with the limited amount of time I have as is. Olas by nostr:npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft makes a compelling case for using React Native / NDK Mobile to ship fast — it’s slick and performs reasonably well in the brief time I’ve spent with it. I’m going to play around with NDK Mobile to see how far I can get with it.
Discussion
React Native components communicate directly with the native platform, which give it a closer look and feel on a mobile device than a PWA (or any kind of web app) ever will.
Yes. This. I tried everything I found that didn’t require reinventing NDK. React native gets really close to the metal; you can always go down to implement what you need in C++, the new architecture stuff makes a significant difference because now you can write native code and not pay an overhead payload penality with serialization/deserialization when you write to the UI.
It’s really annoying and far slower than web development though