Mobile apps
The job, the checklist and the signature, on the phone
We build mobile apps for teams who work away from a desk and for customers who want your service in their pocket. One codebase covers iOS and Android, and the app is connected to the systems your office already uses.
Mobile app
Today · 4 visits
- Boiler service08:30 · Split
- Install thermostat10:00 · Solin
- Leak inspection13:00 · Kaštela
- Annual check15:30 · Trogir
What it is
Work recorded where it happens
When a technician fills in a paper form and someone types it up the next day, the office is always a day behind and details go missing. A mobile app records the work on the spot: the checklist, the photos, the parts used and the customer’s signature. It keeps working without signal and sends everything to the office when the connection returns.
- One React Native codebase for iOS and Android
- Works offline and synchronises when the connection returns
- Uses the camera, barcode scanning, location and push notifications
- Reads from and writes to the same systems the office uses
A service visit
- AppJob opened on siteAddress, history and notes
- ChecklistSteps completedPhotos attached
- PartsMaterials recordedScanned from the van
- SignatureCustomer signs on screen
- OOfficeReport and invoice data arrive
What we deliver
From the first screen to the app stores
Design for one hand
Screens designed for use on site: large targets, few steps, and readable in daylight.
iOS and Android app
A single React Native codebase that produces a native app for both platforms.
Offline and sync
Data stored on the device and synchronised in the background, with clear handling when two people change the same record.
Back end and integrations
An API and database behind the app, connected to your ERP, CRM or scheduling tool.
Store publishing
App Store and Google Play listings prepared and submitted under your developer accounts, or private distribution for internal apps.
Updates and care
New releases when the operating systems change, crash monitoring and fixes after launch.
How a project runs
In people’s hands early
- 01
Map the work
We go out with the people who will use the app, or talk to the customers who will, and note what they need at each step.
- 02
Prototype
A clickable design is tried on real phones before any code is written, so the flow is right before it is built.
- 03
Build and test
A test version goes to a small group early. Their feedback shapes the rest while the back end and integrations are built.
- 04
Publish and care
The app is published or distributed to your team, and we keep it current as phones and requirements change.
What we build with
- App
- React Native, Expo, TypeScript
- Back end
- Node.js, PostgreSQL, REST API, Push notifications
- Connected to
- Odoo, Your CRM, Your scheduling tool, Document storage
Do you need an app, or would a website do?
An app is a good fit when…
- People work where there is poor or no signal
- The work needs the camera, scanning, location or signatures
- Push notifications would replace phone calls and messages
- Customers use your service often enough to keep an app installed
Probably not for you when…
- A page that works well in a phone browser would cover it
- Customers would use it once or twice a year
- There is no back-office system yet for the app to connect to
- The main reason is that a competitor has one
Use cases
Where mobile apps are used
Problems a mobile app is often part of solving.
An assistant that answers from your documents
Staff or customers ask in plain language and get an answer drawn from your documents, with the source shown.
Open use case OperationsBusiness automationCustom softwareNew colleagues ready on day one
Accounts, equipment, documents and first-week tasks set in motion from one form.
Open use caseQuestions about mobile apps
Why React Native?
One codebase produces an app for both iOS and Android, which keeps the two versions in step and makes changes quicker. For business apps the result is hard to tell apart from a separately built one. If your app needs something that depends on deep platform-specific work, we will tell you before we start.
Do you handle publishing to the App Store and Google Play?
Yes. The developer accounts are opened in your company’s name, so the app belongs to you, and we prepare the listings and submit the builds. Each store reviews apps to its own rules and timing, which we plan for but do not control.
Can an internal app be distributed without the public stores?
Yes. Both platforms offer ways to distribute an app privately to your own staff. We set up the option that suits the number of devices and how they are managed.
How does offline work?
The app stores what the user needs on the device and records changes locally. When a connection returns it synchronises with the server. We agree with you what happens when two people change the same record, so nothing is silently overwritten.
Does it need a back end?
Almost always. The app needs somewhere to send and fetch data. Where you already have an ERP or CRM, the back end is mostly a thin layer in front of it; where you do not, we build the database as part of the project.
What about updates after launch?
Phones and operating systems change every year, so an app needs regular releases to stay current. That work is part of a care agreement, together with monitoring and fixes.
Show us one process. We will show you what it could look like.
The analysis is free, takes about an hour of your time, and ends with a written summary you keep.
Prefer to read first? See examples