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

Mobile App for Pendik businesses

Around the Dolayoba and Seyhli industrial estates in Pendik, an assembly crew may spend its day on somebody else's property, where no turnstile stands and there is nowhere to bolt one. Mobile app development in Pendik, Istanbul therefore starts from a hardware question: what records the entry? On the construction workforce attendance project the answer is the phone in the worker's pocket. A QR scan says who, a location check says where.

Get a quote Tell us about your project

Mobile App — Pendik

If your payroll sits at head office while the work happens at the customer's, and one person passes through several premises in a week, an entry record in Pendik cannot hang off a fixed gate. The work closest to that condition is construction site workforce attendance. It was written for building sites, not for a factory floor: production lines, machine capacity and shift planning fall outside it, and we have nothing to show there. What carries across is the removal of hardware — a phone instead of a fixed reader, a location check instead of a gate. The field side runs on React Native (Expo), Laravel receives the scans and MySQL keeps them. We keep no office and install nothing on site.

  • What records an entry is not a box on a gatepost but the worker's own phone, so moving to a new address brings no hardware to mount, wire or take down.
  • The QR scan settles whose entry it is and the location check settles which site it happened on, so nobody picks a site name off a list.
  • Earned time is kept in no second table; it comes off closed entry and exit pairs, and an entry whose exit was never scanned stays open as an incomplete record.

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 attendance — a phone instead of a turnstile, location instead of a gate

A gate on a building site exists only while the job does, and buying a fixed reader means mounting it and later taking it down. So we put no device on the gate. Entry and exit come off a QR scan on the worker's phone, and a location check says which site the scan happened on; the two land in one record, so no site name is picked from a list. An entry whose exit was never scanned stays open as an incomplete record. Earned time sits on the closed pairs rather than in a second table. The field app runs on React Native (Expo); Laravel receives the scans and MySQL keeps them.

Read the case study →

Working with Pendik 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 have a turnstile at our own gate. Does it have to come out?

    No. If a device works at a gate you own, leave it there. This mechanism is for the places with no gate: when a crew is on somebody else's premises or the site is temporary, the phone takes the reader's job and nothing has to be installed there.

  • Our crew enters several addresses in a day. Does each one need setting up?

    It does not. An address is a piece of information inside the record, not a hardware job. Because the location check settles where a scan happened, a new address amounts to a new site entry in the system.

  • It was written for building sites. What does it say to a manufacturer?

    It speaks about the shape of the record rather than the sector: who, where and when meet in a single scan. Watching a production line, machine capacity and shift planning sit outside this scope; we have nothing to show there and promise nothing.

  • Who built it, and does somebody come out to install it?

    We built it with a development partner, and nobody comes out. No reader is mounted at a gate, so a site that closes leaves nothing to take down. The record travels with the phone rather than the building, and your crew leaves an address without leaving equipment behind.

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