How phanthanhbach/food-ordering-app works
Project type and purpose
• This is a React Native mobile application (“Food-Ordering-App”) for ordering food.
• It targets iOS and Android (app.json, babel.config.js) and leverages Firebase (firebase.js) for backend services (authentication, database, storage).
File structure
• Top level files:
• App.js – root component
• navigation.js – app navigation configuration
• firebase.js – Firebase SDK initialization & wrappers
• src/components/ – reusable UI components (Header, BottomTab, HomeScreen subcomponents)
• src/screens/ – feature screens (SignIn, SignUp, Home, Menu, FoodDetail, Profile, Voucher, etc.)
• No custom backend code; Firebase acts as BaaS.
Key insights from README
• Course project for “Mobile Application Development.”
Main components
a. Mobile Client (React Native App)
• Presentation layer
– Screens (SignIn, SignUp, Home, Menu, FoodDetail, Profile, etc.)
– Reusable Components (Header, BottomTab, AboutUs, Offers, Slider, etc.)
• Navigation layer
– Stack & Tab navigators (defined in navigation.js)
• Service layer
– Firebase SDK wrapper (firebase.js)
b. Backend services (Firebase)
• Firebase Authentication
• Cloud Firestore (or Realtime Database) for menu items, orders, vouchers
• (Optional) Firebase Cloud Functions for order processing
c. External Dependencies
Relationships & interactions
• UI Screens ←→ Navigation
• UI Screens → firebase.js service calls → Firebase Auth / Firestore / Storage
• Asynchronous data flow: fetch menu data → render Menu screen; submit order → write to Firestore
• Real-time updates (if used) flow from Firestore → client listeners → UI
Architectural patterns & design principles
• Layered architecture (Presentation / Navigation / Services / Data)
• Component-based UI (React Native best practice)
• BaaS integration for rapid backend setup
• Separation of concerns: UI logic in screens & components, data logic in firebase.js