Architecture to scale
Custom mobile apps

Data gets entered where the work happens

Apps for teams on the street, at the site or in the warehouse, connected to your systems. They work even without signal.

Take the self-assessment Installable or web?
The problem

The work happens out there. The system lives in here.

The technician, the driver or the sales rep records it however they can, and at night someone in the office types it into the system.

  1. The work, in the field A repair, a delivery, a visit. 10:00
  2. Photo, WhatsApp or paper Recorded however possible, if at all. 10:05
  3. The office types it up Someone types what arrived, and fills the rest from memory. At night or on Monday
  4. It reaches the system Late, and minus what got lost on the way. One or more days
Cost 1

Double entry

You pay twice for the same work: doing it and then typing it up.

Cost 2

Late information

The office finds out when it can no longer do anything.

Cost 3

Lost data

Whatever is not written down on the spot is recorded from memory, and wrong.

A custom app is not about "having an app": it is entering data where the work happens and letting it travel to the system on its own.

The service

The app and everything behind it

For your team in the field or on the floor

Work reports, orders and deliveries, entered on the spot

Work reportsService ordersSignaturesPhotosCode scanningLocationVisits and deliveries
Offline

No signal, work goes on

The app saves on the phone and syncs when the connection is back. How complete that mode is gets defined in the assessment.

For your customers

What they ask you by phone today

Orders, account status, claims, appointments and shipments.

Connected

To the system you already have

ERP, invoicing or CRM. If a piece is missing, we build it in the same project.

First

The right format

Installable, web or a mix, depending on your case.

Afterwards

Publishing and maintenance

In public stores or internal distribution, and kept up to date with each new system version.

Public storeInternalVia a link

Don't have the system behind it yet? It is tackled in the same project, through custom software.

Installable or web

Installable app or web app? It depends on your case

The short answerCamera, location, notifications and offline work already exist in both, with differences by device and browser. What decides is your devices, your conditions and how the app reaches the people who use it.

What we look at to decide

What it has to do
PhotosCodesLocationNotificationsPrintingBluetooth
On which devices
Which phones?Company or personal?Which browser?
Under what conditions
GlovesSunOne handHours without signal
How it reaches people
Public storeInternalVia a link
How it is maintained
How often does it change?Who supports it?
«Installable means being in the store»An internal app is distributed privately, and a web app can also be installed on the phone.
«One format is always cheaper»What moves the budget most is the scope, not the format.
«With a given format everyone has the latest version»It depends on how it is distributed; if your project needs it, we handle it.

In the assessment we bring it down to your case: which features you really need, on which devices and under what conditions.

How we work

From the street to the app, in six steps

A small first version that gets used soon, tested by the people who will use it.

  1. Assessment

    What the person who will use the app does today, and under what conditions.

  2. Format and scope

    The essentials, so the first version ships fast.

  3. Screens

    Few, with big buttons. Measured in seconds per task.

  4. Build

    The app and what sits behind it, connected to your systems.

  5. Field testing

    Your teams test it on a real working day.

  6. Launch and follow-up

    We publish it and adjust it during the first weeks.

Then comes support and maintenance: on mobile it is not optional, systems change every year.

Deliverables

What you keep when we finish

The app is in your company's name. Accounts, access and code rights, in writing before we start.

  • The app up and running On your people's or your customers' devices, through the agreed channel.
  • Documented connections So you don't depend on a single person.
  • Manual and documentation Technical, and how to use each screen.
  • Maintenance plan For new system versions, devices and features.
Is it for you?

When an app makes sense, and when not yet

It makes sense if…

Your team writes things on paper or in messages, and someone types them up.
You need to know right away what happened on the street or at the site.
You need to capture photos, signatures, location or codes.
Your customers call to ask things they could check on their own.
Your people work without signal and today that means "write it on paper".

Better to wait if…

The process is not defined yet.Instead: we sort it out first; an app locks in the mess.
You only need to look up information online.Instead: a simple web app is usually enough.
What is missing is the management system.Instead: we order the stages, without ruling out the app.
The app is wanted "to show off".Instead: if it doesn't save anyone work, we tell you up front.

Before building, let's define what you need

We look at how your team works out there today and you leave with a written definition:

  • Which format fits your case: installable, web or both.
  • What the first version includes, the minimum so it gets used soon.
  • In what order to do it and which systems it connects to.
Take the self-assessment

If what you need is smaller than an app, we will tell you that too.

FAQ

What clients ask us most about custom apps

If your question isn't here, message us on WhatsApp.

How much does a custom app cost?

It depends on the scope, the format, the device features used, how many platforms need support and the integrations required. That is why we do not publish a price: we first narrow down the minimum useful scope and then give you a concrete quote, with no features that do not add value.

Should I go for an installable app or a web app?

There is no fixed rule. Several features that used to be exclusive to installed apps (camera, location, notifications, offline mode) are now available in web apps too, with differences depending on the device, operating system and browser. We decide by looking at three things: which features you really need, which devices and browsers you have to support, and the conditions it will be used in. That evaluation is part of the assessment, and we do it before writing any code.

Will it connect to the system I already use?

Yes, as long as that system allows data to be read and written from outside. We check this at the start, because a good part of the project depends on it. If it does not, we show you the alternatives.

Do I need a management system in place first?

Not necessarily. The app needs something behind it to store and serve data: it can be a system you already have, a third-party tool we integrate with, or a system we build alongside the app in the same project. What we define during the assessment is the order of the phases, not a mandatory prerequisite.

Does it work without internet?

It can be built that way: the app saves the work on the device and syncs it when the signal comes back. How complete that mode is depends on the features involved, the format and the devices, which is why we define it with you and include it when your operation needs it.

How does the app reach the people who use it?

It depends: through a public store when the app is for your customers, through private distribution when it is for your company's teams, or via a link if it is a web app. We handle the process for any of the three.

Who owns the app?

Developer accounts and access are held in your company's name. Code ownership and usage rights are set out in writing in the project agreement before work begins, so there is no doubt later on.

What happens after launch?

An app needs maintenance: operating systems and browsers get updated, and what works today can break later. We cover that with a support and maintenance agreement, with an agreed scope and response times.