Android App in New Zealand

Who is holding the phone?

Android projects in New Zealand fall into two camps, and they have almost nothing in common except the operating system.

The public. Roughly half the phones in the country, weighted towards cheaper handsets and older Android versions. If your customers are the general public, you cannot sensibly launch on iOS alone.

Your own workforce. Drivers, technicians, inspectors, site staff, retail. Android dominates here because a rugged handset costs a quarter of an iPhone and can be locked down centrally. If this is your project, you get a luxury consumer apps never have: you choose the device.

Say which one it is in your brief. It changes the testing budget more than any other single fact.

Fragmentation is the real cost difference

iOS is a handful of screen sizes and one manufacturer. Android is hundreds of handsets, several manufacturer skins that each change behaviour slightly, and a long tail of old versions still in daily use.

This does not make Android hard to build for. It makes it expensive to be sure about. A quote that assumes emulator testing is cheaper than one that includes a rack of real devices, and you will not see the difference until a customer with a five-year-old Samsung cannot check out.

Two things to insist on in the quote:

• The minimum Android version supported, named. The last four or five versions covers nearly everyone here.
• How testing is done — real handsets, a device cloud such as Firebase Test Lab, or emulators only.

If the app is for staff, name the handset you are buying and watch the testing line drop.

Build once for both, or twice?

Cross-platform — React Native or Flutter — produces an Android and an iOS app from one codebase. It is typically 30 to 50 percent cheaper than two native builds, and for ordering apps, portals, booking apps, field tools and most business software your users will never know.

Native Android, written in Kotlin, still earns its cost when you need deep hardware work, heavy background processing, tight integration with device management, or performance that is part of the product.

The wrong reason to choose either is that the agency only does one of them. Ask directly: what would you build this in, and what would change if we went the other way?

Google Play is easier than the App Store, with one catch

Review is faster and less opinionated than Apple's, and updates go out in hours rather than days. Registration is a one-off USD 25 rather than an annual fee.

The catch is Google's annual target API level requirement. Every year the minimum rises, and an app that has not been updated to meet it stops being distributed to new users. This is not a bug or a surprise — it is a scheduled maintenance job, and it is the single most common reason a business discovers their two-year-old app has quietly vanished from the store.

Note also that newly registered personal developer accounts must run a closed test with real testers before publishing publicly. Register your company account early; it is not something to start in launch week.

Offline is the feature people forget to ask for

If the app is going into a van, onto a farm, into a basement or out to the Coromandel in January, it will lose signal. What it does in that moment is a design decision, not an accident.

Ask each developer:

• What can the user still do with no connection?
• Where is that data kept on the phone, and is it encrypted?
• What happens when signal returns and two people edited the same job?
• What does the user see while it is catching up?

Offline-capable is materially more expensive than online-only. It is also the difference between an app your field staff use and one they abandon in week three, so decide it deliberately rather than discovering it.

Own the Play account and the listing

Register the Google Play developer account in your company's name, on your card, and add the agency to it. The account owns the listing, the reviews, the install base and the ability to ship an update. If it sits with an agency, changing developer means starting your ratings from zero.

Comparing five quotes

Scope varies more than price here. Read for:

• Which Android versions and which devices are covered, in writing.
• Whether the backend is in the quote or assumed to exist.
• Whether offline behaviour is specified or hand-waved.
• Who owns the Play account, the listing and the code.
• Whether annual API level updates are included in support or billed separately.

Describe who uses the app, on what handset, in what conditions, and the three things they must be able to do. Developers who build for New Zealand field businesses will ask about signal before they ask about screens, and that is usually the one you want.