Maximizing List Performance in React Native with FlatList
Learn how to replace ScrollView with FlatList, tune keyExtractor, getItemLayout, and initialNumToRender, and measure real‑world gains in frame rate and memory usage.
Loading…
ReadMeFeed / Community knowledge
#react-native
Real questions. Useful conversations. Find the people who know your stack.
Managing App Navigation with Expo Router's File-Based System
Stop fighting with massive navigation config files. Learn how Expo Router's file-based system automates routing and deep linking in React Native.
Architecting Secure Data Persistence with Expo Secure Store: Requirements, Design, and Failure Handling
Learn how to design a minimal, reliable secure‑storage layer in Expo. Covering requirements, trust boundaries, operational checks, failure modes, and when to redesign, the guide shows concrete code and diagnostics for real‑world apps.
Stop Using ScrollView for Long Lists: Optimizing React Native FlatList
Learn how to move from ScrollView to FlatList in React Native to handle long datasets. We cover virtualization, getItemLayout, and memory management tips.
reactnativeCombining Bottom Tabs with Independent Stacks in React Navigation v6
Learn how to nest stack navigators inside bottom tabs in React Navigation v6 to give each tab its own navigation history while keeping a shared tab bar.
reactnavigation
expoReact Native Hermes Release White Screen on Cold Start: Diagnostic Guide
Diagnostic guide for React Native apps with Hermes enabled that show a blank white screen on cold start in release builds while debug builds work. Covers bundle packaging, bytecode generation and native build config.
Diagnosing Deep Link Failures in React Navigation v6
Step‑by‑step checklist to identify why React Navigation v6 ignores incoming deep links and how to fix each common cause.
Managing App Updates with Expo Over-The-Air (OTA) Delivery
Stop waiting for app store reviews for every bug fix. Learn how Expo's OTA updates deliver JavaScript changes instantly and where the native code boundary lies.
Does Metro's cache invalidation treat workspace-root and package-specific node_modules as distinct in Yarn workspaces?
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