How ebrahimgad123/netflix_clone_reactnative_app works
Project type and purpose
• This is a React Native mobile application bootstrapped with Expo (“create-expo-app”) for browsing and saving movies.
• It uses file-based routing for screens (under the app folder), a Redux Toolkit store for state management, and calls out to an external movie API via a small service layer.
File structure
• Top-level “android” folder: the native Android project managed by Expo.
• “app” folder: file-based routing directory; each .tsx file or subfolder is a screen (index.tsx, profile.tsx, [id].tsx, etc.).
• “compoonent” (sic) folder: reusable UI components (FlatListComponent, HorizontalFlatList, SearchBox).
• “services”: api.ts (REST client), useFetch.ts (data-fetching hook).
• “store”: Redux Toolkit slice (savedMoviesSlice.ts), store setup (index.ts).
• Config files: babel.config.js, metro.config.js, tailwind.config.js, tsconfig.json, and .env for secrets.
README for additional insights
• Confirms it’s an Expo project using file-based routing.
• No custom backend—purely client side, fetching from external services.
• You “start” by running Expo, which spins up Metro and bundles JS for Android/iOS.
• Green for state management
• Orange for network/services
• Gray for native/Expo runtime
• Related files/folders in containers with light borders (e.g., group all “app/” screens).