Skip to content
dvnt.io

Resources · glossary

Native vs hybrid app

A native app is built separately for Android and iOS, in each platform's own languages. A hybrid app has one shared codebase that produces both versions. The choice decides the cost and how close to the hardware you can get.

Also called
  • native app
  • hybrid app
  • cross-platform app
  • native vs cross-platform
  1. 01

    What you really save

    One team instead of two, but not half the bill. You still have to test on both systems, and differences in behaviour still show up. The saving is real, just rarely as big as the first line of the proposal suggests.

  2. 02

    Where hybrid stops being enough

    With heavy graphics, constant background work and unusual hardware. An ordinary app with lists, forms and notifications fits in a hybrid with no compromise the user would notice.

  3. 03

    What you don't see at the start

    Dependence on a middleman. A hybrid app sits on a framework someone else develops, and their pace decides how quickly you support a new OS version. Native has no such link, but it has two codebases to maintain.

  4. 04

    How to choose without guesswork

    List the features that need the hardware and check whether any of them is key to the product. If none is, the technology question matters less than who will maintain the app for the next three years.

In practice

Related terms

  • Mobile appA program installed on a phone and downloaded from an app store. It can use device features such as notifications, the camera and location, which a browser does not offer or offers only in part.
  • PWA (progressive web app)A website you can install on a phone like an app: it has its own icon, opens full screen and does some things without internet access. It doesn't need an app store or its commission.

← All terms

15 minutes. No sales pitch.

A term in a proposal sounds foreign? In 15 minutes we explain what it means for your project.