How josinaldojunior/code_shopping works
Project type and purpose
• This is a full-stack application built in three layers:
• A Laravel back-end (REST API + MVC + Firebase integration)
• An Angular single-page web client (_angular-app)
• An Ionic mobile client (_whatsapp)
• Purpose: provide CRUD operations (products, categories, users, chat groups) via a Laravel API, web administration via Angular, mobile chat/messaging via Ionic + Firebase.
File structure
• Top-level directories:
• app, routes, database, config, resources, public → Laravel back-end
• _angular-app → Angular front-end
• _whatsapp → Ionic (Angular) mobile front-end
• Key patterns:
• Laravel follows MVC: Models (app/Models), Controllers (app/Http/Controllers), Resources (app/Http/Resources), Middleware, Events/Listeners
• Angular uses modules, components, services (src/app/services/http, guards, directives, pipes)
• Ionic uses pages, components, providers, Firebase config
• Config & build files:
• composer.json, webpack.mix.js → back-end build
• package.json, angular.json → Angular build
• package.json, config.xml, webpack.config.js → Ionic build
README
• Brief: “Projeto do curso Laravel-Angular-Ionic” confirms learning integration of Laravel API + Angular web + Ionic mobile.
Elements
• Green for API
• Orange for DB
• Purple for Firebase services
Detailed breakdown
• UI Components
• HTTP Services & Interceptors
• Routing & Guards
• Pages (chat, login, home)
• Providers (auth, chat-group-viewer, storage-permission)
• Firebase config
• Laravel API subdivided into:
• Controllers (Api/*)
• Models & Resources
• Events & Listeners
• Middleware (Auth, Cors)
• Data Layer:
• MySQL schema (users, products, chat_groups, etc.)
• Firebase Realtime DB / Firestore for chat messages
• FCM for notifications