Quiz Entry - updated: 2026.07.14
What are hybrid mobile applications, and what variants exist?
Hybrid apps run web technology inside a native app shell, so one codebase ships to multiple platforms while still looking and installing like a real app.
The goal of a hybrid app is to hide the seams: from the user's point of view it is just an app from the store, even though a web application is running inside a "native frame". This buys you native distribution and hardware access without writing a separate app for each OS. There are three main variants, which differ in how much is really web vs. native:
| Variant | How it works | Example |
|---|---|---|
| Browser-based | a WebView displays the web app, with plugins for hardware | Cordova, Ionic |
| Native UI | JS logic, but it renders real native widgets | React Native |
| Cross-compiled | code is compiled to native machine code | Flutter, Xamarin |
- Browser-based (Cordova / Ionic) — your HTML/CSS/JS runs in an embedded browser (WebView), and plugins bridge to the camera, GPS, etc. Easiest path from an existing web app, but performance is the weakest of the three.
- Native UI (React Native) — you write JavaScript, but it maps to actual native UI components, so the interface looks and performs more native.
- Cross-compiled (Flutter) — Dart code is compiled to native ARM code and drawn by its own rendering engine, giving the best performance among hybrid approaches.
Memory tip: all three trade a bit of native performance for one shared codebase; they just draw the web/native line in different places.