EN TR
Get a quote
View all services
Web software

One app carries the brochure pages and the request queue.

System architecture

The pieces and their boundaries are settled before code.

Enterprise & commercial software

Several institutions, one system, records kept apart.

Mobile app

One codebase, both stores: iOS and Android.

Software consulting

We take a running system over and improve it.

AI consulting

AI only where the problem actually calls for it.

Get a quote
EN TR

Mobile App · Tuzla

Mobile App for Tuzla businesses

Mobile app development in Tuzla, a shipyard and heavy-industry district of Istanbul, starts from one condition: the work happens inside closed steel volumes — a ship's hold, the inside of a tank — where the signal stops. An app that waits for a network is useless there. The record has to be created on the phone and closed there. AlgoKlima is the system of ours built for that, and it is our own product.

Get a quote Tell us about your project

Mobile App — Tuzla

Along the shipyard strip in Tuzla the work happens inside enclosed steel volumes, where coverage stops. The honest part comes first: the sectors do not line up. AlgoKlima was written for air conditioning, boiler and appliance service, not for shipyards or heavy manufacturing. What lines up is the working condition. A crew moves between enclosed spaces, and a record must be complete and closed before the signal returns. So what the phone holds is not a retry buffer waiting on the network; it is the record itself. The queue empties in the order jobs were opened. The office panel keeps running while a phone sits outside coverage. We work fully remotely and keep no office.

  • A job is written into the phone's local queue the moment it opens, so saving and sending are not two separate steps and nobody on the crew has to decide when to transmit.
  • The queue empties in the order jobs were opened, so entries that piled up during hours without signal reach the panel in the order events happened, not in the order the connection came back.
  • The app writes into the same record the panel carries, so no second data store sits under the phone waiting to be reconciled with the office, and no separate mobile copy of a job forms.

Why Algoriel

  • The field team works from the phone

    A record opens where the work happens, so nobody drives back to the office to type it in again.

  • A screen instead of a brochure

    The SsangYong showroom kiosk runs on the shop's own device; a visitor never downloads an app, opens an account or hands over personal data.

  • A state change pings the phone

    When a Tahlil.com record changes state the notice reaches the phone, so nobody calls in to ask for a result.

  • One app, both stores

    Phone apps are written on a single framework, so there are never two native codebases to keep in step.

What we build

Mobile App

  • The platform follows the job

    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.

  • An interface built for the moment of use

    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 services behind the 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.

  • Who made the entry, and where

    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.

  • Working with no connection

    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.

  • Which device it lands on

    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.

Work like this

Mobile App · Case study

AlgoKlima field app — the record is created on the phone, the queue keeps its order

Our own product: a system whose upkeep we carry, not a build handed over and left behind. The field app comes out of one React Native (Expo) codebase, and the panel behind it runs on Laravel with Inertia and Tailwind; both sit on the same MySQL core, with Redis carrying the read load. What the app holds on the phone is the record itself, and the queue empties in the order jobs were opened. The hard part is named plainly: panel and app can change the same record without knowing about each other, and conflict resolution merges both edits into one record rather than dropping one.

Read the case study →

Working with Tuzla teams, remotely

We have no office, so work for this city runs remotely and we do not offer on-site support. What was done, and why it was done that way, stays in writing. The project pages mark which builds came out of a partnership.

  • The first release ships as a working piece; extras follow later.
  • Every client we know of is in Turkey.
  • Decisions stay in writing; progress shows in working screens.

Frequently asked

  • Do you have an office in Tuzla, or a crew that visits sites?

    No office — we work fully remotely. We do not start with screen designs either: first we settle which record is created in the field and by what rule the queue empties.

  • What happens to entries when a crew spends hours with no signal?

    They stack up and arrive in the order they were opened, so the panel reads the day as it happened. We quote no figure for how many pile up — we never measured one.

  • The crew use their own phones and the fleet is mixed. Does the offline part break?

    The app comes out of one React Native (Expo) codebase, so the queue behaves the same on both platforms. No phone becomes the privileged one where syncing works.

  • Would an off-the-shelf field app do the job for us?

    If the crew stays in coverage and the work is a form and a photo, then yes, and we say so. The line starts where a record must close with no connection and the office edits that same record.

Mobile App in other cities

The other cities where we publish this service are below, grouped by province.

Other services for this location

Tell us where your app will be used.

Get a quote or open the service