Makna โ Subsidized Fertilizer Transaction App
A dual-user mobile app serving millions of farmers and kiosk operators across Indonesia for the national subsidized fertilizer program.
Role
UI/UX Designer
Timeline
2024
Platform
Mobile (Android & iOS)
The Problem
Indonesia's subsidized fertilizer program serves millions of farmers nationwide, but the transaction process was largely manual โ creating inefficiencies, verification bottlenecks, and limited visibility into distribution data.
Design a mobile app for two very different user groups โ rural farmers with limited digital literacy, and kiosk operators managing high-volume daily transactions โ while navigating complex subsidy rules across multiple fertilizer types.
Two Users, One Platform
Farmers (Subsidy Recipients)
Often first-time smartphone users. Located in rural areas with varying connectivity. Interact with the app infrequently (seasonal purchasing patterns) and need flows that work without prior digital experience.
Kiosk Operators (Agricultural Distributors)
Process dozens of transactions daily. Need to verify recipient eligibility via QR scan. Need speed and efficiency above all โ throughput is their primary constraint.
Registration with Biometric Verification
The 5-step registration flow (Input NIK โ Foto KTP โ Liveness โ Foto โ Buat PIN) includes biometric liveness detection for identity verification. Step indicators give users a sense of progress and prevent abandonment. Large, simple PIN creation UI is designed for users unfamiliar with mobile security concepts.
Key Design Decisions
Simplicity as Principle, Not Just Aesthetic
Maximum 2 actions per screen. Bottom-anchored primary buttons (thumb-reachable). Confirmation dialogs before any irreversible action. The subsidy calculation logic lives entirely in the system โ users see final prices, not formulas.
The Receipt as a Share-Ready Artifact
The transaction receipt screen is designed for screenshot-sharing โ a common behavior in the target demographic where users share proof via WhatsApp. Clean typography, clear totals, prominent "Cetak" (Print) CTA.
Outcome
Designing for low-literacy users is not about dumbing things down โ it's about being precise with visual hierarchy, ruthlessly cutting unnecessary steps, and letting the system handle complexity so the user doesn't have to.