ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Learn how to use React Native FlatList’s virtualization, key props, and image caching to build memory‑efficient lists that perform well on any device. Includes a 10k‑item example, trade‑offs, and actionable tuning tips.
Stop the lag in your React Native apps. Learn how to use FlatList virtualization, getItemLayout, and windowSize to render thousands of items without crashing your app.
Guide to picking JavaScript or native stack navigators in React Navigation based on performance, header flexibility, and native dependencies.
Learn how to implement high-performance virtualization in React Native using FlatList, focusing on getItemLayout, memory management, and avoiding JS thread bottlenecks.
Determine whether Metro's cache‑key generation incorporates a distinction between the repository‑wide node_modules folder and the node_modules folders belonging to individual packages in a Yarn workspace monorepo. Metro builds its cache hash from file‑system watch events and the resolved module map; in a workspace, a change inside any package's node_modules
Context Access in React Navigation The NavigationContainer component manages the navigation state and provides the context required for hooks like useNavigation . This architecture requires that any component accessing the navigation object must be a descendant of the container in the React component tree. A design challenge arises when a component needs to
Goal: Determine whether to use FlatList with custom header rendering or SectionList for a large categorized dataset while maintaining smooth scrolling and low memory usage on both iOS and Android. Constraint: SectionList provides built‑in sticky section headers but requires a specific data shape and may allocate additional internal structures; FlatList is li
I'm designing local persistence for a React Native app (0.73-era, Android and iOS) where a reinstall or device-to-device restore must never silently resurrect stale state. The data is user preferences plus a small offline cache, and after any restore the app needs to prove the recovered records are intact and current before trusting them. The trade-off I can
We have a React web app using styled-components and are adding a React Native app using styled-components/native. Both should consume the same design tokens (colors, spacing, typography) through ThemeProvider, and ideally some presentational components would be shared rather than rewritten per platform. The uncertainty is where the interoperability line actu
reactnative
reactnavigation
styledcomponents