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

Mobile App for Bakirkoy businesses

A result sheet leaves a clinic in Bakirkoy and gets read somewhere else entirely: in a car, at a kitchen table, at one in the morning. Whoever could have explained the abbreviations is back in the building. That is the hour when a phone stops being a shop window and becomes the place where the reading actually happens. Tahlil.com is built around it. A value goes in from the app, and a specialist reading is written onto the same record.

Get a quote Tell us about your project

Mobile App — Bakirkoy

Private health providers and the street-level retail along Incirli sit next to each other across Bakirkoy. The work of ours that lands closest is Tahlil.com. It is worth naming where it does not line up: this is not a laboratory information system. Instrument integration, sample tracking and lab workflow fall outside what we can show, and we have no hospital or clinic chain as a client here. What carries across is the shape of the record. An entry and a specialist reading meet on one record, and the phone holds no copy. The app is React Native (Expo), with a Laravel core, MySQL records, a Redis cache and OneSignal behind it.

  • A patient types the value into the app, and when the reading is written that same record updates, so no second copy of a result forms on the phone.
  • An AI pre-reading is prepared, but the text a patient receives is written and approved by the doctor in the panel, and responsibility stays with whoever approved it.
  • Once a reading is approved a OneSignal push calls the patient back to that record, so nobody has to keep opening the app to check.

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

Tahlil.com — a value goes in from the phone, the approved reading lands on it

A patient enters test values and a specialist doctor writes the reading; the final wording that reaches the patient comes from the doctor. The mobile side ships to both stores from one React Native (Expo) codebase and keeps no data of its own, so what the app shows is the record the panel writes into. An AI pre-reading is prepared, the doctor approves it, and the moment a reading is approved a OneSignal push calls the patient back to the result. The scope line, plainly: this is not a laboratory information system, and we have nothing to show on instrument or sample workflow.

Read the case study →

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

  • Could we send the result as a link instead of putting an app on a patient's phone?

    For a one-off result, yes, and we say so. An app earns its place once the same person's records start to accumulate and somebody has to be told the moment a reading is ready. A link carries neither of those jobs.

  • Who writes the reading, and where does approval happen?

    A specialist doctor writes it and approves it in the panel. An AI pre-reading is prepared first, but the last word on the text belongs to the doctor, and nothing unapproved appears in the app.

  • Have you delivered this to a health provider in Bakirkoy?

    No. We have no client in the district, we keep no office and we work fully remotely. Tahlil.com sits on this page for the shape of its record, not for an address.

  • Can you pull results straight off our laboratory instruments?

    That is not work we can show. In Tahlil.com the value is entered by the person holding the result, and instrument integration, sample tracking and lab workflow stay outside the scope.

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