Bijak
Three marketplace apps. One reusable engine.
The brief, in a paragraph.
Bijak operates India's largest agri-trading platform connecting farmers, traders, and buyers. Their suite of three marketplace apps needed rapid feature development to stay ahead in a competitive market. The apps faced usability friction in trade flows, lacked real-time pricing updates, and needed better alignment between user needs and product features. The development velocity needed to increase without sacrificing quality.
Every project has a story before it has a solution. Here's the part nobody writes on the case-study cover.
Three apps moving at three different speeds.
The apps faced usability friction in trade flows, lacked real-time pricing updates, and needed better alignment between user needs and product features. Three personas — farmers, brokers, and field agents — each had their own app, and feature velocity was uneven, code was duplicated, and product-user alignment was slipping.
- 0115+ features stacked up in backlog across three apps
- 02State management drifting between BLoC and ad-hoc patterns
- 03Real-time pricing required across all three surfaces
- 04Field-agent demographics needed visual storytelling at scale
Modular components, GetX state, agile delivery.
Integrated 15+ new features across three marketplace applications, focusing on streamlined trade flows and real-time pricing mechanisms. Implemented GetX state management for reactive data handling and built modular, reusable components to accelerate development across all three apps. Worked closely with the product team in agile sprints to prioritize features based on user research data.
GetX over BLoC for this domain
Marketplace data is highly reactive — prices, listings, location. GetX gave the simplest mental model for this shape.
Modular component library
Built 20+ reusable widgets shared across all three apps. New features now ship by composition, not duplication.
Real-time pricing
Subscription-based price updates from the trade engine. UX optimized for low-bandwidth villages.
Agile cadence with product
Two-week sprints with clear demos, prioritized by aggregated user research data, not by HiPPO.
A platform that ships across three apps simultaneously.
The component library became the secret weapon. New features now compose from existing primitives — design, code, and tests carry over.
- 0120+ reusable widgets across three apps
- 0215+ features delivered across 6 months
- 03Brokerage workflow rebuilt for high-volume bulk trades
- 04Agent app gained demographics + sell-comparison views
- 05Sprint velocity up 40% by month four
The numbers, after the dust settled.
Across all three apps in six months, measured by feature surface.
Story points delivered per sprint, sustained through quarter-end.
Measured via product-driven user research and post-release telemetry.
Across three marketplace surfaces, all live in production.
What changed, measured.
| Metric | Before | After |
|---|---|---|
| Sprint velocity | Baseline at engagement start (month 1) | +40% by month 4, sustained through quarter-end |
| Reusable component library | 0 shared widgets — UI duplicated across 3 apps | 20+ shared widgets, new features compose instead of duplicate |
| Backlog of cross-app features | 15+ features stalled across three apps | All 15+ shipped across 6 months |
| User-feature alignment | Product calls driven by HiPPO opinion | +25% alignment, measured via research data and post-release telemetry |
What it's built with.
- Flutter
- Dart
- GetX
- Hooks
- Kotlin
- Java
- REST APIs
- Firebase Analytics
- AWS
- Agile
- Sprint Reviews
- User Research
From the blog.
Building E-Commerce Apps with Flutter: Features, Cost & Best Practices
A complete guide to building e-commerce and marketplace apps with Flutter, covering essential features, payment integration, architecture best practices, cost breakdown, and real-world experience from the Bijak agricultural marketplace.
How I Ship Flutter MVPs in 6 Weeks (Real Timeline from 20+ Projects)
A week-by-week breakdown of my proven Flutter MVP process — from kickoff to App Store submission in 6 weeks. Real deliverables, real trade-offs, real numbers.
“Yashraj adapts seamlessly to different processes and demonstrates strong problem-solving skills, especially in rapid bug fixing.
I build Flutter apps, Next.js websites, and full-stack products for ambitious teams.
Got a problem with this shape?
Most engagements start with a thirty-minute conversation. Tell me what you're building and what hurts.