Panen Raya icon

Custom app · Demo · Business · 2026

Panen Raya

A demo internal tool for a union of smallholder cooperatives in West Kalimantan: an offline Android app for field officers weighing palm fruit bunches and rubber at the plantation, plus a head-office web dashboard for prices, stock, trucks, and farmer payouts.

Panen Raya

Tap around: buttons, tabs and cards work like the real app. Want one like this? Message us →

Build something like this
Panen Raya, screens 1

What it does

  • Works fully without signal, with a sync queue and conflict handling
  • Scan a member card to open the farmer's profile and plots
  • Bluetooth scale, fruit grading, and rubber content on one receipt
  • Thermal receipt printing with a verification code
  • Daily price board by tree age and rubber content
  • Payout batches with fertilizer credit deductions and tiered approval

Panen Raya is a self-initiated demo by Wailo, not a client project. We imagined a union of smallholder cooperatives in Sanggau, Sekadau, and Landak buying fresh palm fruit bunches and rubber from hundreds of members. In places like this, weighing slips are often still handwritten, prices by tree age are easy to dispute, payouts can take weeks, and there is barely any signal out in the plantations.

The field app is designed to be used in harsh daylight: high contrast, large numbers, wide buttons, and one task per screen. An officer scans the member card, reads the weight straight from a Bluetooth scale, records grading deductions or the rubber's dry rubber content, then prints a thermal receipt with a verification code, so the farmer leaves with proof that matches what the server will hold. The head-office dashboard is denser: a stock map of collection points with overdue-fruit warnings, truck dispatch to the mills, a daily price board by tree age and rubber content, and payout batches with tiered approval.

Technically, the Android app would be built with Kotlin and Jetpack Compose, with Room as the on-device source of truth. Every transaction is saved locally first, queued, and sent when a signal appears; conflicting edits, such as a farmer's bank account changed both at the office and in the field, are never silently overwritten but surfaced as a conflict to resolve. The dashboard uses Next.js and PostgreSQL, and payouts go to the bank as a bulk transfer file through a generic integration.

Next we would test the weighing flow with real field officers: how quickly a single receipt can be completed, whether thermal prints stay legible after rain, and how farmers read the fertilizer credit deduction on their receipts.

Build something like this

One message is enough to start. We reply with a clear scope, a cost range, and a timeline.

← See all work