How domylan/my-pets works
The mobile client built with Flutter (located in the “client” directory).
2. The admin web panel built with a modern JavaScript framework (in the “admin” directory, using React – note the .jsx files, SCSS styling, and organized component/pages).
Even though the backend folder isn’t clearly visible in the file tree, the README instructs running a “backend” process (via yarn commands) suggesting there is or will be a separate Node.js backend that exposes API endpoints. In addition, there is integration with third-party services such as the VNPAY payment gateway to handle secure transactions.
Main system components
• Mobile Client (Flutter): Represents the consumer-facing mobile application.
• Admin Panel (React): Acts as a web-based control interface for pet centers and management.
• Backend/API Server: Although not explicitly shown as a separate folder, treat this as the central server that handles business logic, database interactions, authentication, and third-party integrations.
• External Services: VNPAY (for secure payment processing) and any notification or social networking services the system may use.
• (Implicit) Database & Storage: This layer (not fully shown in files) would handle data for users, pets, orders, and other transactional details.
Relationships and interactions
• The Mobile Client and the Admin Panel both communicate with the Backend Server via RESTful APIs.
• The Backend Server handles authentication (possibly using token management as seen in admin/src/services/token.js) and business logic for pet transactions, user profile management, posts, notifications, etc.
• External integrations such as VNPAY are called from the Backend when processing payments.
• The Admin Panel also includes client-side state management (using Redux under admin/src/redux) and service layers (in admin/src/services/apis) for communication with the Backend.
• The Flutter client organizes its code into screens, services, and models which define the mobile UI, logic, and data structures; it similarly communicates with the backend.
Important architectural patterns
• Separation of Concerns: There is a clear separation between the front-end layers (mobile UI and admin web UI) and the centralized backend.
• MVC/MVVM-like organization: The Flutter client segregates UI (screens) from models and services; the admin panel organizes components, pages, routes, and Redux state.
• API Driven Architecture: Both front ends consume backend APIs. The services directories in both projects encapsulate REST API calls.
• Modular and Scalable: The detailed folder structures (for components, assets, routes, and services) indicate that the system is designed to be easily extended through clearly defined modules.
Technologies and frameworks
• Flutter & Dart for the client mobile application.
• React (with JSX) alongside Redux for the admin panel.
• Node.js (implied by yarn commands and npm scripts) for the backend server.
• SCSS for styling on the admin web interface.
• Third-party integrations like VNPAY for payments.
• Additional libraries for notifications, post and user management, and media (video/image uploads) in both client and admin.