How enatega/food-delivery-singlevendor works
Project type and purpose
• This is a full-stack, multi-module white-label food-delivery solution with three distinct client applications (Admin Dashboard, Customer App, Rider App) and a proprietary backend/API (Node.js + Apollo GraphQL) that connects to MongoDB and various external services.
• The Admin Dashboard (ReactJS) lets restaurant owners manage orders and riders. The Customer App (Expo/React Native) is for placing and tracking orders. The Rider App (Expo/React Native) is for drivers to accept and deliver orders.
File structure
• Top-level modules:
• Admin Dashboard/… (ReactJS + Reactstrap + Apollo client)
• CustomerApp/… (Expo/React Native + Apollo client)
• RiderApp/… (Expo/React Native + Apollo client)
• Each module has its own src folder with components, screens/views, Apollo setup, assets, i18n, config, and environment files.
• Root-level assets/, contributingGuides/, README.md, LICENSE, etc.
• No public source code for the backend; it’s closed/proprietary.
README for additional insights
• High-level architecture image: three clients all communicate with a single GraphQL API.
• Dependencies: Expo, React Native, ReactJS, Apollo GraphQL, ExpressJS, NodeJS, MongoDB, Firebase, Stripe, PayPal, Google Maps, Amplitude Analytics, email provider, OAuth (Facebook/Google).
Detail is key
• Four tiers: presentation (three clients), API, data, external.
• How localization, theme/context, and authentication plug into each client.
• Don’t omit push notifications, payment flows, or analytics events—they are critical to the solution.
• Review the high-level architecture image in the README as a starting reference and expand it with the internal folder structure and service integrations listed above.