Skip to content
Codivaro
← All notes

App · 5 November 2026 · 6 min read

Getting an app built: process, cost drivers, and web app or native app

What an app really needs, when a web app is enough, and what drives the effort. An honest guide for businesses before commissioning an app.

MSMurat SertCodivaro · Karlsruhe

“We need an app” is often the first sentence in the conversation. Sometimes that's right. Sometimes a good web app solves the same problem faster and for less. Before you commission an app, it pays to answer a few questions honestly.

Do you really need an app?

An app in the stores is worth it when your customers open it regularly: to order, book, collect points, or for your team's daily work. For something used once or twice a year, hardly anyone downloads an app.

  • More of an app: regular customers, stamp card or loyalty programme, push notifications, camera or QR scanning, offline use in the field.
  • More of a web app: occasional use, QR ordering at the table, booking appointments, anything that should work instantly without a download.
  • Both: many projects start as a web app and get an app later, once it's clear customers come back.

Native, cross-platform or web app?

  1. 01

    Native app

    Built separately for iOS and Android. Maximum control, but two codebases and double the maintenance.

  2. 02

    Cross-platform

    One codebase, for example with React Native, for both stores. The sensible route for most business apps.

  3. 03

    Web app

    Runs in the browser, no store, no download. Quick to roll out, but limited access to device features.

What drives the effort

A serious price is only possible once the scope is clear. These points shape it most:

  • Number of screens and flows: login, ordering, profile, history, settings.
  • Integration: is there already a back end, a till or an inventory system, or does it need to be built too?
  • Payments, push notifications, location, camera, offline support.
  • A panel for your team to manage content, orders or offers.
  • Publishing on the App Store and Google Play, including Apple's and Google's reviews.

How an app project runs

  1. 01

    Call

    Clarify the goal, the audience and the three most important flows.

  2. 02

    Concept & fixed price

    Screens and features in writing, at a fixed price.

  3. 03

    Development with demos

    Every week you try the real state on your own phone.

  4. 04

    Store release

    Submission to Apple and Google, under your company account.

  5. 05

    Operations

    Updates for new iOS and Android versions, bug fixes, further development.

Try it instead of imagining it

The “Customer app” live demo on this site shows what a customer app with its own panel feels like: order, pay with Apple Pay, mark it ready in the panel and see the push notification on the phone.

Related serviceApp developmentAn app your customers or your team actually open every day. iOS and Android from one codebase, connected to the system you already run.Start a project →