Expo – Open-source platform for making universal apps for Android, iOS, and web

Post by r9295 » Wed, Jul 26, 2023, 2:26 PM UTC

knlam wrote: post #77

r9295 wrote: post #52

Without a doubt, Expo is one of the worst tools I have ever used. 1. I can't get a debug build of the app without using their cloud services. 2. Latest version of Android app to preview Expo apps did not work with latest stable Expo version. 3. Random build errors all the time due to some features being deprecated without being mentioned anywhere. 4. Tries to do too much and breaks quite often

They improve a lot in the last 2 years, give it another try. The experience nowadays is pretty pleasant compare the plain RN project

Post by Zelphyr » Wed, Jul 26, 2023, 2:28 PM UTC

Post by jacobp100 » Wed, Jul 26, 2023, 2:39 PM UTC

qazxcvbnm wrote: post #99

jacobp100 wrote: post #91

Earlier quoted context omitted.

It’s possible to do all this stuff in RN - you just need good native bindings to the features Stuff like the iOS 13 page sheet modals being broken is still an issue - but there’s a set of present/dismiss callbacks in the modal manager you can override in your code to fix it Not sure if you meant page sheet controllers for iOS 15 (the ones that let you pin it half way up). There have been implementations of this, but…

If asynchronous layout were the culprit, presumably that's the precise type of issue that react-native-reanimated solves? It seems to me that the experiences created via react-native-reanimated run quite smoothly indeed. Of course, the developer still has to reimplement interactions otherwise provided by iOS etc, but React Native should not be a reason for things like sloppy interactions.

Post by qazxcvbnm » Wed, Jul 26, 2023, 2:49 PM UTC

jacobp100 wrote: post #115

qazxcvbnm wrote: post #99

Earlier quoted context omitted.

If asynchronous layout were the culprit, presumably that's the precise type of issue that react-native-reanimated solves? It seems to me that the experiences created via react-native-reanimated run quite smoothly indeed. Of course, the developer still has to reimplement interactions otherwise provided by iOS etc, but React Native should not be a reason for things like sloppy interactions.

The animated package doesn’t come into play here. When the layout needs to be recomputed in RN, it does it asynchronously - regardless of what’s calling it. Part of this can be explained because the JS can hook listen for layout updates via the onLayout prop and make changes to the layout - and could in theory cause infinite loops. But there’s no mechanism - as far as I’m aware - to say you don’t care about that deta…

Post by ramones13 » Wed, Jul 26, 2023, 3:05 PM UTC

scop wrote: post #106

norman784 wrote: post #95

Earlier quoted context omitted.

I learned a while ago that is not worth using an abstraction layer over the official tooling (whatever Apple and Google provides you), even for small apps I was building one for each platform (as one dev). Tried at the time Xamarin and PhoneGap, and bit later RN, each one has his quirks and things that works in one platform but not in other so in the end you end up building one app for each platform more or less, but…

I’ve come to the same conclusion. I began to build a very simple app about a month ago and as a Web Dev figured React Native would be the best tool. Having completed about 60% of the app, I’m going to trash the whole thing and restart with Swift/Kotlin. I’ve encountered too many “quirks” that end up burning a huge amount of time for what should be an inconsequential component.