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

Mobile App for Basaksehir businesses

A mould shop or machine builder around Ikitelli finishes only part of the job on its own floor. The machine is commissioned at the buyer's plant, and a crew stays out there for weeks. Whatever counts hours at the workshop gate never sees them, because that count is tied to one device at one address, and there is nothing to install at the other end. Construction workforce attendance starts from the opposite premise: the site is temporary, so an entry binds to the place it was scanned.

Get a quote Tell us about your project

Mobile App — Basaksehir

Machine manufacturing and mould workshops fill the Ikitelli line in Basaksehir, and what gets built there is installed somewhere else, sometimes in another province. The work of ours closest to that pattern is construction workforce attendance. Where it does not line up should be said out loud: the system was written for building sites, and we have nothing to show on assembly steps, commissioning or quality records. Warehouse and dispatch operations fall outside it too. One rule carries across: the site need not be permanent, only the record does. The app runs on the worker's own phone in React Native (Expo), Laravel takes the entries and MySQL keeps them.

  • A QR scan supplies who, a location reading supplies where, and the two meet in one entry, so a site is never picked by hand off a list.
  • Time comes out of a matched entry and exit, so an entry with no exit scanned against it stays open rather than counting as a finished shift.
  • When the job ends there is no hardware to take down, because the system lives on phones the crew already carry and nothing is installed at the next address.

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

Construction workforce attendance — a temporary site, an entry bound to a location

A building site is temporary and people move between sites, so no turnstile goes in. Entry and exit run through a QR scan and a location check: the code says who scanned, the location says which site, and both land in one record. Time comes out of the matched pair, and progress payment is produced from those same records, not a separate sheet. The app runs on the worker's own phone from a React Native (Expo) codebase, with Laravel taking entries and MySQL holding them. The scope line: written for building sites; assembly steps, commissioning and quality records fall outside it.

Read the case study →

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

  • Our crew works inside a customer's plant and we cannot install anything there. What does this system need?

    Nothing installed. The record is created in the app on the worker's phone: the QR code establishes identity, the location reading establishes the site. When the job ends no equipment is left behind.

  • Is a worker's location tracked continuously?

    No. Location is captured as a field on the record at the moment an entry or exit is scanned. Nothing is logged in the hours between; what the system knows is the two scans.

  • Could we track the assembly steps of a machine as well?

    Not something we can show. The system was written for entry, exit and progress payment on a building site, so assembly steps, commissioning and quality records stay outside it.

  • What happens if somebody forgets to scan out?

    The record stays open. Because time comes from a matched pair, an incomplete entry is never presented as a finished shift, and the correction is made on that record itself.

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