How jeetgoyal80/cropic-ai works
Project type and purpose
• This is a full-stack, mobile-centric agricultural aid system.
• Frontend: a Flutter mobile app (app/) for farmers to sign up, log in, submit claims, view crops, insights, profiles.
• Backend: a Python FastAPI service (Backend/app/) exposing REST endpoints for farmers and disease-prediction.
• ML component: a PyTorch model file (disease_model.pt) and Jupyter notebook (Ml_model/notebook/Training.ipynb) used for training and served by the backend.
• Database: managed in Backend/app/database/db.py (likely SQLite or PostgreSQL via SQLAlchemy/SQLModel).
File structure
• Top-level folders:
• app/ (Flutter mobile application)
• Backend/ (Python FastAPI backend)
• Ml_model/ (model training notebooks)
• app/: follows Flutter conventions
• android/ (native Android build)
• lib/ (Dart code: models, providers, screens, services, utils)
• Backend/app/: follows FastAPI conventions
• routers/ (API endpoints: farmers.py, predict.py)
• schemas/ (Pydantic DTOs)
• models/ (PyTorch model artifacts)
• utils/ (authentication and helper functions)
• database/ (connection and ORM setup)
• Configuration files: requirements.txt, pubspec.yaml, gradle files, etc.
README
• Minimal placeholder (“Let’s Started”).
Be detailed but avoid over-fragmentation
• Environment boundaries (Mobile, Backend, Database, Dev/Training).