5 ms·

For me, the React Native experience has been instructive. Android is quick and easy to develop, debug, and deploy. The iOS side includes multiple hoops, const

For me, the React Native experience has been instructive. Android is quick and easy to develop, debug, and deploy. The iOS side includes multiple hoops, constant frustration stemming from XCode, long app release times, and minutes-long builds for production-size apps. Our team, without any policy dictating daily development habits, has coalesced around Linux/Android development with iOS testing before release.

askafriend 6y ago
As a consumer, I've never used a React Native app that I liked using. It's always janky and commpromises UX in ways that made me simply use the app less or had the effect of teaching me to "get in and out of the app as quickly as possible".
- ARandomerDude 6y ago
  As with everything, it depends on the implementation. There are some things I'd like to clean up about our app, but overall feedback has been very positive.
- com2kid 6y ago
  > As a consumer, I've never used a React Native app that I liked using. If it is a good react native app you won't know it is RN. If you notice it, it is by definition poorly done. There are some things (e.g. specific animations, UI elements) that RN just isn't great at, the best way to avoid making a janky app is to avoid even trying to do those things.
  - 72deluxe 6y ago
    Non-native menus and poor keyboard focus handling and shortcuts are the giveaway, and extreme memory usage!
- ulisesrmzroche 6y ago
  That’s your bias. Most consumers have mo clue what react native is
nicoburns 6y ago
> Our team, without any policy dictating daily development habits, has coalesced around Linux/Android development with iOS testing before release. Interestingly our team has gone the opposite way (again, no official policy). The deciding factor in our case has been the relative performance of Xcode/iOS Simulator vs Android Studio + Android Emulator. Android Studio on it's own slows my computer down more than Xcode compiling AND the iOS Simulator running at the same time. The Android emulator is all but unusable on my MacBook. I agree there's a lot of painful bits around signing/release on iOS though.

askafriend 6y ago

As a consumer, I've never used a React Native app that I liked using. It's always janky and commpromises UX in ways that made me simply use the app less or had the effect of teaching me to "get in and out of the app as quickly as possible".

ARandomerDude 6y ago
As with everything, it depends on the implementation. There are some things I'd like to clean up about our app, but overall feedback has been very positive.
com2kid 6y ago
> As a consumer, I've never used a React Native app that I liked using. If it is a good react native app you won't know it is RN. If you notice it, it is by definition poorly done. There are some things (e.g. specific animations, UI elements) that RN just isn't great at, the best way to avoid making a janky app is to avoid even trying to do those things.
- 72deluxe 6y ago
  Non-native menus and poor keyboard focus handling and shortcuts are the giveaway, and extreme memory usage!
ulisesrmzroche 6y ago
That’s your bias. Most consumers have mo clue what react native is

nicoburns 6y ago

> Our team, without any policy dictating daily development habits, has coalesced around Linux/Android development with iOS testing before release. Interestingly our team has gone the opposite way (again, no official policy). The deciding factor in our case has been the relative performance of Xcode/iOS Simulator vs Android Studio + Android Emulator. Android Studio on it's own slows my computer down more than Xcode compiling AND the iOS Simulator running at the same time. The Android emulator is all but unusable on my MacBook. I agree there's a lot of painful bits around signing/release on iOS though.