All articles

Hiring2 min read

How to choose an app developer in New Zealand: 10 questions to ask

Choosing an app developer in NZ? Ten questions to ask before you sign, what a good answer sounds like, and the warning signs to watch for.

By Blank Software

In this article5 sections+
  1. 01Before the build
  2. 02During the build
  3. 03Ownership and after launch
  4. 04Warning signs
  5. 05How we answer them

Choosing an app developer is mostly about risk. Most studios can show you good screenshots. What separates them is how they scope the work, who owns the result and what happens after launch. These ten questions get there quickly, and a good developer will be glad you asked.

Before the build

  1. 01Have you shipped and run an app of your own? Building for clients is one thing. Living with store reviews, crash reports and real users is another, and it changes the advice you get.
  2. 02Who will actually build it? Ask whether the people in the meeting are the people writing the code, or whether the work is handed to someone else.
  3. 03What should the first version leave out? A good developer pushes back on scope. If every feature on your list makes it into version one, the plan is too big or the quote is too hopeful.
  4. 04Will I get a written proposal before work starts? It should set out what is being built, the price and the payment schedule, so nobody relies on memory when questions come up later.

During the build

  1. 05iOS, Android or both, and with what? Ask which framework they recommend for your app and why. One codebase for both platforms suits most apps. Some genuinely need native code. Be wary of the same answer for every brief with no reason given.
  2. 06How will I see progress? You should be able to install test builds on your own phone as the work lands, not wait for a big reveal at the end.
  3. 07How do you test it? Ask what is tested automatically and when. An app without automated tests gets harder and riskier to change with every release.

Ownership and after launch

  1. 08Who owns the code and the store listings? Ownership should be agreed in writing before the build starts. Ask whether the app will be published under your own Apple and Google developer accounts.
  2. 09What happens after launch? iOS and Android release new versions every year, and apps need updates to keep working and stay secure. Ask what ongoing maintenance covers and how it is priced.
  3. 10How do you handle personal information? If your app collects anything about its users, your developer should be able to explain where it is stored, who can see it and how it fits your obligations under the Privacy Act 2020.

Warning signs

  • A fixed price before anyone has asked what the app needs to do.
  • No written agreement on scope or ownership.
  • Vague answers about who does the work.
  • No plan for the app once it is in the stores.

How we answer them

We build and run our own apps, rallyp0int on the App Store and FlatMatch, so living with real users is part of our everyday work. You deal directly with the people who design and build your app. Every project starts with a written proposal you agree before work begins, and ownership is set out in your engagement agreement. We can publish under your own developer accounts so the app stays in your name. After launch we offer ongoing service agreements covering maintenance, security updates and what comes next.

Planning an app?

Tell us what you have in mind. We will scope it with you and send a written proposal.

Start a project