Mobile app development company in New Zealand

We usually use React Native for an app on iOS and Android. It shares a codebase across both platforms while rendering each platform’s own interface components. Native modules are available when a feature needs them, and some logic can be shared with a React website. This gives you a practical route to both stores without maintaining a separate native app for each platform.

A native build suits an app that depends on deep device features, heavy graphics or complex background work. You maintain separate Swift and Kotlin codebases, so there is more code to build and look after. Flutter is another cross-platform option: its Dart code draws the interface, which suits a heavily branded app where you want screens to look identical across platforms.

A progressive web app is worth considering for a staff tool. It skips store review, though it needs packaging to appear in the stores, and an iPhone user must add it to the Home Screen before it can ask to send notifications. Talk directly with the people building your product as we assess which route fits the features you need.

The Privacy Act’s information privacy principles cover how personal information is collected, stored, used and shared. We map the information your app needs and set up the relevant information screens around those collection and use decisions, so the data flows are considered as part of the build.

If your app collects personal information about someone from another source, information privacy principle 3A requires reasonable steps to make that person aware of specified matters, unless an exception applies. We identify those sources with you and set up a notice in the relevant flow, so the person has a route to the information they need.

A few decisions and access details will give us a useful starting point for the scope.

• First-release tasksList what users must do, in the order they would do it, instead of bringing a long feature list.
• Existing systemsNote the website, CRM, booking software or payment provider involved, whether each has an API, and who holds admin access.
• Developer accountsStart registering Apple and Google accounts in your company’s name. Organisation accounts need a D-U-N-S number for verification.
• Notification rulesNote who needs each message, when it should arrive and which categories users should be able to switch off.
• MeasurementIdentify the screens and tasks you want to understand. Analytics and crash reporting in the first release show where users drop out and which devices crash.

• !

  Putting sign-up first

  Let people see value before asking them to create an account. Apple asks apps without significant account-based features to allow use without a login.

• !

  Requesting notifications immediately

  Ask when the benefit is clear, such as after an order. On Android 13 and later, notifications stay off until the user allows them.

• !

  Adding an SDK without checking privacy answers

  Review the store disclosures when adding analytics or advertising tools. Google Play’s Data safety form must cover data collected by third-party SDKs.