react-native

To structure React Native components effectively, extract screen logic into custom hooks so functional components remain simple, explicit, and easy to test. This separation keeps presentation clean and reusable while making presentation logic straightforward to test and refactor.

The best way to manage state in React Native is to use local state first, then scale to Zustand or React Query when needed. This approach prevents premature complexity and ensures state management guidance matches your app's actual data fetching requirements.

Handle platform-specific code in React Native by using selective code branches or separate files for iOS and Android variants. This strategy enforces explicit props and stylesheet-based styling to avoid anti-patterns and maintainable cross-platform apps.

Yes, you can use Zustand and React Query together for state management in React Native. The Skill provides state management guidance to scale from local state to these libraries, ensuring your custom hooks and functional components maintain clear separation of concerns.

React Native screen code becomes hard to maintain when business logic mixes with presentation. Extracting logic into custom hooks and enforcing explicit props creates testable presentation logic and stylesheet-based styling, avoiding anti-patterns for maintainable cross-platform apps.

No, you do not need separate files for every platform-specific React Native component. You can handle iOS and Android differences using selective code within a single file, applying explicit props and stylesheet-based styling to ensure maintainability and avoid anti-patterns.