jutsu-react-native:react-native-platform

Use React Native's Platform API to detect the OS and conditionally execute code paths. Platform.OS returns 'ios' or 'android', allowing you to branch logic, import platform-specific modules, or use Platform.select() to return platform-specific values in a single expression.

Yes. React Native supports platform-specific file extensions: name your files Component.ios.tsx and Component.android.tsx, then import Component generically. The bundler automatically selects the correct file. Provide a shared Component.tsx as a fallback for unsupported platforms.

Use file naming conventions (Component.ios.tsx, Component.android.tsx) for complete platform divergence, or use Platform.select() within a single file for minor differences. Combine these patterns: platform-specific files for substantial differences, Platform.select() for tweaks to shared logic.

Import platform-specific native modules using the same file-naming convention as components. Wrap permission requests in Platform.OS checks to call iOS-specific APIs (e.g., requestCamera) or Android equivalents, respecting each platform's permission model and safe-area requirements.

Android's hardware back button requires explicit handling via Platform.OS checks or the BackHandler API, while iOS relies on gesture-based navigation. Detect Platform.OS === 'android' and configure back-button logic separately to prevent unintended app exits.

Avoid hardcoding platform assumptions in shared components. Use Platform.OS consistently for detection, test both platforms thoroughly, and remember that safe areas, permission flows, and navigation patterns differ significantly between iOS and Android.