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

Mobile App for Sariyer businesses

Technology offices and head offices are dense on the tower floors around Maslak and Ayazaga. The costliest screen in an app, meanwhile, is the sign-up screen: someone installs it, meets the account step, and leaves before finding out what they were going to get. Tahlil.com splits the door in two: the tahlilmatik calculators ask for a single value and hand back a reading for it. Mobile app development in Sariyer, Istanbul starts there, at the first screen rather than the feature list.

Get a quote Tell us about your project

Mobile App — Sariyer

Technology offices, university spin-outs and head offices sit side by side along the Maslak and Ayazaga line, and what they share is not scale but first contact. The build is ready, the app is in the store, and nobody sees what it does before opening an account. The work closest to this district's profile is Tahlil.com, and the mismatch is worth stating: it was written for health technology, so for a finance product, a banking app or a payment flow we have nothing to show and promise nothing. What carries across is where the door opens. The core is Laravel, MySQL keeps the records, Redis takes the cache, Tailwind shapes the interface, and the React Native (Expo) client reads that same core.

  • A calculator asks for one value and shows where that value sits against its reference range, so a first reading needs neither an account nor an appointment.
  • The calculator is not a separate product: it hangs off the same Laravel core as the site, the clinician panel and the phone client, so no second codebase and no second content set appear.
  • How far the door opens is written down as well: a calculator returns a reading rather than a diagnosis, and the specialist's comment stays a separate, approved step.

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 — the calculators open a second way in, with no appointment

The main flow is plain: a patient enters test values, a specialist writes the comment. The friction sits at the door: nobody sees what the platform does before opening an account. The tahlilmatik calculators split that door. Somebody types one value, reads where it falls against its reference range, and is inside without booking. The calculator is not a separate build: it hangs off the same Laravel core as the site, the clinician panel and the React Native (Expo) client, with MySQL keeping records and Redis the cache. What it hands back is bounded: a reading, not a diagnosis.

Read the case study →

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

  • What can somebody do in the app before opening an account?

    Use the tahlilmatik calculators: type a single value and read where it falls against its reference range. A record and an appointment come in only when an interpreted result is wanted, so neither is a condition of first contact.

  • Did you write the calculator as a separate app?

    No. It hangs off the platform's own core, and the site, the clinician panel and the phone client all feed from there. Written separately, the same content would be maintained twice and the two copies would drift apart.

  • Do we need two apps written for the two stores?

    You do not. It comes out of one React Native (Expo) codebase and the entry screen behaves the same in both stores. Every phone app that leaves our desk is built that way.

  • We are not in healthcare. What can Tahlil.com show us?

    It speaks about the door, not the sector. Tahlil.com was written for health technology, and in finance or banking we have nothing to show. What carries across is this: a small tool that asks for one piece of information pushes the registration wall past first contact.

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