Research & innovation

What works in this field?
And how do we know?

A recommendation is only as useful as its evidence and context. KishKam’s research connects farmer observations, traditional practices and scientific findings while keeping their sources and limitations visible.

Three questions guide our research.

⌁

Agricultural knowledge

Document the practice, crop, season and observed outcome. Preserve the difference between a farmer’s experience, a research finding and an untested hypothesis.

◌

Sensing & autonomous systems

Investigate sensing, navigation and multi-agent coordination around defined agricultural tasks and realistic operating conditions.

↗

Field evidence

Use consented observations and appropriately designed trials to evaluate usefulness. Record uncertainty and negative results alongside promising findings.

Engineering note · development, not field results

Before advice, make the record reliable.

The question

Can a diary preserve enough field and activity context to support useful questions later?

Current work

The prototype has field and diary screens. Authentication endpoints and database migrations have passing development tests. Connecting the complete farmer workflow is still in progress.

What is not established

Screen designs and software tests do not demonstrate farmer adoption, improved yields or field readiness. Those questions require pilot feedback and documented evaluation.

See development milestones →
Evidenced Development Note · Note 01

Field Diary Workflow & Offline-First Schema

Author: Kirankumar Malothu · Date: 14 October 2026 · Status: Prototype Development

1. Evaluated Workflow

We evaluated a core three-stage record workflow in the KishKam Field prototype: field profile initialization, daily activity entry (sowing, irrigation, inputs, pest observations), and local-first data caching.

KishKam Field development screen sheet showing onboarding, accounts, fields and diary interfaces
Figure 1: Current development interface showing account setup, field listing, and activity logging flows.

2. Observed Performance

Local in-memory and SQLite records allow immediate entry without network delay. Sowing and irrigation logs capture date, crop type and field association reliably in test environments.

3. Technical Limitations

Testing is currently limited to development emulators and simulated records. Sync conflict resolution under intermittent rural connectivity has not been field-tested. The prototype does not yet provide agronomic validation, yield predictions, or spray advice.

4. Next Evaluation Step

Conduct structured usability sessions with 5–10 farmers to measure data entry completion rates, Telugu text readability, and offline synchronization stability under actual rural network constraints.

Research notes

Show the source.
Explain the limits.

Future research notes will explain the question, method, source and limitations—not just the result. Publications and engineering demonstrations will carry clear attribution; field findings will appear when there is evidence to report.

Interested in collaborating on agricultural research, field trials, or intelligent automation? Start a conversation →