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 · Fatih

Mobile App for Fatih businesses

Service work in Fatih moves street by street: a boiler in a han above Küçükpazar, a unit in the back kitchen of a small hotel near Sirkeci. Whoever is at the counter answers the phone and names an hour, while the technician's actual day sits on the technician's phone. Both sides work correctly; neither sees the same day. AlgoKlima removes that split — the office panel and the field app write into one set of records, so nothing has to be merged at closing time.

Get a quote Tell us about your project

Mobile App — Fatih

Addresses on the historic peninsula sit close together, but getting inside costs time: narrow streets, no parking, a steep han stair. A technician changes address all day. AlgoKlima is the work closest to that pattern — our own product, and we carry its upkeep. Where it does not overlap is plain: AlgoKlima was written for air conditioning, boiler and appliance service, so a wholesale food trader's order flow or a guesthouse's booking ledger is not work we can show. What overlaps is not the equipment but the way the office and the field meet on one record. The panel runs on Laravel with Inertia and Tailwind; the field app is React Native (Expo). Both sit on the same MySQL core, with Redis carrying the read load.

  • A call opened at the counter and a job closed in the field are two ends of one record, so the panel holds the job as closed the moment the technician closes it and nobody types the day in again at night.
  • Customer, unit and job sit in one place, so the office opens the same customer card the field already sees and a second customer list never grows on the other side.
  • The phone app is React Native (Expo) and the panel is Inertia, both built on one core, so no transfer service runs between them.

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 — office panel and field app share one set of records

Our own product: a system we keep updating rather than a build handed over and left behind. The office panel runs on Laravel with Inertia and Tailwind, the field app on React Native (Expo), and they are not two products but two faces of the same MySQL core, with Redis carrying the read load. The office opens a call, the technician closes that same record on site, and both sides work off one customer and unit record. The scope is stated too: AlgoKlima was written for air conditioning, boiler and appliance service. A wholesaler's order book or a guesthouse's front desk lies outside it.

Read the case study →

Working with Fatih 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 the counter panel and the technician's phone show the same job?

    Yes, because they are not two products. The office panel is built with Inertia, the field app with React Native (Expo), and both write into the same MySQL core. When the technician closes a job, the panel already holds it closed.

  • The signal is weak in a han basement. Can a job be opened there?

    It can. The record is created on the phone and lands in order once the connection returns. That is not what this page turns on, though: the point here is that the office and the field write to the same record.

  • We are a small team. Is software early for us?

    If the day closes on one sheet with one person, then yes, and we say so. The line starts where whoever answers the phone cannot see the field, and the day gets typed in a second time at night.

  • Would you not need to come in to set it up?

    We keep no office, and the work is fully remote. The first session is not about screens: we settle who opens a call, who closes the record, and when the panel is meant to see it.

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