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
I am developing a mobile with react-native (react-native-firebase/auth) and using Firebase Auth to manage user login. In the beginning, I only use the email/password to auth users and work nice. Now I would like to let users use Azure AD. Since react-native-firebase/auth does not support Microsoft account at this moment, so I use react-native-app-auth. After
I have a query for firebase that has an array of IDs that has a size > 10. Firebase has restrictions on the number of records to query in one session. Is there a way to query against more than 10 at a time? [Unhandled promise rejection: FirebaseError: Invalid Query. 'in' filters support a maximum of 10 elements in the value array.] https://cloud.google.co
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
commented · 25 Jun 2024, 10:03 UTC
reactnative
reactnavigation
oauth