How We Built AgriSense NZ — A Farm Management App for Kiwi Farmers
New Zealand farmers run some of the most sophisticated agricultural operations in the world. But the tools they use to manage those operations haven't kept up. AgriSense NZ was built to close that gap.
22 April 2026
New Zealand farmers run some of the most sophisticated agricultural operations in the world. But the tools they use to manage those operations haven't kept up. Spreadsheets, paper notebooks, and generic farm apps built for overseas markets leave a gap that Kiwi farmers have been quietly working around for years.
AgriSense NZ was built to close that gap.
The Problem
Walk onto most New Zealand farms and you'll find the same pattern: a clipboard in the shed, a whiteboard in the kitchen, and three or four disconnected apps trying to track what's happening across the operation. Calving dates in one place. Drench records in another. Shed inspections on paper, re-entered later if at all.
The existing tools either came from overseas — built for American feedlots or Australian station work — or were locked into a single farm type. Dairy-only. Sheep-only. Nothing that understood the realities of a mixed Southland operation or the specific compliance requirements of NZCP1 and NZCP2.
Farmers deserved better. So we built it.
Why a Southland Studio
Vivura Studio is based in rural Southland. That matters. Building for farmers is not a market segment we researched — it's the community we live in. We've seen firsthand how rural broadband behaves, why offline-first design isn't optional, and why an app that assumes a city user's context will fail the moment it hits a milking shed.
Proximity to the problem shaped every design decision. AgriSense isn't an app about farming. It's an app built from inside the farming community.
The Tech Stack
AgriSense runs natively on iOS, Android, and the web — not as a cross-platform compromise, but as three dedicated experiences sharing a common backend.
- iOS: Swift and SwiftUI, using modern iOS patterns for performance and platform integration.
- Android: Kotlin with Jetpack Compose, giving us a fully native Android experience rather than a watered-down port.
- Web: Flutter for the browser-based farm manager console.
- Backend: Firebase and Firestore for real-time sync, offline support, and scalable document storage.
- AI assistance: An in-app help assistant powered by Firebase Cloud Functions and the Anthropic API, giving farmers contextual answers without leaving the app.
Choosing native over hybrid meant more work. It also meant a faster app, better platform integration, and a product that feels at home on every device a farmer might pick up.
Key Features
AgriSense covers the full breadth of a modern NZ farm operation:
- Flock and herd management across dairy, sheep, beef, and mixed farms
- Lambing and calving records with event tracking and historical data
- Health, drenching, and animal welfare logging
- Wool records and kill sheet tracking
- Shed inspection module aligned with NZCP1 and NZCP2 requirements
- Milking journal for daily operational records
- Infrastructure planning with interactive farm mapping
- Stocking rate calculator and other decision-support tools
- AI-powered help assistant for in-app guidance
Each module was shaped by conversations with actual farmers, not assumptions made from a desk.
The Hard Parts
Honest reflection: this was not a simple build.
Launching on the Google Play Store meant navigating a moving target of technical requirements, including the 16KB memory page size rollout that forced architecture changes mid-development. The App Store required careful handling of Sign in with Apple and authentication flows. Firebase debugging — including some memorable crashes tied to Firestore document IDs — taught us the value of defensive coding in a real-world data environment.
Multi-platform sync is genuinely hard. Designing an offline-first architecture that handles patchy rural internet, reconciles conflicting edits from multiple devices, and still feels instant to the user is the kind of problem that keeps you up at night until it clicks.
We solved these problems not by cutting corners, but by accepting that production-grade apps take production-grade effort.
What We Learned About Building for a Specific Audience
Building AgriSense reinforced something we already believed at Vivura Studio: the best products come from deep understanding of a specific user, not broad appeal to a generic one.
Farmers don't want a beautiful app. They want an app that works in gumboots, with cold hands, in a cow shed, on a 3G connection. That constraint shaped every interface decision. Large tap targets. High-contrast design. Minimal navigation. Offline-first by default. Features named in language farmers actually use, not the language an urban designer thinks they use.
The lesson is portable. Whether we're building for farmers, retailers, service businesses, or any other audience, the same principle applies: know your user better than your competitors do, and build accordingly.
What's Next
AgriSense is live on both the App Store and Google Play, with an active roadmap. We're currently expanding the sheep and beef functionality through a multi-phase rollout covering flock management, lambing, health and drenching, wool, and kill sheet tracking. The Shed Inspection module continues to evolve alongside NZ compliance requirements.
New features ship regularly. The app gets better every release because the farmers using it keep telling us what's missing.
Need Something Similar Built?
AgriSense NZ is what happens when a design and development studio commits deeply to solving a specific problem for a specific audience. The same approach applies to any serious product build.
If you're thinking about an app, a platform, or a digital product for a distinct industry or customer base — one that needs to be built right, not just built fast — we'd love to talk.
