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

Mobile App for Beylikduzu businesses

Trade in Beylikduzu runs through rooms where the product is on show: showroom floors, sales floors, B2B sales counters. A buyer walks in, looks at the thing itself, and decides on the spot. The limit sits in that same room. A floor holds a set number of units, and the difference between two equipment packages is not something a shelf can display. A printed catalogue patches that gap, and it goes stale the moment a specification moves. The work closest to how this district sells is the KGM SsangYong showroom kiosk.

Get a quote Tell us about your project

Mobile App — Beylikduzu

The purchase moment in these rooms is physical and short. Someone measures a piece by eye, opens a door, then looks for somebody to explain how two versions differ. At a busy hour nobody may be free. The kiosk answers from a screen the business owns rather than from the visitor's phone, and that single decision shapes the rest of the build. On the business side, changing what the screen says stops being a print job: equipment detail reaches the device from the same codebase, so a revised specification no longer means recalling brochures from the floor. The application is written in React Native (Expo); no separate mobile stack was set up for the kiosk case.

  • Floor space stops deciding how much of the range a visitor sees: the screen carries units that are not standing in the room and puts equipment packages side by side.
  • The interface was set for a short session on foot rather than scaled up from a phone layout, so touch targets are larger, type is bigger and navigation stays shallow.
  • Device ownership is settled at the start rather than at handover: the application lives on the business's own screen, and a visitor browses without downloading anything or opening an account.

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 a shop floor cannot park

A showroom floor holds only so many cars and so many consultants, so the rest of the model line and the gap between trim levels stay out of reach while a buyer is deciding. The kiosk stands on that floor as a touchscreen the dealership owns: a visitor steps up, moves through the range, and reads how equipment packages differ without queueing for a salesperson. It runs on a single React Native (Expo) codebase, and revised equipment detail reaches the screen from that codebase instead of going back to a printer.

Read the case study →

Working with Beylikduzu 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 the application have to be installed on our customers' phones?

    No. It runs on a touchscreen the business owns, standing in the room where the product is. A visitor walks up and starts using it: nothing to download, no account, no personal details handed over.

  • What does it cost us to update the screen when product detail changes?

    A content change, not a print run. Equipment and specification detail reaches the device from the same codebase, so no batch of brochures has to be reprinted, collected and redistributed across the floor.

  • Can we show versions we cannot fit onto the floor?

    Yes. What the screen carries is not bound to the square metres of the room. A visitor moves past the units physically present and compares equipment packages on the same screen.

  • Is a kiosk the same job as a phone application?

    The stack is the same: one React Native (Expo) codebase covers both. The interface is not. A kiosk meets somebody standing up briefly, so touch targets grow, type gets larger and navigation depth is cut back.

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