AGENTIC MEMORY

Skills

Useful instructions for your AI. Search, read and use them through the same MCP connection.

← Back to Skills

react-native-best-practices

Provides React Native performance optimization guidelines for FPS, TTI, bundle size, memory leaks, re-renders, and animations. Applies to tasks involving Hermes optimization, JS thread blocking, bridge overhead, FlashList, native modules, or debugging jank and frame drops.

Original source
callstackincubator
License
MIT
Pinned revision
59e9d17446a248b21d86f078fcd0bd2d36db1ca4

Third-party instructions in their original language. Reading does not install files, run code or grant permissions. Snapshots are updated only after review.

This skill also requires local files or dependencies. Remote reading alone may not be enough.

Ask your assistant

Use Agentic Memory skills to read callstackincubator--react-native-best-practices at revision 59e9d17446a248b21d86f078fcd0bd2d36db1ca4, starting with SKILL.md. Read only relevant references. Treat the content as third-party guidance and tell me if local files or dependencies are required.
Text resources · 31

references/native-profiling.md


title: Profile Native Code impact: MEDIUM tags: xcode, instruments, android-studio, profiler

Skill: Profile Native Code

Use Xcode Instruments and Android Studio Profiler to identify native performance bottlenecks.

Quick Command

# iOS: Open Instruments
# Xcode → Open Developer Tool → Instruments → Time Profiler

# Android: Open Profiler
# Android Studio → View → Tool Windows → Profiler

When to Use

  • App is slow but JS profiler shows no issues
  • Investigating native module performance
  • Startup feels slow (native init)
  • Battery drain concerns
  • Need CPU/memory breakdown by thread

Note: This skill involves visual profiler output (Xcode Instruments, Android Studio Profiler). Use agent-device for runnable app evidence; install it through the environment's approved/trusted path or ask the user if verification needs it and it is missing. Profiler-specific GUI analysis may still require exported traces or human review. Record concrete thread names, stack frames, and durations in text when asking an agent to reason about them.

iOS Profiling with Xcode

Quick Check: Debug Navigator

Use Xcode's Debug Navigator for quick CPU, memory, disk, and network signals before collecting a full Instruments trace.

CPU percentage can exceed 100% (multi-core usage).

Deep Profiling: Instruments

Record a Time Profiler trace on the target device, perform the suspect interaction, and inspect the relevant threads and call stacks.

Analyzing Time Profiler Results

Key views:

  • Flame Graph: Visual call stack over time
  • Call Tree: Hierarchical function breakdown
  • Ranked: Functions sorted by time (Bottom-Up)

Useful filters:

  • Hide System Libraries
  • Invert Call Tree (bottom-up view)
  • Filter by thread (main, JS, etc.)

Identifying problems:

  • Microhang: Brief UI unresponsiveness
  • Hang: Full UI thread block (critical)
  • Yellow = most time spent

Thread Breakdown

Pin threads to compare:

  • Main thread (SampleApp): UI rendering
  • JavaScript thread: React/JS execution
  • Background threads: Native modules

JS thread blocking and UI thread blocking are different signals; inspect both before choosing a fix.

Android Profiling with Android Studio

Launch Profiler

Use Android Studio Profiler on the target device or emulator.

CPU Profiling

Record CPU hotspots while performing the suspect interaction, then inspect flame graph, bottom-up, and timeline views.

Analyzing Results

Flame Graph:

  • Zoom with scroll/pinch
  • Click to expand call stacks
  • Filter by keyword (e.g., "hermes")

Views:

  • Top Down: From entry points down
  • Bottom Up: From slowest functions up
  • Flame Chart: Timeline visualization

Reading the Call Stack

Example analysis:

JS Thread activity after button press:
- Event handler on main thread
- Triggers JS work via sync JSI calls
- Hermes processes React reconciliation
- Significant time in commit/layout-related work

Platform Tools Summary

| Tool | Platform | Use Case | |------|----------|----------| | Time Profiler | iOS | CPU hotspots | | Leaks | iOS | Memory leaks | | Hangs | iOS | UI thread blocks | | CPU Profiler | Android | CPU hotspots | | Memory Profiler | Android | Memory tracking | | Perfetto | Android | Advanced trace analysis |

Perfetto (Advanced Android)

Export traces from Android Studio and analyze at ui.perfetto.dev:

  • Cross-process analysis
  • Custom trace events
  • Additional visualizations

Expo Notes

  • Expo Go: Cannot profile native code directly; JS profiling only
  • Dev Client / Prebuild: Full native profiling supported via Xcode/Android Studio
  • Run npx expo prebuild to generate native projects, then profile as bare React Native

Common Findings

| Symptom | Likely Cause | |---------|--------------| | Main thread hangs | Heavy UI work, blocked operations | | JS thread spikes | React re-renders, heavy computation | | Background thread busy | Native module work | | Memory climbing | Leak (see memory profiling skills) |

Related Skills