3 ms·
Hi! I'm the author of the post, happy to answer any questions you might have!
by bryan_ka 6y ago
Hi! I'm the author of the post, happy to answer any questions you might have!
- randompwd 6y agoI was briefly on a project which used React Native ~3 years ago. The non-descrpit red error screen was a killer. Has the dev experience for RN improved much since then?
- bryan_ka 6y agoIt's gotten much better over the last three years! Like the other reply here said - go take a look at the recent LogBox updates there!
- EngVagabond 6y agoCheck out the new error screen (LogBox) in 0.63! https://reactnative.dev/blog/2020/07/06/version-0.63 https://reactnative.dev/blog/2020/07/06/version-0.63
- osamaqarem 6y agoHi Bryan. Loved the article! I've been doing React Native for about a year-plus now. One of the things I've struggled with is making Android feel performant. The first render for heavy screens can be noticeably slow. Do you have any practices that you stick to to ensure Android performs well? Thanks!
- bryan_ka 6y agoWe've got some SectionList and FlatList components in the app that can get pretty long (e.g. our Unit screen lists out every lesson and content-item in there, that's pretty big.) We use the initialNumToRender prop to help out with rendering long lists like that - dunno if that's one of your performance bits, but it was a big help to us!