DevPlant

Smartphone-based early detection of crop pests and diseases. Photograph one leaf, and the phone tells you whether it looks healthy, names the likely disease or pest, rates how severe it is, and suggests treatments. Everything runs on the phone, offline.

Status: early preview (v0.1.1). This build shows the architecture working end to end. No trained AI model is bundled yet: diagnosis uses a simple colour-based stand-in that can only tell "healthy", "leaf spot" and "yellowing" apart. Do not rely on it for real crops.

Try it

Download DevPlant-v0.1.1.apk from the Releases page and install it on an Android 10+ phone (you may need to allow installing apps from your browser or file manager).

iPhone: the mobile/ folder is the same app in JavaScript (Expo). Install Expo Go on the iPhone, double-click mobile/START-WINDOWS.bat or mobile/START-MAC.command on a computer, and scan the QR code. See mobile/README.md.

Architecture

Four Gradle modules, with import rules enforced by the build:

Module	Role	Depends on
mixes	The screens. Draws the interface and nothing else.	contracts
contracts	The abstraction layer: interfaces and plain shapes.	nothing
app	The bridge. Implements the contracts with the gates and picks which gate to use.	all three
gates	The tools: database, leaf photos, on-device AI model. Runs fully offline.	nothing

mixes never touches gates; gates and contracts import nothing of ours; app is the only place that knows both sides. The design decks are in the repo root (DevPlant_architecture (2).pptx, DevPlant_tree.pptx).

One scan, from leaf to diagnosis

1. mm_scan: the camera frames one leaf. The photo stays on the phone.
2. mm_data Store.scan: forwards the photo to ScanStore.
3. app_rules LeafPictures: turns it upright, crops it square, resizes it for the model.
4. gates gm_model: the on-device model returns top labels with confidence.
5. app_rules DiagnosisRules: picks pest or disease, severity and treatment; low confidence asks for a retake.
6. app_db → gm_db: scan and diagnosis rows are written; Changes refreshes History and Alerts.

The model is chosen in one line in app/.../wiring/AppServices.java:

model = TfliteModel.open(context, "devplant_v1");

To use a trained model, put devplant_v1.tflite and devplant_v1.labels.txt (one label per line, matching the guide keys such as late_blight, fall_armyworm, or healthy) in gates/src/main/assets/.

Screens (mixes)

mm_shell (header, pager, island) · mm_theme · mm_scan · mm_result · mm_library · mm_history · mm_fields · mm_alerts · mm_dashboard · mm_search · mm_settings · mm_data

Database (gates/gm_db)

Room, 8 tables: Crop, Field, Scan, Diagnosis, Disease, Pest, Treatment, Alert. Seeded on first run with 6 crops, 14 diseases, 7 pests and their treatments; entries added in a later version are added to existing installs on the next start.

Plant catalogue (cloud/)

The Catalog page lists 600 plants with photos and 4 common problems each. They come from the cloud/ folder, deployed on Vercel (see cloud/README.md). The app downloads the catalogue once, keeps it, and saves each photo the first time it is shown, so it then works offline. The site address is one line in gradle.properties: devplant.catalogUrl.

gates/gm_http (WebFiles) is the only gate that goes online; app_http/CloudPlantCatalog implements the PlantCatalog contract with it; mixes/mm_catalog draws it.

Reports (from the CropGuard design)

Every scan is also filed as a report: crop, area, result, how sure, where the result came from (simulated, AI model or expert), verification status (reported, under review, field verified) and sync status (on this phone, waiting to send, sent). A photo the rules ask to retake is kept as an uncertain report instead of being thrown away. Reports sit beside the scans and never change them:

• contracts: Report, Question, Consent, ReportStore, ReportServices (next to Services, which is unchanged)
• gates/gm_reports: their own Room file, devplant_reports.db (reports and questions), and the sharing choice; gates/gm_http/JsonHttp for the officer service
• app/app_reports: ReportingScanStore wraps RoomScanStore and files the reports; ReportSync sends them
• mixes: mm_reports (My reports, from the menu), mm_welcome (first launch: what stays on the phone, and whether to share report details; photos are never shared) and mm_help (ask an extension officer, from the result screen and My reports)

With sharing on, report details go to the officer service in cloud/ (the same site as the catalogue) whenever the phone has signal: at app start, after a scan or a question, and when My reports opens. Officers review them on the dashboard at /officer/; the status, the officer's note and answers to questions come back to the phone. Asking about a report sends that report even with sharing off, because the farmer chose to. The JavaScript app mirrors all of this in bridge/reports.ts, gates/reportsStorage.ts, gates/reportSender.ts, app/reports.tsx, app/welcome.tsx and app/help.tsx.

Planned

app_http (regional outbreak alerts back to farmers) · app_security (sign-in) · app_notify (push alerts) · gm_location (GPS for fields).

Build

Requires Android Studio (or the Android SDK) and JDK 21.

./gradlew :app:assembleDebug        # debug APK
./gradlew test                      # unit tests

Release builds are signed only when a keystore.properties file (not in the repo) provides storeFile, storePassword, keyAlias and keyPassword.

Fortland Android preview

Fortland is a separate Android app. Download the latest Fortland 1.5 test build. Release notes. This APK is debug-signed; installing it over a release-signed version may require uninstalling the older app first, which removes its local data.

Disclaimer

Treatment advice is general. Confirm serious problems with a local agricultural extension officer and always follow product labels for any chemical.