Back to Mobile Development

react-native-best-practices

react-nativeperformanceoptimizationmobile-developmentjavascriptnative-moduleshermesapp-performance
⭐ 1.4kπŸ“„ MITπŸ•’ 2026-06-02Source β†—

Install this skill

npx skills add callstackincubator/agent-skills

Works across Claude Code, Cursor, Codex, Copilot & Antigravity

This skill provides a systematic framework for debugging and enhancing the performance of React Native applications. It focuses on identifying bottlenecks across the JavaScript runtime, native bridge, and application bundling process. By addressing common issues like list rendering lag, excessive bundle size, and suboptimal startup times, it helps developers transition from reactive debugging to proactive optimization. The content emphasizes data-driven decision-making, using native profiling tools, bundle analyzers, and specific React patterns like atomic state management. It covers the full stack from high-level React optimization strategies to low-level native module integration and memory management. Whether you are addressing frame drops in complex UI components or minimizing binary size for distribution, this resource offers direct, actionable solutions tailored for professional React Native development environments.

When to Use This Skill

  • β€’Eliminating UI stutter during high-frequency list scrolling
  • β€’Reducing cold start time on low-end Android devices
  • β€’Diagnosing and resolving memory leaks in the native bridge
  • β€’Shrinking production app binary size before store deployment

How to Invoke This Skill

Example prompts that trigger this skill in Claude Code, Cursor, or Antigravity:

  • β€œHow do I fix my React Native app performance?
  • β€œReduce React Native bundle size
  • β€œWhy is my list scrolling laggy in React Native?
  • β€œOptimize React Native cold start time
  • β€œReact Native memory leak debugging guide

Pro Tips

  • πŸ’‘Combine this skill with a profiling tool (e.g., Flipper, Xcode Instruments, Android Studio Profiler) to accurately pinpoint bottlenecks before applying solutions.
  • πŸ’‘Implement suggestions incrementally, measuring performance after each change to isolate the impact and avoid introducing new issues.
  • πŸ’‘Prioritize optimizations marked as 'CRITICAL' or 'HIGH' impact by the skill first, as these often yield the most significant performance gains.
  • πŸ’‘Regularly review your component re-renders using React DevTools to proactively identify unnecessary updates before they become performance problems.

What this skill does

  • β€’Optimizing list rendering via virtualization
  • β€’Visualizing and reducing JavaScript bundle size
  • β€’Measuring Time to Interactive (TTI) and frame rate consistency
  • β€’Refactoring native code for Turbo Module compatibility
  • β€’Implementing automatic memoization and state atomization

When not to use it

  • βœ•When building basic prototypes that do not require production-grade performance
  • βœ•When investigating purely backend or API-side response latency

Example workflow

  1. Run an initial bundle analysis to identify large dependencies.
  2. Profile the UI using React DevTools to pinpoint expensive re-renders.
  3. Replace standard ScrollViews with virtualized lists where appropriate.
  4. Audit native module implementation to ensure asynchronous execution.
  5. Verify performance gains using native profiling tools like Instruments or Android Profiler.
  6. Finalize builds with Hermes and R8 optimizations enabled.

Prerequisites

  • –Access to Metro bundler and React Native CLI
  • –Installed React DevTools and native profiling suites
  • –Basic understanding of the Hermes engine

Pitfalls & limitations

  • !Premature optimization without first gathering metrics from profiling tools
  • !Over-memoizing components, which can sometimes increase overhead rather than reduce it
  • !Neglecting platform-specific differences when applying general JS-side fixes

FAQ

Should I use FlashList for every list?
Use FlashList for large or dynamic datasets where performance is critical. For small, static lists, a standard FlatList is usually sufficient.
How can I tell if my bundle is too large?
Run a source map explorer on your production bundle; if libraries you don't recognize or heavy polyfills appear, it is time to optimize your imports.
Is the React Compiler necessary for all apps?
While not strictly required, it significantly reduces manual memoization overhead and prevents common re-render bugs in complex applications.

How it compares

Unlike generic performance prompts, this skill enforces a taxonomy of specific metrics and tools, ensuring that solutions map directly to verified Callstack-backed React Native standards rather than trial-and-error changes.

Source & trust

⭐ 1.4k starsπŸ“„ MITπŸ•’ Updated 2026-06-02
πŸ“„ Full skill instructions β€” original source: callstackincubator/agent-skills
# React Native Best Practices

