Mobile App Development in Hamilton: If It Needs Four Bars, It Is Not Finished

NZ$70,000 to NZ$190,000 depending on offline requirements and platform count. A single-platform online-first app for a small crew starts around NZ$70,000. Full iOS and Android with proper offline sync, photo evidence and hardware integrations sits at NZ$155,000 and up. Budget another NZ$18,000 to NZ$38,000 a year for maintenance and OS compatibility.

Yes, if it is built offline-first from the start. The device holds a local copy of the day's jobs, the crew completes work normally with no connection, and everything syncs when signal returns. Retrofitting offline into an online app later typically costs more than building it that way originally, which is why it belongs in the first scope conversation.

For most Hamilton field operations, React Native or Flutter is the right call because you get both platforms from one codebase and the performance difference does not matter for forms, photos and lists. Go native when you need heavy camera processing, complex Bluetooth hardware, or background location precision beyond what cross-platform frameworks handle cleanly. Your developer should be able to explain their choice in terms of your specific features, not preference.

Google Play usually clears within a day or two, and Apple typically takes one to three days but can take a week if something needs clarification. Plan a two-week buffer before any hard launch date, and never schedule a first release for the week before your busiest season. Rejections most often come from privacy policy gaps or unclear permission usage descriptions, both of which are avoidable.

Yes. Tracking employee location is collection of personal information under the Privacy Act 2020, and you need staff to know what is collected, why, how long it is kept and who can see it. Practical builds limit tracking to working hours, make it visible to the person being tracked, and delete breadcrumb data after a set period. Getting this wrong is an employment relations problem long before it is a legal one.

You should own both. Your business holds the Apple Developer and Google Play accounts and adds the agency as a user, and your contract states that source code and design assets transfer to you. If an agency publishes under their own account, moving to a new developer later means a new listing and every crew member reinstalling, which is a genuinely painful fortnight.

Yes, and this is often where custom earns its money over template apps. Bluetooth integrations with scales, EID tag readers and printers are well-trodden work, though each device needs its own testing because manufacturers implement things differently. Budget one to three weeks per hardware type and insist on testing with your actual devices rather than a similar model.

Make the app remove a phone call rather than add a task. Crews adopt fast when the app means they no longer ring the office to find out where they are going next or to confirm a job is done. Run a pilot with the two most sceptical people you have, fix what they complain about, and let them tell the rest. Top-down mandates produce compliance, not use.

Yes, usually 30 to 40 percent cheaper, and it is the right answer more often than app developers admit. A mobile web app updates instantly with no store review and works fine when your crew has reliable coverage. It becomes the wrong answer the moment you need genuine offline reliability, background photo upload or Bluetooth hardware, all of which are common in Waikato field work.

You can move partially, and the two tools differ sharply. FlutterFlow exports real Flutter source code on its paid plans, so a development team can take it over and keep building; Bubble has no code export, so leaving Bubble means a rebuild where only your data comes with you. If a future migration is realistic, pick FlutterFlow, keep the data model clean, and treat the no-code version as a market test rather than the permanent product.

Yes, and connecting your existing tools is one of the main reasons to build custom: mainstream platforms like QuickBooks, Stripe, Shopify, and Google Workspace all publish documented APIs. Budget 1 to 3 weeks of work per integration depending on API quality and how much data flows in both directions. Ask any vendor whether they have integrated with your specific tools before, because quirks like QuickBooks' OAuth token handling and API rate limits get learned on someone's project, and it should not be yours.

Apple can reject it, depending on the tool and how generic the result is. Review guidelines 4.2 and 4.3 reject apps with minimal functionality or apps generated from commercial templates that duplicate thousands of others, which catches thin website wrappers and unmodified template apps. Tools that compile to real native code, FlutterFlow being the main example, pass review routinely as long as the app itself does something substantive.

Agency rates in markets like Hamilton typically run $100 to $200 per hour against $25 to $60 offshore, but the hourly rate is not the project cost. Across 2,000+ Digital Heroes projects, the setup that consistently works is a hybrid: senior architects and a named lead for your project with a distributed build team behind them, which lands total cost well below all-local without the rework cycles that pure lowest-bid offshore engagements produce. Compare bids on total delivered cost with maintenance included, never on rate cards.

Plan on 10 to 16 weeks for a focused first version on Digital Heroes timelines: about two weeks of design, eight to ten weeks of development and testing, then store submission. Apple usually reviews within 24 to 48 hours, and Google Play can take up to a week for a new developer account. The schedule slips when the feature list grows mid-build far more often than it slips because of the stores.

You should own the source code outright, and the contract must say it plainly with an intellectual property assignment that transfers ownership on final payment. Watch for agreements that only license the code to you, keep it in the agency's repository, or register the Apple and Google developer accounts under the agency's name. Insist on code delivered into a repository you control from week one, not at final handover.

A skilled freelancer is the right call for a single-discipline scope under roughly $15,000, like a website, a plugin, or one integration. Above that, projects need design, backend, testing, and project management at once, and a solo builder becomes the single point of failure: if they get sick or take a bigger client, your project simply stops. Agencies bill 20-40% more per hour but carry continuity, code review, and someone to escalate to, which is what you are actually buying.

A one-page brief beats a formal specification: the problem the app solves, who will use it, the 10 to 15 features version one must have, two or three apps you want it to feel like, and your budget range and deadline. You do not need wireframes or a technical document; producing those is what the agency's discovery phase is for. A written feature list also makes quotes comparable, because every vendor is finally pricing the same thing.

Discovery is a short paid phase, usually one to three weeks, where the agency turns your idea into wireframes, a technical plan, and a firm estimate. It is worth paying for on anything nontrivial because it surfaces scope problems while they cost hundreds instead of tens of thousands. It also produces a portable asset: a good discovery document lets you take the project to any competent team, which keeps your agency honest on price.

Your data can move, but your users' passwords cannot. Platforms like Bubble let you export records through CSV files or their API, but password hashes never leave the platform, so a migration needs a password reset or email login flow for every existing user. Plan the export before you hit the platform's pricing or capacity ceilings, because migrating under pressure is how data gets lost.

Digital Heroes builds custom mobile app systems for operators who have outgrown the off-the-shelf tools in their category. The work is delivered remotely: our engineers work from Delhi and Lucknow, leadership is in New York, and some team members live in London and Sydney and work remotely from there. We have no office in Hamilton. You can chat with the team directly, and every form gets an email reply within 24 hours.