Native Development

Core Principles

Always request permission before native changes. Native code changes affect app stability, require native team review, and can impact both iOS and Android platforms. Follow the permission protocol for all native modifications.

Use Proxy fallback for missing native modules. Native modules may be unavailable during development, testing, or when running shared modules in regular React Native apps. Proxy with error handlers provides graceful degradation.

Wrap native modules with TypeScript interfaces. Direct NativeModules access lacks type safety. Create typed wrapper objects (SharedModules* prefix) that match native APIs for compile-time type checking.

Use NativeEventEmitter for native-to-JS communication. One-way async calls work for most native functionality, but bidirectional communication requires NativeEventEmitter for native-initiated events.

Why: Native development requires careful coordination between JS and native layers. These patterns ensure type safety, testability, error handling, and maintainability for React Native bridge code.

When to Use This Skill

Use these patterns when: