Mobile apps are commonly classified by how they are built rather than by what they do. Four approaches dominate today: native apps, hybrid apps, cross-platform apps and progressive web apps (PWA). They differ in the technologies used, the degree of access to device hardware, the amount of code that can be shared between operating systems and the way the app reaches its users. These classifications vary and the categories overlap: some sources treat web-based hybrids and cross-platform frameworks as a single group. The distinction is practical rather than academic: mobile devices account for over half of global web traffic, about 52% as of mid-2026 according to Statcounter Global Stats[11], and the chosen approach shapes an app's cost, performance, reach and maintenance for years.
A short history
Mobile software predates the smartphone, but the modern app model began with the launch of Apple's App Store on 10 July 2008, which opened with around 500 apps[12]. Google's Android Market launched the same year and was rebranded as Google Play in March 2012[13]. These stores turned apps into a mass distribution channel and made the native model the default for a decade.
As supporting two separate platforms proved expensive, alternative approaches emerged. Hybrid frameworks wrapped web pages in a native shell; cross-platform frameworks such as React Native (2015) and Flutter compiled one codebase into two apps; and the term "progressive web app" was coined in 2015 by Frances Berriman and Alex Russell to describe web apps that behave like installed software[2][3].
Native apps
A native app is written specifically for a single operating system using that platform's own tools and programming languages. On iOS the primary language is Swift[7]; on Android development is Kotlin-first, with Java also supported[8]. Because the code targets one platform directly, native apps have full access to the system framework APIs and device hardware, including features exposed through the platform's hardware abstraction layer[14].
The strength of this approach is the fullest access to hardware among these approaches and generally the strongest performance, together with a close match to each platform's interface conventions and mature tooling from Apple and Google. The trade-off is that covering both iOS and Android requires two separate codebases, which means higher cost, longer development time and a broader skill set to maintain. Native development is therefore common where performance and deep hardware access matter most, such as games, camera-heavy apps and system utilities.
Hybrid apps
A hybrid app is built with standard web technologies, such as HTML, CSS and JavaScript, and then packaged inside a native container. Apache Cordova, one of the earliest frameworks of this kind, describes applications that "execute within wrappers targeted to each platform" and rely on a web view to render the interface[6]. A single web codebase therefore runs on several systems, which lets web developers build mobile apps with familiar tools, more quickly and cheaply than two native builds. The cost is that the web view adds a performance and feel penalty, access to newer device features can lag behind native, and complex, animation-heavy interfaces are harder to match.
The limits of the hybrid approach became a well-known industry lesson in 2012, when Facebook rebuilt its app from an HTML5 hybrid to native. Mark Zuckerberg publicly called the bet on HTML5, made while trying to improve the company's mobile experience, its biggest mistake[17]. Hybrid tools remain in use for content-driven apps; the Ionic framework, which builds on Cordova, powers apps such as the fitness app Sworkit[6].
Cross-platform apps
Cross-platform frameworks compile a single codebase into apps that run on more than one operating system, but, unlike hybrid apps, they render closer to native performance rather than relying on a web view. React Native, released by Meta in 2015, follows the principle "learn once, write anywhere" and is used to build apps for Android and iOS[4]. Flutter, an open-source framework supported and used by Google, similarly builds "natively compiled, multi-platform applications from a single codebase"[5].
Both frameworks are used at scale. Meta's official React Native showcase lists apps including Instagram, Facebook, Microsoft Office, Teams and Outlook, Amazon Shopping and Shopify[15]. Google's Flutter showcase lists Google Pay, Google Ads, BMW, eBay and the Alibaba marketplace Xianyu, among others[16]. The main trade-offs are that very demanding apps may still need native modules, some platform-specific code remains necessary, and the project depends on the framework and its release cycle.
Progressive web apps (PWA)
A progressive web app is, in the words of MDN Web Docs, "an app that's built using web platform technologies, but that provides a user experience like that of a platform-specific app", running across operating systems from a single codebase and supporting features such as offline use and installation[1]. Unlike the other three types, a PWA is delivered through the web browser rather than an app store. This removes the install step, keeps a single web codebase that search engines can index, and makes the initial download small; the trade-offs are more limited access to some device hardware, uneven support for advanced features across browsers, and weaker discovery without an app store listing.
PWAs have been adopted by large services to reach users on slow networks or low-end devices. Google's web.dev case study on Twitter Lite reports a PWA of about 600KB over the wire versus a 23.5MB native Android install, together with a 75% rise in Tweets sent and a 20% drop in bounce rate[18]. Pinterest's engineering team reported large gains in engagement and sign-ups after launching its PWA[19].
Distribution and cost
Native, hybrid and cross-platform apps are usually distributed through app stores, most notably Apple's App Store and Google Play, which charge a commission on digital sales. The standard rate is 30%, reduced to 15% for small developers or on an initial portion of annual revenue: Apple applies 15% under its Small Business Program[9], and Google Play charges 15% on the first 1 million US dollars a developer earns each year and 30% above that[10]. These standard rates apply as of 2026 and have been subject to regulatory and legal change, such as the European Union's Digital Markets Act. Progressive web apps, being delivered over the web, fall outside these commissions.
Choosing an approach
There is no single best type; the right choice depends on the goals of the app. Native development suits products where performance and deep hardware access are decisive. Hybrid and cross-platform approaches reduce duplicated work across systems and are common for business apps that must run on both iOS and Android. A PWA fits services that value instant access and web reach over app-store presence. Many organisations combine approaches, for example a native core with web-based sections, rather than committing to a single type.