Website or app for a small business

A native app is a genuinely different artefact from a website. It is distributed through the App Store or Google Play, subject to each platform’s own review process, and it requires ongoing maintenance to stay compatible with new operating system versions. For most small businesses considering an app, the actual need is better served by a well-built website.

Why building a mobile app is a border, not a smaller version of web design

Building a native iOS or Android app is a different discipline from web design. It has its own specialists, its own development languages and frameworks, its own distribution model through app stores rather than a browser, and its own ongoing maintenance obligations tied to operating system updates. This site does not cover native app development as a discipline in its own right. What it covers is the decision point where a business considering an app should first check whether a website genuinely cannot do what they need. In most small-business cases, it can.

What a native mobile app requires that a website or mobile website does not

App store submission and review

Both Apple and Google review submitted apps against their own published guidelines before publishing. A rejected or delayed submission is a real project risk a website never faces.

Separate platform codebases, or a cross-platform framework

iOS and Android are different platforms. Building a mobile app for both generally means either two separate codebases or a framework designed to target both from one, each with its own trade-offs.

Ongoing compatibility maintenance

Operating system updates on both platforms periodically require an app to be updated to remain compatible, submitted, and reviewed again. That is an ongoing cost with no direct website equivalent.

User acquisition through app store discovery

This is a different problem from search engine visibility for a website, and one this site’s methodology does not cover.

Where a native app genuinely earns its cost

A small number of genuine cases justify the added cost and complexity. One is a business whose core offering depends on deep device integration — camera-based functionality beyond what a browser reliably offers, background location tracking, push notifications a user genuinely wants and interacts with regularly. Another is a business whose customers are expected to open the tool frequently enough that home-screen presence and app-store discoverability provide real, ongoing value beyond a single visit.

Where a website (or a progressive web app) genuinely covers the need

For the large majority of small Australian businesses — trades, professional services, local retail, hospitality — the actual customer interaction is infrequent and transactional: find the business, get information, make an enquiry or a booking, occasionally return. A responsive website handles this pattern completely, without the ongoing app-store maintenance burden. Where a degree of installability or offline access genuinely adds value, progressive web apps and offline access covers that middle ground before a full native app is considered.

App store fees are a real, checkable part of the ongoing cost gap

Beyond development cost, publishing a native app carries ongoing platform fees a website simply does not. Apple’s Developer Program requires an annual membership fee to publish and maintain an app on the App Store. Google charges a one-time registration fee to publish on Google Play. These are published, current figures on each platform’s own developer site, worth checking directly before budgeting a native app project. They are a genuine recurring or one-off cost with no website equivalent, on top of whatever the actual development work costs.

SMS and email can achieve much of what push notifications are sold on

A common argument for a native app is the ability to send push notifications. But for most small businesses the underlying goal is already achievable through SMS and email — staying in touch with existing customers about a booking reminder, a seasonal offer, or an account update. Both reach a customer without requiring them to have installed anything at all. Both are what this site’s own build already uses for lead notification, without any app in the loop. A business genuinely evaluating whether it needs an app for this reason specifically should weigh it against the fact that the underlying communication goal already has a working, app-free path.

What a cross-platform mobile apps framework changes, and what it does not

Frameworks that let a single codebase target both iOS and Android — React Native and Flutter are the two most widely used — reduce, but do not eliminate, the separate-platform cost named above. Each platform still has its own app store submission process, its own review, and its own platform-specific quirks that surface even from a shared codebase. Choosing a cross-platform framework is a genuine way to reduce native app development cost relative to two entirely separate codebases. It does not remove the app-store fees, the review process, or the ongoing maintenance burden covered earlier in this page.

A short website-or-app decision guide for small businesses

Need	Website (or PWA) covers it	Native app likely required
Customers find the business, view services, enquire or book occasionally	Yes	—
Deep camera, sensor, or background-location functionality	Limited	Yes
Frequent daily use where home-screen presence and push notifications drive real engagement	Partial (PWA can offer some of this)	Often yes
App store discoverability as a marketing channel	No	Yes, but this is a different discipline from web design

What to do next: choosing between a website and a native app

Be specific about which capability is actually driving the app idea before committing to native development — in most cases a well-built website answers the underlying need at a fraction of the ongoing cost. For what web design is as a discipline, and where its border with native app development actually sits, web design sets out the wider context this decision sits inside.