How christophe-chausseray/camps-react-native-app works
Project type and purpose
• This is a full-stack mobile client (React Native) whose sole responsibility is to fetch and display camping sites around Paris on iOS and Android. It does not include the backend source code, but relies on an external GraphQL API and the Google Maps API.
File structure
• Top-level platform folders:
• android/ – Android native project (Java, Gradle, native modules)
• ios/ – iOS native project (Objective-C/Swift, Xcode, CocoaPods)
• src/ – JavaScript/TypeScript client code
• ApolloClient.ts – Apollo GraphQL client setup
• components/ – reusable UI pieces (Header, etc.)
• views/ – feature screens, separated into Camping/List and Camping/Details
• models/ – TypeScript types for domain objects (e.g. campingItem)
• mocks/ – Apollo mocks for tests
• App.tsx, index.js – application entry point and root component
• Config & infra: metro.config.js, babel.config.js, tsconfig.json, .env.dist, GitHub Actions workflows in .github/workflows/
README for additional insights
• Uses React Native CLI (Metro bundler + Babel)
• Uses Apollo Client to fetch from a GraphQL endpoint (CAMPS_API_HOST)
• Integrates Google Maps via a JS API key
• Testing with React Native Testing Library + Apollo MockedProvider
• CI: GitHub Actions triggers lint, tests, builds; deploys documentation to GitHub Pages
Essential architectural elements
• Don’t just show screens; show how they hook into Apollo, how the network layer is configured, and how native modules (maps) integrate
• Bundler step (Metro) and the build pipelines for each platform
• Testing & CI as part of the overall system lifecycle
• Environment variable injection (.env → Google Maps API key, CAMPS_API_HOST)