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

Mobile App for Kartal businesses

Repair yards and device service firms are dense off Soğanlık and around Cevizli. In that kind of work a part leaves the shelf mid-job. Nobody walks back to a desk with oily hands to fill in a form: the part goes on, the paper waits for evening. What goes missing is not the part but which job it went to. On AlgoCar that line is written from the phone into the work order, and the stock movement is deducted from that record, not typed in again at the store.

Get a quote Tell us about your project

Mobile App — Kartal

Manufacturing and repair sit next to each other in Kartal, and several jobs open in a day off one shelf. The fitter is at the bench, the store is on another floor, and the record ends up somewhere between them. AlgoCar is the work closest to that habit — our own product, whose releases we cut ourselves. Where it does not overlap: AlgoCar was written for vehicle servicing, so machine park planning, bench scheduling and the procurement side fall outside it. What carries over is which record a part leaves the shelf on. The field app is React Native (Expo) and the panel is Inertia with Tailwind, both attached to one Laravel core; MySQL holds the records and Redis sits in front of the lists opened all day.

  • The part is written to the work order at the shelf while the job is open, and the stock line follows from that entry, so nothing waits to be keyed in on the store side.
  • Jobs opened on the same day do not blur together, because which part went to which order is held in the record itself and no evening reconciliation step appears.
  • Part entry is not free text, so a gap between a count and the job record can be read back down to individual work orders.

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

AlgoCar — the part is written from the phone, stock moves off that record

Our own product, built around the vehicle that comes into the workshop rather than handed to a client and left behind. The mechanism is narrow: a work order opens, the part consumed is written to it, and the fall in stock follows from that entry. No second line waits to be keyed in on the store side. The field side is React Native (Expo), the panel Inertia with Tailwind, and both attach to one Laravel core; MySQL holds the records and Redis sits in front of the lists opened all day. Scope: AlgoCar was written for vehicle servicing, so production plans, bench schedules and procurement stay outside it.

Read the case study →

Working with Kartal 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

  • Does writing the part from a phone slow the fitter down?

    The writing already happens; only its place changes. The part goes onto the open work order at the shelf, and the evening step of copying paper across disappears, so the total work goes down rather than up.

  • We service machines and devices, not vehicles. What carries over to us?

    AlgoCar is vehicle service software and we do not dress that up. What transfers is where the stock movement comes from: the order is open, the part is written to it, the shelf falls from there. Put a serial number on the order instead of a plate and the rule holds.

  • Do we install it on the fitters' own phones?

    Yes, a separate device fleet is not required. One React Native (Expo) codebase reaches both stores, and the step of writing a part sits in the same place on either platform.

  • Does this hold for the device service firms around the health campus?

    As a mechanism, yes: the part is written to an order and stock falls from it. But we have no work to show in that sector and we claim no institutional reference there. The evidence we stand on is AlgoCar.

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