Apps for Customers and Staff
An app is worth it when people want to get something done without sitting at a desk or picking up the phone: booking an appointment, placing an order, reporting damage, checking the status of a job. We build apps for your customers and for your staff — for iPhone, Android and the browser from one shared source base, so a rule does not have to be maintained in three places. Release in the App Store and on Google Play is part of the scope, as is the care afterwards: adapting to new operating system versions, fixing faults, further development.
- calls and emails for routine requests
- paper forms and routing slips
- bookings and orders by phone
- an idea for an app of your own
- existing systems without mobile access
- one app for iPhone and Android
- the same application in the browser
- sign-in with roles
- push notifications where they are needed
- release in the App Store and on Google Play
We build apps for iPhone, Android and the browser — from the first idea to release in the App Store and on Google Play, and we keep looking after them afterwards.
How to tell that this is about you.
If more than two of these sentences sound familiar, a conversation is worthwhile.
What a project in this area looks like.
Not a fixed template, but the order in which the decisions are made. Reverse that order and you pay for it later.
- 01
The purpose first
Who uses the app, what should that person get done with it, and what happens today instead. An app that merely exists is no longer opened after the first week.
- 02
App, browser or both
Not everything needs an app from the App Store. Where the browser is enough, it stays in the browser; where camera, location, push notifications or work without a network are needed, it becomes an app. This is decided before development starts.
- 03
One development for every device
iPhone, Android and browser are built from one shared source base. A rule is maintained in one place and applies the same everywhere.
- 04
Connection to your systems
The app shows data from your existing systems and writes back what is captured in it. Which system is authoritative is agreed beforehand.
- 05
Release and care
Release in the App Store and on Google Play is part of the scope. Afterwards we keep the app running when Apple and Google change their operating systems, fix faults and develop it further.
The capabilities that come together here.
Which of them are used follows from the process — not the other way round.
What is explicitly not included.
A boundary you only learn about in conversation costs both sides time.
- No games and no entertainment applications
- No app without a purpose that can be described in one sentence
- No separate second application that maintains the same data twice alongside an existing web application
The questions we will ask.
So you know where it is heading — and whether you already have the answers today.
- Who should use the app, and what should that person get done with it?
- How does this run today — by phone, by email or on paper?
- Does it really need an app from the App Store, or is the browser enough?
- Which existing systems does the app need to know, and which of them is authoritative?
You cannot buy this ready-made. What gets built follows the way your company works.