Skip to main content

Service 02 — Apps

An app that stays on the phone because it saves work every day.

An app is worth it when people do the same thing with it several times a week: logging jobs, booking hours, checking stock, photographing receipts. If that isn't the case, an installable web app usually gets to the same result faster and for less. We settle that question first — not after the contract is signed.

Who it's forFor companies whose staff or customers work on the move — where a browser window at a desk isn't enough.

Starting point

Where it usually goes wrong

Installed once, never opened again

An app without a daily reason to open it ends up on the third home screen within a week. What decides this isn't the feature list but whether it replaces a step that is awkward today.

Build twice, maintain twice

Developing iOS and Android separately doubles the effort and the places things can break. And with every change the two versions drift a little further apart.

Between finished and available sits the review

Apple and Google review every version before it appears. Skip that in the plan and you end up with a finished app nobody can download — and a rejected version costs another round.

Demonstration

A job finished out in the field

Whatever happens on site, in the warehouse or at the customer is recorded before anyone gets back to the office — including where there is no signal.

  1. 01

    The job is on the device

    The phone shows what is due, with everything needed to get the work done.

  2. 02

    It gets done on site

    Ticked off, photographed, signed — where the work happens, not from memory in the evening.

  3. 03

    No signal is no problem

    In a basement, in a hall, out in the country: the app keeps working and stores entries on the device.

  4. 04

    Back online, everything synced

    As soon as there is a connection again, the records travel to head office by themselves. Nobody has to remember.

Scope

What you get

First the question of whether it has to be an app
If an installable web app is enough, we say so. It needs no store, ships sooner and costs less. We build a native app when camera, offline use, push notifications or device access demand it.
One codebase for iOS and Android
Both platforms from one project. What you commission once gets changed once and tested once.
Usable without a connection
In a basement, an underground car park, out in the countryside. Entries stay on the device and go out the moment there's a signal again.
Connection to your systems
Inventory system, CRM, time tracking, your own database. The app is a way into your data, not a second island someone has to keep in sync.
Push notifications only when there's a reason
An alert when someone has to act. Everything else waits inside the app — that's the difference between used and muted.
Accessible on the device too
System font sizes, contrast, operation with VoiceOver and TalkBack. The same requirement as on the web, just with different tools.
Published under your own accounts
The developer accounts at Apple and Google are in your name. We set them up and publish through them — the store listing belongs to you, not to us.
Maintenance planned, not sprung on you
iOS and Android change their requirements every year. What has to happen then, and what it costs, is settled before the start rather than in the first invoice afterwards.

Process

How it runs

  1. 01

    Use case and route

    Who uses it, how often and what for. That decides whether it becomes an app or an installable web app.

  2. 02

    Scope & fixed price

    Screens, interfaces, platforms. Then a binding proposal with a fixed date.

  3. 03

    Build & test on real devices

    Every interim version lands on your own phone long before any store sees it.

  4. 04

    Release & handover

    Store listings, waiting out the review, walkthrough. After that the code, the accounts and the credentials are yours.

Price

What it costs

One app for iOS and Android from a single codebase — or as an installable web app.

Fixed price

Both platforms included

  • Deciding between a native app and an installable web app
  • Concept, screen structure and interaction flow
  • Development for iOS and Android from one codebase
  • Offline operation and connection to your systems
  • Accessibility: system font sizes, contrast, VoiceOver and TalkBack
  • Publication under your own developer accounts
  • Walkthrough and documentation

Questions

What gets asked about this most

What does a website cost with you?

We quote fixed prices, not hourly rates. After the call you get a proposal with one number and one date — what's in it, stands. Starting prices per package are on the pricing page. If something new comes up mid-project, we discuss it first rather than quietly adding it to the invoice.

How long does a project take?

A company website typically runs three to five weeks, an app six to ten weeks plus the store review, a single automated workflow one to two weeks, an AI agent two to four weeks. The biggest variable isn't on our side — it's how quickly copy, images and access credentials arrive. The proposal states exactly what we need from you and when.

What happens after launch?

Your choice. Either you take over — code, content and all credentials are fully yours, with no dependency on us. Or you take the retainer: updates, monitoring, security patches and ongoing development at a fixed monthly price, cancellable monthly. No annual contract, no notice period.

Do I need technical knowledge?

No. You need to know your business — the technical side is our job. We explain decisions in plain language, including what they imply down the line. After launch you get a short walkthrough and written documentation so you can maintain content yourself.
You'll hear back within 24 hours

An app that stays on the phone because it saves work every day.