## Overview

Performance optimization guide for React Native applications, covering JavaScript/React, Native (iOS/Android), and bundling optimizations. Based on Callstack's "Ultimate Guide to React Native Optimization".

## Skill Format

Each reference file follows a hybrid format for fast lookup and deep understanding:

- **Quick Pattern**: Incorrect/Correct code snippets for immediate pattern matching
- **Quick Command**: Shell commands for process/measurement skills
- **Quick Config**: Configuration snippets for setup-focused skills
- **Quick Reference**: Summary tables for conceptual skills
- **Deep Dive**: Full context with When to Use, Prerequisites, Step-by-Step, Common Pitfalls

**Impact ratings**: CRITICAL (fix immediately), HIGH (significant improvement), MEDIUM (worthwhile optimization)

## When to Apply

Reference these guidelines when:
- Debugging slow/janky UI or animations
- Investigating memory leaks (JS or native)
- Optimizing app startup time (TTI)
- Reducing bundle or app size
- Writing native modules (Turbo Modules)
- Profiling React Native performance
- Reviewing React Native code for performance

## Priority-Ordered Guidelines

| Priority | Category | Impact | Prefix |
|----------|----------|--------|--------|
| 1 | FPS & Re-renders | CRITICAL | js-* |
| 2 | Bundle Size | CRITICAL | bundle-* |
| 3 | TTI Optimization | HIGH | native-*, bundle-* |
| 4 | Native Performance | HIGH | native-* |
| 5 | Memory Management | MEDIUM-HIGH | js-*, native-* |
| 6 | Animations | MEDIUM | js-* |

## Quick Reference

### Critical: FPS & Re-renders

**Profile first:**
# Open React Native DevTools
# Press 'j' in Metro, or shake device β†’ "Open DevTools"


**Common fixes:**
- Replace ScrollView with FlatList/FlashList for lists
- Use React Compiler for automatic memoization
- Use atomic state (Jotai/Zustand) to reduce re-renders
- Use useDeferredValue for expensive computations

### Critical: Bundle Size

**Analyze bundle:**
npx react-native bundle \
--entry-file index.js \
--bundle-output output.js \
--platform ios \
--sourcemap-output output.js.map \
--dev false --minify true

npx source-map-explorer output.js --no-border-checks


**Common fixes:**
- Avoid barrel imports (import directly from source)
- Remove unnecessary Intl polyfills (Hermes has native support)
- Enable tree shaking (Expo SDK 52+ or Re.Pack)
- Enable R8 for Android native code shrinking

### High: TTI Optimization

**Measure TTI:**
- Use react-native-performance for markers
- Only measure cold starts (exclude warm/hot/prewarm)

**Common fixes:**
- Disable JS bundle compression on Android (enables Hermes mmap)
- Use native navigation (react-native-screens)
- Defer non-critical work with InteractionManager

### High: Native Performance

**Profile native:**
- iOS: Xcode Instruments β†’ Time Profiler
- Android: Android Studio β†’ CPU Profiler

**Common fixes:**
- Use background threads for heavy native work
- Prefer async over sync Turbo Module methods
- Use C++ for cross-platform performance-critical code

## References

Full documentation with code examples in references/:

### JavaScript/React (js-*)

| File | Impact | Description |
|------|--------|-------------|
| js-lists-flatlist-flashlist.md | CRITICAL | Replace ScrollView with virtualized lists |
| js-profile-react.md | MEDIUM | React DevTools profiling |
| js-measure-fps.md | HIGH | FPS monitoring and measurement |
| js-memory-leaks.md | MEDIUM | JS memory leak hunting |
| js-atomic-state.md | HIGH | Jotai/Zustand patterns |
| js-concurrent-react.md | HIGH | useDeferredValue, useTransition |
| js-react-compiler.md | HIGH | Automatic memoization |
| js-animations-reanimated.md | MEDIUM | Reanimated worklets |
| js-uncontrolled-components.md | HIGH | TextInput optimization |

### Native (native-*)

