Historical note: This article was originally published when mobile development was commonly divided into native, HTML5 and hybrid applications. The technology has evolved significantly since then. This updated version reflects the broader range of options now available.
Choosing how to build a mobile app once seemed relatively straightforward: develop a native application, create an HTML5 web app, or combine the two with a hybrid approach.
Today, the boundaries are less clear. Progressive web apps have expanded what browsers can do, while cross-platform frameworks such as Flutter and React Native allow teams to share much of their code while still delivering app store experiences.
The right decision, therefore, depends less on which technology appears most modern and more on the product’s users, purpose and constraints.
The Main Development Approaches
Native apps
Native apps are developed specifically for an operating system, usually iOS or Android, using its preferred languages, tools and software development kits.
They generally provide strong performance, direct access to device capabilities and close alignment with the platform’s design conventions. However, supporting multiple operating systems may require separate codebases or specialist development skills.
Native development is particularly suitable for products that depend on advanced device features, demanding graphics, complex background processing or highly refined platform-specific experiences.
Progressive web apps
A progressive web app, or PWA, is delivered through the web but can offer features traditionally associated with installed applications. Depending on the browser and operating system, it may support installation, offline use, notifications, camera access, location services and local storage.
PWAs can provide broad reach and rapid updates without requiring users to download every change from an app store. However, access to device features and support for particular capabilities can still vary by platform.
They are often a good option when accessibility, discoverability and speed to market are more important than deep integration with the device.
Hybrid apps
Hybrid applications use web technologies such as HTML, CSS and JavaScript inside a native application container. They can be distributed through app stores and use plugins to access device capabilities.
This approach can reduce duplicated development across platforms, but the final experience depends heavily on the framework, architecture and quality of implementation. Hybrid applications should no longer be assumed to be inherently slow, although highly demanding experiences may still expose performance limitations.
Cross-platform native apps
Frameworks such as Flutter and React Native have created another important category. They allow teams to share substantial parts of a codebase across operating systems while producing mobile applications for installation.
React Native, for example, provides components that map to native user interface building blocks and supports platform-specific code where required. React Native documentation
Cross-platform development can offer a useful balance between development efficiency and a native-quality experience. It does not entirely eliminate platform-specific work, particularly when an application requires specialised integrations or different behaviour on iOS and Android.
Comparing the Options
| Consideration | Native | Progressive web app | Hybrid | Cross-platform native |
|---|---|---|---|---|
| Distribution | App stores | Web and optional installation | App stores | App stores |
| Shared code across platforms | Limited | High | High | High |
| Device integration | Extensive | Varies by browser and platform | Available through plugins | Strong, with native extensions |
| Performance | Usually excellent | Suitable for many experiences | Depends on implementation | Often close to native |
| Platform-specific design | Strong | Browser-based | Can emulate native design | Can support native conventions |
| Offline capability | Strong | Supported when implemented | Supported | Strong |
| Updates | Usually app-store dependent | Immediately available | Usually app-store dependent | Usually app-store dependent |
| Time to market | Potentially longer | Often faster | Moderate | Moderate |
| Specialist skills | Platform-specific | Web development | Web and mobile integration | Framework plus platform knowledge |
These are general tendencies, not fixed rules. A well-designed web or cross-platform application can outperform a poorly implemented native one.
Questions to Ask Before Choosing
The technology decision should begin with the product rather than the preferred development framework.
Consider:
- Who will use the product, and on which devices?
- Does it need to be available through an app store?
- Which device features are genuinely necessary?
- How important are offline use and background processing?
- What level of performance does the experience require?
- Does the interface need to follow each platform’s conventions closely?
- What skills are available within the development team?
- How quickly must the product reach the market?
- What will it cost to maintain across platforms?
- How frequently will it need to be updated?
A simple content or transactional service may work very effectively as a responsive website or PWA. A graphics-intensive product or one relying heavily on device hardware may justify native development. Cross-platform frameworks can be attractive when an organisation wants app-store distribution and a shared codebase without relying primarily on browser-based interfaces.
The Product Decision Comes First
There is no universally superior approach. Every option involves trade-offs between user experience, capability, reach, development speed and long-term maintenance.
The most important question is not, “Should we build a native or non-native app?” It is:
What is the simplest approach that can deliver the experience our users need, reliably and sustainably?
Technology should support the product strategy, not determine it.
Data With Purpose 
Leave a comment