Mobile app development Melbourne

Build a mobile app when a phone is the right tool for the job

Our mobile app development work in Melbourne starts by checking whether a phone is genuinely the right tool, then plans the users, data, security, release and support around it.

When a mobile app makes sense

01

The work happens away from a desk

People need to complete a specific job in the field, on a site or while moving between jobs.

02

Phone features help the user

Camera, location, notifications, offline storage or biometric access makes the work easier or possible.

03

People will use it regularly

People will use the app regularly; a one-off visit may be better handled by a website.

04

Updates and support have an owner

Someone is responsible for app-store releases, phone updates, support and future changes.

What we decide before development

  1. Who will use it and where

    Define who needs the app, where they use it and what success looks like.

    You receiveApp brief

  2. Web or mobile option

    Compare responsive web, progressive web, cross-platform and native options.

    You receiveMobile or web decision

  3. Systems and data

    Set APIs, permissions, offline behaviour, security and recovery.

    You receiveData and security plan

  4. Release and support

    Plan testing, app stores, monitoring, ownership and ongoing change.

    You receiveRelease plan

Next step

What should the app help people do?

We will check whether a mobile app is the right choice and what it needs to work properly.

Questions

Questions people ask us

Do I actually need an app?
Only if it needs the phone's hardware, works offline, sends notifications people want, or gets used weekly. Most businesses fail all four tests and would be better served by a good mobile website for a fraction of the cost.
How much does it cost to build an app in Australia?
Most business apps land in a band that reflects the systems behind them rather than the number of screens. The app is the visible part. The data, sync, permissions and admin interface are the larger share of the work.
How long does app development take?
Three to six months for a first version that does one job properly. Anything quoted at six weeks is either very small or is leaving out the store submission, the admin interface and the testing.
Should I build native or cross-platform?
Cross-platform by default, which gives you iOS and Android from one codebase for most of the cost of one. Native when you need heavy graphics, deep hardware access or strict performance. That is less common than people assume.
What costs are not in the quote?
Store submission and the rejections that come with it, developer account fees every year, certificates that expire, two operating system updates a year that will break something, an admin interface, and support when a user loses their phone.
Do you build for both iOS and Android?
Yes, usually from one codebase. If budget only stretches to one, we would ask which platform your users are actually on rather than assuming, because the answer differs a lot by industry and audience.
Will my app get rejected by the App Store?
Possibly on the first submission, and it is usually avoidable. Apple's review guidelines are public and specific, and most rejections are for things that were knowable before any code was written. We read them at scoping.
Who owns the app and the developer accounts?
You do. The app lives in your developer accounts, the code is in your repositories, and you can take it elsewhere. Get this wrong at the start and you cannot move it later without republishing.