| File | Impact | Description |
|------|--------|-------------|
| native-turbo-modules.md | HIGH | Building fast native modules |
| native-sdks-over-polyfills.md | HIGH | Native vs JS libraries |
| native-measure-tti.md | HIGH | TTI measurement setup |
| native-threading-model.md | HIGH | Turbo Module threads |
| native-profiling.md | MEDIUM | Xcode/Android Studio profiling |
| native-platform-setup.md | MEDIUM | iOS/Android tooling guide |
| native-view-flattening.md | MEDIUM | View hierarchy debugging |
| native-memory-patterns.md | MEDIUM | C++/Swift/Kotlin memory |
| native-memory-leaks.md | MEDIUM | Native memory leak hunting |
| native-android-16kb-alignment.md | CRITICAL | Third-party library alignment for Google Play |

### Bundling (bundle-*)

| File | Impact | Description |
|------|--------|-------------|
| bundle-barrel-exports.md | CRITICAL | Avoid barrel imports |
| bundle-analyze-js.md | CRITICAL | JS bundle visualization |
| bundle-tree-shaking.md | HIGH | Dead code elimination |
| bundle-analyze-app.md | HIGH | App size analysis |
| bundle-r8-android.md | HIGH | Android code shrinking |
| bundle-hermes-mmap.md | HIGH | Disable bundle compression |
| bundle-native-assets.md | HIGH | Asset catalog setup |
| bundle-library-size.md | MEDIUM | Evaluate dependencies |
| bundle-code-splitting.md | MEDIUM | Re.Pack code splitting |

## Searching References

# Find patterns by keyword
grep -l "reanimated" references/
grep -l "flatlist" references/
grep -l "memory" references/
grep -l "profil" references/
grep -l "tti" references/
grep -l "bundle" references/


## Problem β†’ Skill Mapping

| Problem | Start With |
|---------|------------|
| App feels slow/janky | js-measure-fps.md β†’ js-profile-react.md |
| Too many re-renders | js-profile-react.md β†’ js-react-compiler.md |
| Slow startup (TTI) | native-measure-tti.md β†’ bundle-analyze-js.md |
| Large app size | bundle-analyze-app.md β†’ bundle-r8-android.md |
| Memory growing | js-memory-leaks.md or native-memory-leaks.md |
| Animation drops frames | js-animations-reanimated.md |
| List scroll jank | js-lists-flatlist-flashlist.md |
| TextInput lag | js-uncontrolled-components.md |
| Native module slow | native-turbo-modules.md β†’ native-threading-model.md |
| Native library alignment issue | native-android-16kb-alignment.md |

## Attribution

Based on "The Ultimate Guide to React Native Optimization" by Callstack.

How to Use This Skill Unit

Option A: Project-Specific (Recommended)

  1. Click "Download" above
  2. In your project, create the directory: .agent/skills/react-native-best-practices/
  3. Save the file as SKILL.md
  4. The agent will automatically discover the skill based on its description.

Option B: Global Installation (All Agents)

Save the file to these locations to make it available across all projects:

  • Claude Code: ~/.claude/skills/callstackincubator/agent-skills/react-native-best-practices/SKILL.md
  • Cursor: ~/.cursor/skills/callstackincubator/agent-skills/react-native-best-practices/SKILL.md
  • Antigravity: ~/.gemini/antigravity/skills/callstackincubator/agent-skills/react-native-best-practices/SKILL.md

πŸš€ Install with CLI:
npx skills add callstackincubator/agent-skills

Read the Master Guide: Mastering Agent Skills β†’

Recommended Rules

View more rules β†’

Recommended Workflows

View more workflows β†’

Recommended MCP Servers

View more MCP servers β†’

Take It Further

Maximize your productivity with these powerful resources

πŸ“‹

Define Your Standards

Set up coding standards to ensure this workflow produces consistent, high-quality results.

Browse Rules Library
πŸ“–

Master Workflows

Learn how to create custom workflows, use Turbo Mode, and build your automation library.

Complete Guide

How to use this Skill in Claude Code & Cursor

For Claude Code (CLI)

To use this skill in Claude Code, copy the rule content into your project's custom instructions or follow our Add-Skill CLI guide. This ensures Claude follows your standards during every code generation.

For Cursor & Windsurf

For Cursor or Windsurf, individual skills are best used in the "Rules for AI" section. This specific unit helps the agent avoid mobile development issues, leading to cleaner, more efficient code.

Why the skill format matters: the standardized Agent Skills format lets your AI agent load detailed instructions only when they are relevant, keeping your prompt clean while improving results.

Source & attribution

This skill is categorized under Mobile Development and is published by callstackincubator, maintained in callstackincubator/agent-skills.

← Browse All Agent Skills
Sponsored AI assistant. Recommendations may be paid.