Services

App Development

Need an app built but not sure whether it should run in the browser, install on the home screen or ship through the app stores? We work out with you what your app actually needs and build it the most cost-effective way.

What an app is

An app is software with one job that people use on a phone, a tablet or a computer: book an appointment, close a work order, track a delivery. Whether it comes from the App Store or opens from a link matters little to the user. For your budget, it is the first question.

Almost every app has two parts: the screens people see, and the backend, the server that stores data, applies your rules and exchanges data with your other systems. The backend is the same whichever type of app you choose. The decision is mostly about the screens.

We work out with you which type your app needs and what it costs, then build the screens and the backend. If the app goes into the stores, we publish it under your own developer account if you want.

The apps we build

We build apps for companies that run their operations or sell through an app:

  • Customer apps: book, order, see where a job stands
  • Staff apps: work orders in the field, checklists, time tracking, approvals
  • Partner apps for a platform: for a client we built a partner app alongside the marketplace, seller portal and admin area.
  • Browser apps that feel like installed apps: Tavla.Games, our own backgammon platform, runs without installation, against an AI or in real time against friends.

Four ways to build an app

There are four ways to build an app. They differ in what the app can do on the device and how much work it takes:

  • Web app: runs in the browser on every device, with nothing to install. An update reaches every user at once. The least work: one codebase for all devices. It fits customer portals and internal tools that should be available on every device straight away.
  • Progressive web app (PWA): a web app people can install on their home screen without an app store. It opens like an app, keeps working through short drops in signal and can send notifications on current iPhones and Android devices. Only slightly more work than a web app. It fits apps people open every day, when installing without an app store is enough.
  • Cross-platform app: written once, often in JavaScript, and shipped through the stores as its own app for iPhone and Android. It uses the camera, location and push notifications like a native app. More work: two stores, two review processes, testing on both systems. It fits when your app belongs in the stores and offers the same features on both systems.
  • Native app: built separately for iPhone and Android, each in its platform's own programming language. It gets the most out of the device: demanding graphics, Bluetooth hardware, tasks running in the background. The most work, because two apps are built and maintained. It fits when your app needs these device features and a cross-platform app cannot provide them.

What decides it

Six questions decide which type fits:

  • Camera and sensors: Does someone photograph receipts or scan barcodes? A web app can do that. If the app needs more, such as Bluetooth devices or location tracking in the background, that points to a store app.
  • Offline use: Does your team work in basements, on building sites or where there is no signal? A PWA bridges short drops. If the app has to work for hours without a network, that points to a store app.
  • Push notifications: Should users get reminders while the app is closed? An installed PWA can do this on current iPhones and Android devices; only a store app does it reliably on every device.
  • App store presence: Do your customers look for you there? For a customer app, that matters. For an app only your team uses, a link is enough.
  • Who uses it: Customers decide for themselves whether to install something. Staff use the app you give them, so you are freer to choose the cheaper type.
  • Your existing systems: Does the app need your inventory system, customer database (CRM) or calendar? That work is the same for every type, because it happens in the backend.

Web first, store app when it is needed

For most business apps we start in the browser. A web app or PWA reaches every user quickly, and each update arrives at once. We build the backend so an iPhone and Android app can connect to it later. When camera, offline or push requirements come up, the screens change, not the foundation.

If it is clear from the start that your app belongs in the stores, we start there. What your app needs decides the route.

How we find the most cost-effective route

Before anyone writes code, we go through these questions with you: who uses the app, where, on which device, and which systems it connects to. Afterwards you know which type your app needs, what each alternative would cost and why we recommend one. You talk directly to the developers who then build it.

The Project Wizard gives you a rough budget and timeline in a few minutes. What drives the price of an app is covered in our guide How Much Does It Cost to Build an App?. If you want a first version in front of real users before anything else, see MVP development.

Frequently asked questions

Native app or web app: which costs less?

The web app. It is built once for every device, needs no app store approval and is current everywhere after one update. A native app is built separately for iPhone and Android and costs more as a result. The PWA and the cross-platform app sit in between.

Does our app need to be in the app stores?

Only if your users look for it there or the app needs features that only a store app offers. Customer apps gain more from the stores than apps for your own team. Your staff can open a team app from a link or install it on the home screen.

Does a web app work without internet?

As a PWA, for a while. It keeps the most recently loaded data and sends new entries once the connection is back. If the app has to work for hours without a connection, a store app is the better choice.

Can a web app become an iPhone and Android app later?

Yes. The backend with its data, rules and interfaces stays; only the screens for the stores are new. That is why we build the backend from day one so both can use it.

What does the cost of an app depend on?

The features, the type of app and the systems it connects to. Each additional platform adds development and testing work. Our guide How Much Does It Cost to Build an App? has the details, and the Project Wizard gives you a rough range.

Have a project in mind?

Get an instant analysis and quote using our AI-powered Project Wizard.