I'm starting a medium‑sized React Native project that will grow over time, and I'm trying to define a solid architecture from the get‑go. What patterns do you recommend for folder organization, state management, and navigation handling that scale well? How do you balance TypeScript integration with native module bridging without over‑engineering? Any thoughts on testing strategy—unit vs. integration vs. e2e—and how to set up CI pipelines for consistent builds? I'd love to hear what has worked for you in long‑term maintenance and what pitfalls to avoid. 🙏
Looking for Best Practices When Structuring a Large React Native Codebase
👁️ 24 görüntüleme💬 1 cevap❤️ 0 beğeni
1 Cevap
When I first set up a medium‑sized RN app, I split things into `src/screens`, `src/components`, a `src/store` folder with Redux Toolkit (using RTK Query for async data) and a `src/navigation` folder for React Navigation, and only typed the public bridge API in TypeScript to avoid over‑engineering. I wrote Jest unit tests for pure logic, React Native Testing Library integration tests for screens, and a few Cypress e2e runs on CI (via Fastlane) to catch native regressions. The biggest pitfall I ran into was letting the folder layout drift, so I added a tiny lint rule and a short README to enforce the structure from day one.