Complete Date-Palm Farm System
Budget: $250 – $750 USD
I already have a working prototype, a tested PostgreSQL backend with a REST API, and a complete clickable UI design (web + mobile) with a written style guide. I need a developer to take it over the finish line so our date-palm farm runs entirely from one platform.
The core still missing is the operational layer wired end-to-end. Each palm must move through registry → daily operations → harvest → sales without a hiccup, recording every step of the cycle (pollination, thinning, bagging, harvest, sorting) while keeping data consistent across browser, Android and iOS on ONE PostgreSQL database. The system is unified by two shared keys: a Tree ID (before harvest) and a Lot ID (after harvest); harvest hands the key from tree to lot.
Pollination, harvest and sorting are the most critical touchpoints, so they must be rock-solid and fast to log in the field, immediately reflected on the management dashboard.
You will receive: a working prototype, the PostgreSQL schema, 30 business rules as editable JSON (rules are data, not code), a unified palm registry, a full clickable HTML design + style guide (note: design is HTML, not Figma), and a partially built API.
Deliverables — a deploy-ready bilingual web app (Arabic RTL + English) plus store-ready iOS + Android builds for all roles, covering:
Palm registry with CRUD and QR/Tree ID scan lookup
Operation scheduler & logger for the full cycle, driven by the rules engine
Harvest lot creation (Lot ID), weight capture and real-time stock
Sales module: harvest lots → invoices, payment tracking
Role-based login (hashed passwords + JWT)
7 report types (production, worker productivity, variety/lot revenue, inventory, sales, receivables aging, daily harvest) with PDF/Excel export
Deployment onto a server I own + a basic test suite
Stack is flexible if it respects the existing API: React / React Native or Flutter front end, Node/NestJS back end integrate quickest; solid alternatives considered. Then we go straight to pilot, so clean code and concise documentation are part of acceptance.
The core still missing is the operational layer wired end-to-end. Each palm must move through registry → daily operations → harvest → sales without a hiccup, recording every step of the cycle (pollination, thinning, bagging, harvest, sorting) while keeping data consistent across browser, Android and iOS on ONE PostgreSQL database. The system is unified by two shared keys: a Tree ID (before harvest) and a Lot ID (after harvest); harvest hands the key from tree to lot.
Pollination, harvest and sorting are the most critical touchpoints, so they must be rock-solid and fast to log in the field, immediately reflected on the management dashboard.
You will receive: a working prototype, the PostgreSQL schema, 30 business rules as editable JSON (rules are data, not code), a unified palm registry, a full clickable HTML design + style guide (note: design is HTML, not Figma), and a partially built API.
Deliverables — a deploy-ready bilingual web app (Arabic RTL + English) plus store-ready iOS + Android builds for all roles, covering:
Palm registry with CRUD and QR/Tree ID scan lookup
Operation scheduler & logger for the full cycle, driven by the rules engine
Harvest lot creation (Lot ID), weight capture and real-time stock
Sales module: harvest lots → invoices, payment tracking
Role-based login (hashed passwords + JWT)
7 report types (production, worker productivity, variety/lot revenue, inventory, sales, receivables aging, daily harvest) with PDF/Excel export
Deployment onto a server I own + a basic test suite
Stack is flexible if it respects the existing API: React / React Native or Flutter front end, Node/NestJS back end integrate quickest; solid alternatives considered. Then we go straight to pilot, so clean code and concise documentation are part of acceptance.