Task analysis
We work out how many steps and seconds each job takes and under what conditions. Buttons meant for gloved fingers are large, and frequent actions take a single tap.
Picture a company servicing hotel swimming pools across Antalya and Muğla. On each visit the technician measures chlorine and pH, adds chemicals, backwashes the filter and scribbles it all in a damp notebook kept in the van. When a hotel's quality manager asks for three months of readings in mid-season, half the pages are illegible. There is no reception in the plant room, the technician is wearing gloves and has about twenty minutes per pool. When we design an app for work like this, the first question is not which framework to use but the conditions in which it gets opened. Bright sun or a basement? Gloves on? One hand free? Everything from screen layout to data syncing follows from those answers. And where an app would not be opened every day, say for dealers who order a handful of times a year, we will tell you straight that a mobile-friendly website or a PWA is the wiser spend.
A mobile project is as much about the server behind it, the office dashboard and the yearly round of OS releases as it is about the screens on the phone.
We work out how many steps and seconds each job takes and under what conditions. Buttons meant for gloved fingers are large, and frequent actions take a single tap.
Flutter or React Native for one shared codebase, Swift and Kotlin for hardware-heavy work, a PWA for simple internal tools. The choice is justified in a short comparison table.
Data is written to the device first and sent to the server in the background once a connection appears. When two people edit the same record, a clear rule decides which value wins, and the user sees it.
Camera for photos and document capture, barcode and QR scanning, NFC tags, Bluetooth measuring devices and location. Each is tested on real handsets, the cheapest ones included.
Records captured in the app flow into Logo, Mikro, Netsis or your own system, and the office gets a web dashboard for planning and reports.
Apps used only by staff can be delivered through Microsoft Intune, Apple Business Manager and managed Google Play without ever appearing in the public stores.
Crash reports via Firebase Crashlytics or Sentry with no personal data, release notes, and a compatibility pass before each new iOS and Android version.
The first installable build reaches the field crew as early as possible. A screen that looks perfect at a desk may be unreadable in direct sunlight.
Video calls with users and, where possible, short clips from the field: setting, device, time available, common slip-ups.
A first build shipped via TestFlight and the Google Play internal track, used by a few people in their actual jobs.
One team switches to the app for several weeks while the old notebook or spreadsheet runs alongside, and the differences are reviewed.
Roll-out to all users, short training videos and scheduled maintenance for each year's operating system updates.
Test the app on the oldest phone your team actually carries. A screen that scrolls smoothly on the developer's new flagship can freeze on a four-year-old budget Android out in the field. Add the weakest device in real use to the pilot list; it is the cheapest way to catch performance problems before launch.
No. Apple Business Manager supports private distribution, and on Android you can use managed Google Play or install directly through Intune. The app never shows up in public search and reaches only company devices.
Location is personal data, so the purpose has to be clear and staff must be informed through a privacy notice. We recommend a design that captures location only when a job is logged and never tracks people outside working hours. The legal assessment is a matter for your lawyer or KVKK adviser.
In most cases, yes. If the ERP has an API we connect directly; if not, through an intermediate service or file transfer. A queue with automatic retries makes sure nothing is lost when the link drops.
For a mid-sized app, updates, testing and resubmission usually add up to a few working days a year, billed at €55 per hour plus VAT. If you plan new features too, a monthly pool of hours is more practical.
We decide based on the devices your staff and customers actually use. Typically that means the last few iOS releases and the Android versions still in wide circulation. Supporting very old versions is discussed separately because of security and cost.
Who will use it, in what conditions and how often? We will propose the right format and a realistic scope for the first release.
We have your enquiry
A reply will reach you by the next working day at the latest. If your message says work has come to a halt, it goes to the top of the pile.
No such city in our list. Try another spelling, or just pick the closest big city: we work entirely over remote connections, so nothing about the service changes from one province to the next.
The only cookies here are the essential ones: they keep the site running and remember the city you picked. Nothing is used for advertising or tracking. See our privacy notice for more.