MonaWork: How We Built a 5-Star Enterprise Field Operations App in 12 Weeks

The Brief: A Global Engineering Company's Field Operations Problem

Monadelphous is a global engineering services company with operations across Australia, Papua New Guinea, and Southeast Asia. Their field workforce — maintenance technicians, construction supervisors, and safety officers — was managing job cards, timesheets, safety checklists, and photo evidence on paper. The problems were predictable: lost paperwork, delayed payroll, compliance gaps, and no real-time visibility for project managers.

The brief to Swaran Soft was clear: build a mobile application that digitises field operations end-to-end, integrates with their existing SAP Plant Maintenance module, works offline in remote sites with poor connectivity, and is intuitive enough for field workers with varying levels of digital literacy to adopt without extensive training. Timeline: 12 weeks. Budget: fixed-fee. Quality standard: App Store ready.

The result was MonaWork — a React Native enterprise mobile application that launched with a 4.8-star App Store rating, 94% field worker adoption in week one, and outcomes that transformed Monadelphous's field operations.

The Discovery: Understanding the Field Worker's Reality

The most important investment in the MonaWork project was the two weeks spent in discovery — not in a conference room, but in the field. Swaran Soft's UX team shadowed field workers at two Monadelphous sites, observing how they actually worked: the sequence of tasks, the information they needed at each step, the frustrations with existing paper processes, and the moments where digital tools would genuinely help versus get in the way.

Three insights from discovery shaped the entire product: First, field workers needed to complete job cards with one hand (the other was often holding a tool or a safety rail). This meant large touch targets, minimal typing, and heavy use of pre-populated dropdowns and photo capture. Second, connectivity was genuinely unreliable — not just slow, but completely absent for hours at a time. The app had to work fully offline and sync intelligently when connectivity returned. Third, the single biggest pain point was not the job card itself, but the photo evidence requirement — workers had to photograph completed work for compliance, but the existing process (WhatsApp to supervisor, supervisor emails to PM, PM uploads to SharePoint) was broken and slow.

The 12-Week Build: Week by Week

The Technical Architecture: Built for the Field

The technology choices for MonaWork were driven entirely by field realities, not engineering preferences. The offline-first architecture was the most technically challenging aspect of the build. WatermelonDB — a high-performance React Native database — was chosen for its ability to handle thousands of records locally and sync efficiently with the backend when connectivity was available. A custom conflict resolution engine handled the inevitable scenario where a supervisor edited a job card on the web portal at the same time a field worker updated it on the app.

The Outcomes: Numbers That Matter

What Made the Difference: The Lessons

The 4.8-star App Store rating and 94% adoption rate in week one did not happen by accident. Three decisions made the difference. First, the two weeks of field discovery — which the client initially wanted to skip to save time — were non-negotiable. The offline-first architecture, the one-handed UX, and the photo workflow redesign all came directly from field observation. Without discovery, we would have built a digital version of the paper form, not a tool that genuinely changed how field workers operated.

Second, the user testing in weeks 3–4 with actual field workers — not office staff — surfaced 23 UX issues that would have caused adoption failure. The most critical: the initial design required workers to type in asset IDs. Field workers told us they never knew the asset ID — they knew the asset by its physical location and a painted number on the machine. We redesigned to QR code scanning and location-based asset lookup. That single change reduced job card initiation time from 4 minutes to 45 seconds.

Third, the 12-week fixed-fee model forced discipline. Every feature request was evaluated against the core brief: does this help a field worker complete their job faster and more accurately? Features that did not pass that test were deferred to a future release. The result was a focused, fast, reliable app — not a feature-bloated one that nobody used.