Mobile apps
Bring your services closer to your customers.
A few steps inside an app can finish what used to need a phone call or a visit. We build the whole journey: the screens, the backend that carries out the request, and the notification that confirms it.
1 — Pick a service
Choose a service
- Routine maintenance
- Technical visit
- Consultation
2 — Choose a time
Pick a time
Thursday
- 10:00
- 12:30
- 15:00
3 — Request received
Your request is in
You will get a notification when the time is confirmed.
What makes an app useful
Capabilities, in the context of that journey
-
Interfaces people can follow
A few clear screens that finish the task rather than explain it.
-
Actions connected to a backend
What the user taps actually reaches your system and is recorded there.
-
Notifications at the right moment
A confirmation, reminder or status update, tied to a real action in the app.
-
Real-time updates where they are needed
When a project genuinely needs live status, we build it for that specific purpose.
The technology
Two development approaches, and the services around them
The two development approaches
-
Flutter · Dart
A framework and its language, for building one app that runs on iOS and Android.
-
React Native
Another supported route for iOS and Android apps. It is not simply another name for React on its own.
We choose the approach from what the product needs and what it connects to. Neither one means there is no platform-specific work, or identical performance in every case.
Supporting services
- Firebase Ready-made backend services, as the project needs
- OneSignal Sending and managing push notifications
- Pusher Real-time updates between server and app
- Socket.IO An open two-way connection for live state
Notifications and real-time updates are two different capabilities, and no project needs all of these services. We use the ones that serve a real function in the app.
Development tooling
Xcode Apple’s development tool for its platforms — not a programming language and not a separate framework.
How the parts connect
The app, the backend, and the notification
-
The app
Sends the user’s request.
-
The backend
Carries it out and stores its state.
-
The notification
Comes back to the user with the outcome.
An illustration of the architecture, not a live monitoring console.
Every project is quoted against its own scope, once we understand what you need.
Common questions
Questions before starting your app
Will the app work on both iOS and Android?
Yes — we develop for both using Flutter with Dart, or React Native. Each platform still has its own considerations, and we explain what applies to each while scoping the work.
Can the app connect to our existing website or system?
Usually yes, through an API. We review what your current system exposes and work out what can be connected within the project’s scope.
Are notifications and real-time updates the same thing?
No. A notification is a message delivered to the device; a real-time update changes the screen while someone is looking at it. We work out which your project needs — it may only need one.
Do you publish the app to the App Store and Google Play?
What the project scope covers is preparing the build technically for the stores. The developer account, its fees, store-policy compliance, the submission work and whatever the platform decides on review stay with you or are scoped and quoted separately. We do not promise approval or publication.
How do we choose between Flutter and React Native?
It follows the nature of the product, what it connects to, and who will look after it afterwards. We talk it through and recommend an approach with a clear reason before quoting.
Tell us which service you want to put in an app
Describe the service and what you want a user to be able to do, and we will come back with the right approach and a quote against the scope.