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

Mobile App for Uskudar businesses

In an institution the first question is answered by whoever sits at the counter. At a busy hour that person is with somebody else, and the queue is made of people waiting to ask. Private clinics and course centres are dense between Baglarbasi and Kisikli. Mobile app development in Uskudar, Istanbul therefore starts from the waiting. On the KGM SsangYong showroom kiosk a visitor moves through the whole range at their own pace, without waiting for a consultant to come free.

Get a quote Tell us about your project

Mobile App — Uskudar

Consulting rooms, course centres and appointment-led service offices give Uskudar its texture. Where first contact happens at a counter, one person serves one visitor at a time. The work closest to how these places run is the KGM SsangYong showroom kiosk. The mismatch belongs in writing: it was made for an automotive shop floor, so for a screen carrying institutional records, an appointment book or patient and student data we have nothing to show. What carries across is this: where a visitor can move on their own, the expert's time is left for the question that actually needs an expert. We wrote the application in React Native (Expo), with no second mobile stack for the kiosk surface.

  • A visitor moves through the whole range without waiting for a consultant to come free, which leaves the expert's time for questions that need a conversation.
  • Differences between equipment packages are read side by side in one view instead of being recounted aloud, so the comparison follows the visitor's own order.
  • No institutional record forms on the screen: a visitor browses without leaving a name, a phone number or any other personal detail, so nothing is left behind to keep.

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

KGM SsangYong showroom kiosk — the range read without queueing for a consultant

On a shop floor one consultant serves one visitor, so at a busy hour the person with a question joins a queue and the decision cools there. The kiosk lifts that bottleneck off the person. A visitor steps up to the screen, moves through the range at their own pace and reads how equipment packages differ side by side; the only question still worth queueing for is the one that genuinely needs a conversation. We wrote it in React Native (Expo). The context is plain: this is an automotive shop floor, not a screen holding institutional records or appointments.

Read the case study →

Working with Uskudar 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 this screen replace the person at the counter?

    It does not. What it takes is the first, repeating question: what is on offer and how the options differ. What stays with the person is the question that needs a conversation, and at a busy hour the queue goes to that instead.

  • Does a visitor leave any details on the screen?

    None. No institutional record forms there: no name, no phone number, no other personal detail is asked for. A record that is never kept needs no protecting either, so nothing comes back as a duty on the institution's side.

  • We run a clinic and a course centre. What does an automotive kiosk say to us?

    It speaks about the waiting rather than the sector. The kiosk was made for an automotive shop floor; for a screen carrying institutional records, an appointment book or patient and student data we have nothing to show and promise nothing.

  • Does somebody from your side need to stand by the screen?

    No. The kiosk runs on its own: a visitor arrives, browses and walks away. Each person decides what to open next, so nobody on your side moves the screen along. On our side there is no office and the work runs remotely.

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