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

Mobile App for Kadikoy businesses

Around Osmanağa and Caferağa, consulting rooms, studios and small service floors sit side by side, and any of them may already have a site plus a record kept indoors. When a phone app comes up, the conversation opens with design, and the decision that matters sits behind it: is the app one face of the record that already exists, or a second system holding its own data? Tahlil.com settled that at the start. The site, the doctor's panel and the patient's app are three faces of the same Laravel application.

Get a quote Tell us about your project

Mobile App — Kadikoy

Consulting rooms, studios and floors of advisers working by appointment give Kadikoy its texture. If what you want is a customer seeing a result on their phone, the decision sits behind the interface. Tahlil.com is the work nearest that shape. Where it does not overlap should be said: Tahlil.com is a health platform, so studio booking, retail loyalty or cafe ordering is not what it demonstrates. What does overlap is the structure — a website, a management panel and a mobile client as three faces of one core. Laravel runs the workflow, MySQL holds records, Redis the cache, Tailwind the screens; the mobile side is React Native (Expo) and notifications go out through OneSignal.

  • The app keeps no data of its own: what stands approved in the panel is what the phone shows, and no second copy has to be reconciled between them.
  • A notification follows the state of a record rather than a timer inside the app, so the OneSignal push fires off that same record once the reading is approved.
  • One React Native (Expo) codebase reaches both stores, and because the site and the panel already sit on that core, no separate API project is opened for the phone.

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 — site, panel and mobile app as three faces of one Laravel core

A patient enters test values and a specialist doctor writes the reading. The structural decision matters more: the website, the doctor's management panel and the patient's phone app are not separate systems but three faces of one Laravel core. The mobile side comes out of one React Native (Expo) codebase and reaches both stores; when a reading is ready the OneSignal push fires from that same record, and the app runs no schedule of its own. MySQL holds the records, Redis the cache, Tailwind the screens. Scope: this is a health platform, not a retail or booking build.

Read the case study →

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

  • We already have a site and a panel. Does an app need its own system?

    It does not. On Tahlil.com the site, the management panel and the mobile app hang off one Laravel core, so the app holds no data of its own and stands as one face of the record that already exists.

  • Who sends the notification?

    The state of the record does. When a reading is approved, the OneSignal push fires from that same record; the app runs no timer and keeps no separate send list on the side.

  • Does reaching both stores mean two projects?

    No. One React Native (Expo) codebase reaches both. Since the site and the panel already sit on the same core, no separate API project is opened for the phone.

  • Do you have a reference in Kadikoy?

    We have no client in this district and we do not claim one. What we point to is the work closest to the district's service texture: Tahlil.com. We work fully remotely and keep no office.

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