Guide

Native, cross-platform or web: how will your product reach phones?

"We need an app" can mean three quite different things, with very different costs and trade-offs. Choosing well early saves money and avoids a rebuild. This guide explains the options in plain language.

Key takeaways

A web app runs in the browser and is usually the quickest, cheapest way to start.
A cross-platform app shares one codebase across iPhone and Android and suits most business apps.
A native app is built separately for each platform; choose it for demanding performance or deep device features.
Decide by what your users must be able to do, not by what sounds modern.
Many products start on the web and add an app once there is evidence of demand.

The three options

Web app. Opens in a phone or computer browser, with nothing to install. It can be added to a phone's home screen. One version serves everyone.
Cross-platform app. Built once using a framework, then published to the App Store and Google Play. It looks and feels like a normal app and can reach most device features.
Native app. Written separately for iPhone and for Android using each platform's own tools. It gets the best performance and the earliest access to new device features, at the price of doing the work twice.

How they compare

Cost and speed. Web is usually lowest, cross-platform in the middle, native highest because there are two builds to make and maintain.
Reach. Web works on any device with a browser, with no download barrier. Apps require installation, which many customers will not do for something they use rarely.
Device features. Native and cross-platform can use cameras, sensors, background tasks and push notifications comprehensively. Web can reach many, but support varies by device, and some are limited on iPhone.
Performance. Native is best for graphics-heavy or very demanding apps. For ordinary business apps, cross-platform and good web apps are fast enough.
Distribution. Apps go through App Store and Google Play review and rules. Web can be updated instantly with no approval.
Findability. Web pages can be found through search engines; apps live in store listings.

When each makes sense

Choose web when users visit occasionally (booking, quotes, forms, portals), you need to launch fast, or you are still testing the idea.
Choose cross-platform when people will use it often, you want it on both stores, and you need notifications, camera or offline use without paying for two builds.
Choose native when you need top performance, advanced graphics, heavy use of device hardware, or the latest platform features on day one.

Customer-facing businesses often start with a web app and add a cross-platform app later; internal tools for staff are often web only.

Things people overlook

Store rules and fees. Apps must follow store policies, including those on payments for digital goods. Check these before designing a payment flow.
Updates take longer on stores. A web fix is live in minutes; an app fix needs review and for users to update.
Two audiences. Many Hong Kong users are on iPhone, but Android remains significant. Check your own customers, not a global average.
Maintenance never ends. Phones and operating systems change every year, and apps need upkeep.
The web can feel like an app. A well-built web app on a phone can be remarkably close for many purposes.

An illustration: a fitness studio

Imagine a studio whose members book classes several times a week and want reminders. (An illustrative scenario, not a client.)

The studio could launch a web booking page first, linked from its messages and social profiles, and learn what members actually use. If bookings are frequent and members ask for an app, a cross-platform version adds home-screen presence and push reminders. Native would only be worth considering if it later needed, say, deep health-sensor integration.

Keep reading

Related guides: Online payments in Hong Kong.

Frequently asked questions

Can a web app send notifications?

Often yes, but support differs between devices and browsers and can be more limited on iPhone. If reliable push notifications are essential, discuss it early.

Is cross-platform lower quality?

Modern cross-platform tools produce good results for most business apps. Differences show mainly in very demanding cases.

Can I start on the web and move to an app later?

Yes, and it is a common path. Plan so the back end and design can be reused, rather than starting over.

Unsure which route fits?

Describe your users and what they need to do. We will recommend the simplest approach that works.

Request a project quote