bryan_ka

A big feature for our app is that it needs to work in spotty network conditions - especially as we've expanded internationally, and as students are now studying from home where they often don't have WiFi.

We have a redux store where we keep our data, and much of the "have you watched this video" or "have you completed this assignment" data gets persisted to disk, so if a network failure happens we can just try again when the user's device is back on!

(Does that answer your question?)

It's been a bit since I looked at the overall roadmap, but I've really enjoyed what I've seen and used so far! I've been enjoying Hooks lately, for example.

We'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!

It'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!

I've heard great things about it! Haven't used it myself yet.

We've considered using it for our interactive-exercises code (because it's shared between web and mobile) but haven't made concrete plans yet to make that change. (For now, our interactive exercises are still an embedded webview wrapped in React Native "chrome".)

Hi! I'm the author of the post, happy to answer any questions you might have!