How disaa0/eddys-tender-app works
Project Type and Purpose
• This is a full-stack mobile e-commerce application (“Eddy’s Tender App”) built with a React Native/Expo frontend, an ExpressJS/Prisma backend, and a MySQL database. It processes user actions (browse, cart, checkout), integrates with Stripe for payments, and uses Expo Push Notifications.
File Structure
• Top-level:
• frontend/ – React Native app (Expo) with pages under app/(app), app/(auth), app/(appAdmin), API service wrappers, context providers, hooks, components, assets.
• backend/ – Express API server with src/{config,controllers,middlewares,services,routes}, Prisma ORM schema & migrations, Dockerfile, docs for API/Stripe/notifications.
• mysql/ – Initialization SQL scripts & permission setup.
• docker-compose.yml – brings up backend, mysql, stripe-cli, (and possibly frontend if containerized).
• docs/ – high-level project reports.
README for Additional Insights
• Stack: ExpressJS + Prisma, MySQL, React Native/Expo
• Containerization: Docker Compose coordinates backend, MySQL, stripe-cli
• External services: Stripe API for payments, Expo push for notifications
• Architecture hints: clearly separated frontend/backend, API endpoints under /api, Prisma service layer.
Detailed Component Breakdown (to include
• Frontend:
• Pages: auth, user app, admin app
• State management: AuthContext, CartRefreshContext
• API clients: BaseApiService, AuthService, AdminApiService, etc.
• Backend:
• Config modules (bcrypt, JWT, crypto)
• Middlewares (auth, admin check, upload, input validation)
• Controllers grouped by domain (auth, cart, order, product, webhook, notification)
• Services mapping to controllers
• Prisma client module
• Database:
• Schema (User, Product, Order, Cart, Notification, ShippingAddress)
• Migration history
• Payments & Notifications:
• Stripe API (payment_intent) integration and webhook flow
• stripe-cli local listener
• Expo Push Notification flow