Your Dunedin field team loses coverage the moment the van rounds Portobello, and the app forgets everything
A custom mobile app for a Dunedin research group, health provider, or field operation runs NZ$60,000 to NZ$160,000 over 4 to 8 months. No-code builders and template apps assume a connection. Drive out along the Otago Peninsula, up onto the Taieri, or inland toward Middlemarch and the connection goes, which is exactly where your team is collecting data. An app that syncs on arrival back in town is a different piece of engineering from one that posts a form to an API, and that difference is most of the budget.
Your team already worked around this. They take paper into the field, or they type into Notes, or they photograph a form and transcribe it that evening in the office. The data is good, it just arrives a day late, incomplete, and with no reliable link between the photo, the participant, the location, and the time. When someone asks a question of the dataset six months later, the answer involves finding a person who remembers.
The template app builders fall over on three things specific to this work. They have no genuine offline write model, so a form filled at Taiaroa Head is lost when the app is backgrounded. They have no consent model, so you cannot record what a participant agreed to, when, and in which version of the information sheet. And they have no path to talk to instruments, which matters in a city where a good share of the interesting work involves a device on a bench or a sensor in a paddock rather than a person typing. Once you need any of those three, you are building.
Where the off-the-shelf tools fall short
- Data captured in the field is transcribed in the evening, so errors are found days later and often cannot be corrected at source
- Consent and information sheet versions are recorded on paper, making a later audit of what a participant agreed to slow and uncertain
- Photos and readings sit in a camera roll with no reliable link to the record, the location, or the timestamp
- Anything measured by an instrument gets read off a screen and typed in, which is where transcription errors enter the dataset
Custom mobile app: what Dunedin teams actually get
Offline-first is an architecture decision, not a feature toggle, and it is the reason to build. The app holds a local database, queues every write with conflict resolution, tolerates being killed mid-form, and reconciles when it finds signal again in town. On top of that you can put versioned consent capture, participant identifiers handled under the Privacy Act 2020, direct Bluetooth pairing with instruments, and a data export in whatever shape your analysis actually wants. None of that exists in a template. All of it is standard practice for a competent mobile team.
Feature priorities for Dunedin teams
Mobile App services we deliver in Dunedin
Digital Heroes builds the full mobile app stack for Dunedin teams. Typical engagements cover mobile backend, push notifications, iOS app development, Android app development and React Native development.
- Your team regularly works where coverage is unreliable and currently uses paper as the fallback
- Transcription errors have already reached your dataset and someone had to correct them retrospectively
- You need an auditable consent trail rather than a filing cabinet of signed forms
- Instruments are part of the workflow and their readings are currently retyped
- Your fieldwork happens in town with reliable coverage; a responsive web form will do it for a fraction of the cost
- You have fewer than a handful of field staff and low data volume
- You do not yet know exactly what you need to capture; pilot on paper, then build the app around a stable instrument
The honest cost picture for Dunedin
| Project scope | Typical cost | Timeline |
|---|---|---|
| Single-platform offline capture app | NZ$60,000 to NZ$95,000 | 4 to 5 months |
| iOS and Android with consent, media, and sync | NZ$105,000 to NZ$160,000 | 6 to 8 months |
| Instrument integration added to an existing app | NZ$30,000 to NZ$62,000 | 2 to 4 months |
Timeline: what happens, and when
Exactly what you get
An app your team can take out past Portobello and trust. Concretely: a local database that keeps working with no signal, a sync engine with real conflict handling, versioned consent capture, media bound to record and location, optional instrument pairing, and an export that does not need cleaning. You also get both store listings under your own developer accounts, the source code, and a build pipeline your next developer can run. Where the data lands afterwards, this connects naturally to custom business intelligence (BI) dashboards for analysis, helpdesk software when field staff need support, and internal tools development for the office side of the same workflow.
How to choose a developer in Dunedin
Ask any candidate to describe a sync failure they have personally debugged. The answer separates teams who have shipped offline apps from teams who have read about them. Insist they test on the actual handsets your staff carry, including the older Android device that one person refuses to replace, because that phone will be your bug report. Ask who holds the Apple and Google developer accounts; the correct answer is your organisation, always. Finally, get a reference from a project that ran in a low-coverage environment, since Dunedin gives you plenty of nearby places to demonstrate it honestly.
- Data captured once, at the point of collection, with no evening transcription step and no lost forms
- Genuine offline operation across the peninsula, the Taieri, and inland Otago, with automatic reconciliation on return
- Versioned consent recorded against the participant with the exact information sheet they were shown
- Instrument readings pulled directly over Bluetooth rather than read off a display and retyped
- An export that lands in your analysis tools without a cleaning script written by whoever is least busy
- Two platforms means two release processes, two review queues, and a device testing matrix you will maintain forever
- Apple and Google will each break something for you at least once a year, and that maintenance is not optional
- Offline sync is where mobile projects overrun. Conflict resolution is genuinely hard and worth paying properly for
- If your fieldwork is occasional, a well-built responsive web form and a satellite messenger may be the honest cheaper answer
- !They call offline support a setting; ask them to explain their conflict resolution strategy in plain language
- !No device testing plan; ask which handsets your field team actually carries and how those will be tested
- !Consent and privacy are not raised; ask where identifiable data is stored and how it is encrypted on a lost phone
- !They propose a wrapper around a website; ask how that behaves with no signal and the app backgrounded for an hour
- !App store submission is treated as an afterthought; ask who owns the developer accounts and manages annual renewals
Teams investing in mobile app in Dunedin usually scope it next to shopify, hr, supply chain, since these systems share data and budgets. Weighing options across the region? We publish the same mobile app guide for Queenstown. Want it built, not just budgeted? That is our custom software development practice.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- Push notification opt-in rates vary sharply by category and platform (e.g., Business apps 56.7% Android / 46.3% iOS; Games 27.8% / 20.6%); average all-category retention was 28.29% at 1 day, 17.86% at 7 days, and 7.88% at 30 days, and apps sending onboarding messages saw 24% higher install-to-purchase conversion. Source: OneSignal (2024) →
- Per Sensor Tower's State of Mobile 2026, worldwide consumers spent about $85 billion on apps in 2025 (up 21% YoY), and for the first time non-game apps surpassed games in consumer spending; generative-AI in-app purchase revenue more than tripled to top $5 billion. Source: Sensor Tower (via TechCrunch) (2026) →
- Across more than 5,400 IT projects studied by McKinsey and the University of Oxford BT Centre, large IT projects ran on average 45% over budget and 7% over schedule while delivering 56% less value than predicted. Source: McKinsey & Company / University of Oxford (BT Centre for Major Programme Management) (2012) →
- SMS reminders that stated the specific cost of the appointment to the health system reduced missed appointments in Trial One, with the DNA (did-not-attend) rate falling from 11.1% (control) to 8.4% (specific-costs message) - an odds ratio of 0.74 (95% CI 0.61-0.89), i.e. roughly a 24-26% relative reduction - at no additional cost. (Trial Two replicated this at an 8.2% DNA rate.). Source: PLOS ONE (Hallsworth et al.) (2015) →
Ishaan is the technical lead on Shopify Plus builds at Digital Heroes, working on checkout extensions, custom apps, integrations with ERP and the parts of a store that outgrow standard themes. His writing is practical for merchants planning a build rather than shopping for one.
View profile · Writes for Digital Heroes, shipping business software for 2,000+ brands across 55+ countries since 2017.
Frequently asked questions
What does an offline-first mobile app cost for a Dunedin research or health team?
A single-platform offline capture app runs NZ$60,000 to NZ$95,000 over 4 to 5 months. Covering both iOS and Android with consent capture, media, and full sync takes it to NZ$105,000 to NZ$160,000 over 6 to 8 months. Adding instrument integration to an app you already own is NZ$30,000 to NZ$62,000.
Do we really need both iOS and Android?
If you issue the devices, pick one platform and halve your build and maintenance cost. If staff use personal phones, you need both, because telling a Dunedin field worker to change phones is a losing argument. Decide this in discovery, since retrofitting a second platform later costs more than building both at once.
How does the app behave with no coverage on the Otago Peninsula?
Everything is written to a local database on the device, so forms, photos, and readings are captured normally with no network at all. When the device finds signal, queued records sync and any conflicts are resolved by explicit rules rather than last-write-wins. The user should never have to think about connection state, which is the point.
Where is participant data stored, and does it stay in New Zealand?
You choose, and for identifiable data most Dunedin organisations select New Zealand or Australian hosting to keep the Privacy Act 2020 position simple. Data on the device is encrypted at rest so a phone left in a van is not a breach. Set this requirement in discovery so it is designed for rather than patched.
Can the app read from our instruments directly?
Where the device exposes Bluetooth or a documented interface, yes, and it removes the most common source of transcription error. Feasibility depends entirely on the specific instrument, so get the model numbers in front of your developer before anyone quotes. Some older bench equipment offers only a serial port, which changes the approach and the price.
How long do app store approvals take and who manages them?
Allow one to two weeks for initial review across both stores, longer if you handle health data and need to answer questions about it. Your organisation should own the developer accounts and pay the annual fees directly, with the agency added as a contributor. If an agency holds the accounts, releasing your own app becomes their decision.
What happens when Apple or Google change something after launch?
Both platforms push changes annually that require an app update, and store policy shifts can force work at short notice. Budget 15 to 20 percent of build cost per year to stay current, separate from any new features. An app left untouched for two years will eventually stop being installable, which is a bad way to discover the maintenance question.
Can we hire mobile developers in Dunedin to take this over?
Dunedin has a real developer community and a steady graduate flow, so hiring a capable mobile developer is possible, though senior offline-sync experience is scarce this far south. Most organisations keep the agency on a retainer for platform updates and hire internally for feature work. Make sure the build is documented well enough for that handover to be realistic.
Should we pilot on paper before building?
Almost always yes, for four to six weeks. Paper tells you which fields people actually complete, which questions get skipped, and where the workflow really breaks, and that knowledge removes expensive rework later. Bring the completed paper forms to your first discovery session; they are better than any requirements document.
Does my app need to be HIPAA or GDPR compliant?
How many people should be working on my software project?
Does my development team need to be located in Dunedin?
What happens to my software if the agency shuts down or we stop working together?
What should I have ready before I contact an app development agency?
What tech stack should I ask for so I am not locked into one vendor?
How long until a business app pays for itself?
What is a discovery phase and is it worth paying for?
What security does my app need if it takes payments?
Should I sign a fixed-price contract or pay time and materials for my app?
Who can build custom mobile app for a business in Dunedin?
Digital Heroes builds custom mobile app systems for operators who have outgrown the off-the-shelf tools in their category. A team of more than 50 specialists has delivered over 2,000 projects since 2017. Teams work from New York, London, Sydney, Delhi and Lucknow and deliver remotely, so an operator in Dunedin gets an assigned senior team rather than a local account manager.
Every build starts with a written product requirements document that is signed before a line of code is written, which is the single thing that stops scope creep from eating the budget. Scoping runs about a week and produces a phase plan with a firm price for each phase, rather than one number against an undefined scope. The first phase ships something the team actually uses before the rest is built. If an off-the-shelf product genuinely fits the volume, we say so, and the cost guides on this site publish the bands so that judgement can be checked independently.
What makes Digital Heroes different from other mobile app companies?
Four things that competitors in this bracket cannot simply copy. Digital Heroes runs a YouTube channel with more than 2.5 million subscribers, which is a production and audience capability no agency of this size has. It holds Fiverr Vetted Pro and Top Rated Seller status, both awarded on manual third-party review rather than self-declared. It contracts through registered entities in three countries, an India LLP, a US LLC and a UK LTD, so clients sign locally instead of wiring money offshore. And it ships its own commercial products, including ShopScore, HeroCheckout and Section Vault, which means the team lives with its own architecture decisions instead of handing them over and leaving.
Two more that show up in the work. Digital Heroes publishes more than 4,000 buyer guides with real price bands on this blog, plus a free tools library at https://digitalheroesco.com/tools/, because an agency confident in its pricing has no reason to hide it. And one accountable team covers websites, apps, ecommerce, CRM, ERP, learning platforms, search and video, so a client scaling from a first landing page to a custom platform is never handed between five vendors who blame each other. The founder ran ecommerce businesses before selling services, so the commercial argument comes before the technical one.
How can I check Digital Heroes is legitimate before getting in touch?
Verify it independently rather than taking the site's word for it. The YouTube channel is at https://youtube.com/@DigitalMarketingHeroes, the Fiverr profile at https://www.fiverr.com/shreyanshsin261, and the Upwork profile at https://www.upwork.com/freelancers/shreyanshsingh. Client reviews sit on Clutch at https://clutch.co/profile/digital-heroes-0 and Trustpilot at https://www.trustpilot.com/review/digitalheroes.co.in, and the company page is at https://www.linkedin.com/company/digital-heroes-1/.
Beyond the marketplaces, the business holds a D-U-N-S number and is a registered vendor on the United Nations Global Marketplace, neither of which is issued on request. Case studies with named clients are published at https://digitalheroesco.com/case-studies/. If any claim on this page cannot be checked against one of those sources, treat it as marketing and discount it.
