Upaj farmer experience

We organised the revamp around three repeated tasks: observing the farm, checking mandi prices and finding relevant information. Monitoring, market information and a new notification structure belonged to that experience, rather than treating the visual refresh as a separate result.

Content had its own distribution choice. Rural creators and influencers contributed to the library. Videos longer than a minute used YouTube; shorter formats used a custom CDN. The choice connected content length, distribution and the mobile experience.

I joined information features and creator content with design, engineering and lifecycle communication. The programme addressed the route to useful information and the reason to return to it together.

Useful information still had to be reachable on constrained Android phones. Later portfolio material describes entry reducing from eleven steps to three, alongside attention to app size and cold-start behaviour. These were access changes, not a separately measured onboarding-conversion result.

The same later material describes crop-cycle triggers for notifications. The intended mechanism was to bring a farmer back when information became relevant. This is distinct from assuming that more prompts alone create a reason to return.

Platform monetisation remained in my remit. The historical result concerns the combined experience programme; it does not isolate revenue or engagement effects for one notification, content format or entry change.

For another retention problem I would begin with the task worth repeating, then inspect the effort between the user and that task. In Upaj, farm information, market prices and content gave that investigation a concrete starting point; lifecycle messages helped people reach it.