The pieces and their boundaries are settled before code.
Several institutions, one system, records kept apart.
One codebase, both stores: iOS and Android.
We take a running system over and improve it.
AI only where the problem actually calls for it.
Mobile app
When you are having an app built, the first thing to settle is where it will open. A technician's phone, a worker's own handset and a touchscreen the business owns each decide most of what follows. If it has to keep working where coverage drops, the entry waits on the phone and syncs in order once the signal returns.
Mobile app development takes the part of your business that does not happen at a desk onto a phone, or onto a screen the business owns. Which device the app opens on, what it holds locally and what happens when the connection drops are settled before the first screen is drawn. AlgoKlima's field app opens a service call with no signal, while the KGM SsangYong showroom kiosk runs on the dealership's own touchscreen.
A mobile app is tested at a desk but judged where it is used. A technician opens it in a boiler room, a worker scans in on a temporary site that has only just acquired an address, a visitor taps a screen on a shop floor with a few minutes to spare. In all three the network is worse than it is at a desk.
AlgoKlima’s field app was built for that condition. A service call is opened, filled in and closed with no signal present, and because the information sits on the phone, no waiting notice appears on screen; when coverage returns it reaches the back office in the order it was created. The queue behind that is taken apart in offline-first field apps. AlgoKlima is our own product, so the upkeep of that condition is ours as well.
The construction site attendance system answered a different question: how do you record arrivals and departures without mounting anything on site. The scanned code confirms the person and the device location confirms the site, so nobody has to name a place from a list. Because the system runs on the crew’s own phones, closing a site leaves no turnstile to uninstall.
The KGM SsangYong showroom kiosk took the app off the visitor’s phone altogether. Trim and equipment are browsed on the store’s own touchscreen: no download, no account, no personal data collected. Nor is the interface an enlarged phone app; touch targets, type size and navigation depth were set for someone standing up for a few minutes.
All three came out of the same toolset. A phone in a boiler room and a screen on a shop floor do different jobs, yet both were written with one set, because whoever reopens that code years from now is also us.
When the heart of the job sits in the iPhone itself, we step outside that toolset. ProofPair, Nightproof and Day Sheet were written natively for iOS, with no shared layer in between. Day Sheet keeps a door code behind Face ID and closes a visit from the Lock Screen; Nightproof brings its sound back at the same level after a call or a headphone drop. Each of them reaches straight into interfaces iOS owns, and a shared layer does not go that deep.
The questions a mobile project gets scoped with:
An app bound for both stores is written from one source, so a fix reaches both in the same release. When an app leans on what only iOS offers, such as the Lock Screen, Face ID or the audio engine, we build it natively for iOS. Day Sheet and Nightproof were built that way.
The interface follows the moment rather than the device: standing up, one-handed, a few minutes at a time. On the KGM SsangYong showroom kiosk the touch targets, type size and navigation depth came out different from a phone app.
The server and the notification channel behind an app are decided alongside it, not after release. In Tahlil.com's patient app a push goes out the moment a physician signs off an interpretation, calling the patient back to the result.
When it matters who made an entry and where, both are confirmed from the device itself. On the construction site attendance app the scanned code confirms the person, the device location confirms the site, and the two land in one entry.
If the work continues out of coverage, the app shows no waiting state; the information sits on the phone and reaches the back office in order once the signal returns. AlgoKlima's field app was built for exactly that condition.
Distribution is a decision taken early rather than a final step: the crew's own phones, hardware the business buys, or a screen the store already owns. On the construction site attendance app the crew's own phones mean there is nothing to take down when a site closes.
Every project goes through the same four stages: planning, architecture, modelling, development.
See our process
A touchscreen app standing on the showroom floor. Visitors browse the full SsangYong range and compare trims there, on the dealership's own device. Nothing is installed on anybody's phone: walking up to the screen is the whole setup.
A construction site is temporary, so no turnstile goes up and crews move between projects. Entry and exit are logged from the worker's own phone with a QR scan and a location check. At month end, who was where and for how long is read back out of those records.
Our own product for HVAC, boiler and appliance service companies. The customer and device records the office works from are the same ones the technician carries into the field. A job can be opened and closed in a basement with no signal, and service history stays tied to the device.
Our own iPhone app for house cleaners who work alone. The day's homes appear in order, every door code stays locked behind Face ID, and moving one visit leaves the rotation where it was. A PHP server confirms subscriptions by checking Apple's signature itself, with no outbound call.
UI stands for user interface, UX for user experience. When a quote folds both into one design line, the name does not say which one was priced; the list of outputs does.
An API is an agreement between programs. A second program touching the record forces the gate: a patient's phone at Tahlil.com, a technician's at AlgoKlima. We are building QRVizit without one.
If the fingerprint reader is questioned, which field of a timekeeping record is tied to a body? The identity field takes a reissuable identifier; the record model stays. A lawyer answers the rest.
A field app earns its keep where the signal dies: where data is first written, how the phone's queue empties in order and how conflicts merge, drawn from our service-management work.
In the foreground and with permission, a web browser gives a page the camera and location, so why is the field app installed? The needs list decides first, then who holds the device.
A turnstile never gets installed on a site that will be dismantled. When identity and location live inside the record itself, matched entry-exit pairs yield hours worked, and pay follows from them.
A demo runs from the vendor's side. The difficulty your system was built for begins when the other side touches the same record; take the scenario from there and sign on the record's state.
Not when the app has to reach both stores, because both platforms come out of one source and you fund one codebase. Tahlil.com's patient app went to both stores that way. An iPhone-only app that depends on what iOS itself provides is built natively for iOS instead. Day Sheet was made like that, so it can keep door codes behind Face ID. Which devices you have to reach is something we settle with you while the quote is still being shaped.
The length is set by what your app has to do out of coverage, not by how many screens it has. If information waits on the phone and travels later, the rules of that queue get designed too, and that is heavier than a list of screens. AlgoKlima's field app lets a technician open and close a service call with no signal. What has to work offline is agreed with you during planning.
On your crew's own phones, or on a screen the business owns; the place of use decides. That choice sets your hardware bill too: a pocket app buys no devices, and a kiosk asks a visitor for no download. The construction site attendance app sits on the workers' own phones, so closing a site leaves nothing to unmount. The KGM SsangYong showroom kiosk runs on the dealership touchscreen with no download and no account.
We can; the app connects to your server. The work does not end at your API, though, because the app keeps a waiting queue of its own, so what it holds on the device and what happens to that when the signal returns is defined before we start. AlgoKlima's server accepts entries in the order the field app queued them. Listing the endpoints your server already exposes is our first working session.
It does only if nothing keeps your records today; if you already run a system, the app connects to it. AlgoKlima, which we run ourselves, pairs an office panel with a field app. The phone keeps its own copy of the record, the two copies merge when the connection returns, and edits from both sides go through conflict resolution. The service management case below shows that setup.