How amineladrem/lotus-ncshack works
Project Type and Purpose
• Lotus is a full-stack, client-server healthcare platform:
• A Next.js dashboard (“lotusweb-master”) for pharmacies
• A Flutter mobile app (“Patient-App-Mob”) for patients
• A backend API (“BACKEND” folder—with Django REST or Node.js/Express)
• A relational database (SQLite in DEV, PostgreSQL in PROD)
• External AI service (Google Gemini via the Flutter package)
File Structure
• Top-level directories: BACKEND, Patient-App-Mob, lotusweb-master
• Backend: Django project (manage.py, apps, models, serializers, views, urls)
• Mobile: Flutter project (lib/, assets/, android/, ios/, linux/, macos/, windows/)
• Web: Next.js app (app/, components/, public/, config, Tailwind config)
• Config files: Django settings.py, Flutter pubspec.yaml, Next.js package.json
README for Additional Insights
• RESTful endpoints for login, suppliers count, meds sold, list meds, list suppliers
• Next.js uses fetch()/useEffect for real-time data
• Flutter calls HTTP APIs and directly integrates with an AI service
• Tech stack: Node.js/Express (or Django REST), PostgreSQL (or SQLite), Next.js/Tailwind, Flutter
Main Components & Their Relationships
A. Clients
1. Web Dashboard
– Next.js front end (React pages, Tailwind UI)
– Fetches JSON over HTTPS from the API server
2. Mobile App
– Flutter UI (Dart code)
– State managed via setState
– Calls backend REST endpoints for schedules, login, data
– Integrates directly with Google Gemini API for chatbot
B. API Server
– REST API (Django REST Framework or Express.js)
– Exposes endpoints (/login, /numsup, /medsold, /listmeds, /listsups)
– Handles business logic, authentication, data validation
C. Database
– DEV: SQLite (db.sqlite3)
– PROD: PostgreSQL (host: 127.0.0.1:5432)
– Stores Patients, Suppliers, Drugs, Inventory, Sales
D. External Services
– Google Gemini (via generative_model package in Flutter)
– (Optional) Firebase integrations if using firebase.py
– Geolocation/Pharmacy locator APIs
Flow:
[Web/Mobile Clients] ←HTTPS/JSON→ [API Server] ←SQL Queries→ [Database]
↕
[External AI Service]
Architectural Patterns & Design Principles
• Separation of concerns:
• Presentation (Next.js, Flutter)
• API/business logic (Django/Express)
• Data persistence (SQL)
• External integrations (AI, geolocation)
• RESTful design: clear resource-based endpoints
• MVC (in Django) or layered architecture
• Server-side rendering vs. client-side state for web