UI unresponsive during large data processing on main thread
Tests RN's dual-thread model and 16.67ms frame budget. Strong answers separate JS and UI thread roles, blame long JS tasks for dropped frames, and propose chunking data to yield the event loop. Red flag: claiming memoization alone solves thread blocking.
Tests whether you understand React Native's separation of the JavaScript thread from the native UI main thread and the 16.67ms per-frame budget at 60fps. A strong answer identifies that heavy data processing blocks the JS thread, preventing batched view updates and touch events from reaching native land, which drops frames and freezes interactions. It then outlines refactoring by slicing the work into smaller chunks that yield to the event loop across multiple frames.
Read the original → reactnative.dev
- #react-native
- #performance
- #threading
- #frame-drops
- #js-thread
Get five bites like this every day.
Tezvyn delivers a daily feed of 60-second tech bites with quizzes to lock in what you learn.