Mobile app development for Australian businesses

Who asks us for apps in Australia

Most Australian app enquiries fall into four groups: startups testing a consumer product, service businesses that want staff to work from a phone, retailers and hospitality groups with loyalty or ordering needs, and organisations that need a client portal. Each group has a different failure mode, and the first call is mostly about finding yours.

The field-service case is particular to this country. Tradies, farm advisers, surveyors and mining contractors often work where mobile coverage drops. An app that needs a live connection for every tap will frustrate them, so we design for offline use and later sync.

Before any design work we write a one-page scope: the three jobs the app must do, who uses it, what it connects to, and what can wait for version two. Most overruns we see on mobile projects come from a vague first release, so we cut it down until a real user could finish a real task in the first month. That scope becomes the basis of the fixed quote.

Cross-platform or native

Our mobile app development service page explains how we choose, and the PWA vs native comparison covers the cheaper route.

Store rules and privacy forms

Both stores ask you to describe what data the app collects. Apple requires privacy details in App Store Connect, and Google Play requires a Data safety section. These forms should match your Privacy Act 1988 policy, and an app that collects personal information needs a collection notice and a way to ask for deletion. If you add location, camera or contacts, the permission prompt must explain why in plain words, or review may reject the build.

We prepare the forms, screenshots and review notes with you. We also create the developer accounts under your business name, so your ABN or ACN appears as the publisher and you hold the account. Apple's and Google's current policy pages, linked in the sources, are the final word.

Payments, tax and the Australian user

• In-app purchases for digital goods go through the store, with prices set per country. Physical goods and services use your own payment provider, such as Stripe.
• Prices shown to consumers are normally GST-inclusive, so test totals on a real card before release.
• For ordering and retail apps, Apple Pay, Google Pay and pay-later options are common expectations.
• Notifications that carry marketing are covered by the Spam Act 2003, so keep opt-in separate from account creation.

Testing on Australian devices and networks

A build that feels quick on office wifi in Sydney can crawl on a regional 4G connection. We test on throttled networks, on older mid-range Android phones and on the two most recent iPhone generations. We also check large text and screen reader support, because accessible apps are better apps and the Disability Discrimination Act 1992 applies to services delivered through them.

Before release we run a short beta with your own staff or customers through TestFlight and Google Play internal testing. Crash reports and slow screens are fixed before the public listing goes live.

How a build runs with the time gap

We work in two-week sprints. At the end of each sprint you install a test build through TestFlight or Google Play internal testing and watch a short demo. The sprint review is booked at a time that works for you, and between sprints a single project lead answers your questions in writing. With Perth two and a half hours ahead of India and the east coast four and a half to five and a half, there is always a window of shared hours, but we never need you awake early or late.

Pricing

Projects start at $1,500 and our hourly rate is $30. An app with login, a few screens and one integration sits near the bottom of that range; real-time features, payments, maps and offline sync add hours. Backend hosting and store fees are separate. The web app cost guide is a useful comparison for the server side.