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

Mobile App for Atasehir businesses

Nobody on a head-office floor along Atasehir Bulvari sees where the work is done; what they read is a report. And a report can shrink to one total: hours this month. If the same person worked on several sites during that month, the total says nothing about which job took which hours. On the construction workforce attendance system we tied the record to a person-and-site pair rather than to the person alone. That is where mobile app development in Atasehir, Istanbul starts for us.

Get a quote Tell us about your project

Mobile App — Atasehir

What software has to carry is the distance between a head-office floor and the address where the work happens. Decisions are made in Atasehir, the work turns elsewhere, and a report stands between them. The closest work we hold is the construction site attendance system. The business does not match: it was written for building sites, and we have no bank or insurer to show. What matches is the split the record carries — one row holds the person and the site, so the same worker's hours at different sites add up separately. Head office reads a per-site report out of those records, not a second spreadsheet. The app runs on the worker's phone in React Native (Expo); Laravel takes the entries, MySQL keeps them.

  • One row of the record holds the person and the site together, so the same worker's hours on two different sites never melt into a single total.
  • The per-site report head office reads comes out of the entries themselves rather than a parallel spreadsheet kept alongside them.
  • When somebody moves to another site no new person record opens: the person stays the same and the site is the part that changes.

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 site attendance — one row holds the person and the site together

Workers do not stay at one address; the same person turns up on several sites in a month. So the record carries which site as well as who and how long. One row holds the person and the site, and the same worker's hours at different sites add up on their own. Head office reads a per-site report out of those entries, not a spreadsheet beside it. The app runs on the worker's phone in React Native (Expo); Laravel takes the entries, MySQL keeps them, and nothing is left on site to remove when it closes. The limit: it was written for building sites, not a finance branch operation.

Read the case study →

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

  • How do we read from head office who worked on which site?

    Out of the entries themselves. Because one row carries the person and the site together, a per-site total is not calculated separately — the report is those same entries, read. Nothing has to be merged from a second list at month end.

  • The same person works on two projects. Which one gets the hours?

    Both, without mixing. The person stays one; the site is what changes, and each site's hours add up on their own. A month never collapses into a single figure for one worker.

  • We run branches, not building sites. What does this say to us?

    We say plainly that it was written for building sites; we have nothing in finance or insurance to show. What transfers is the split the record carries: the person and the place worked sit on the same row.

  • Do you have an office in Atasehir, and do you have to come out to install it?

    No office — we work fully remotely. There is nothing to come and install either: the app goes onto phones, sites are defined from the central panel, and no device is left standing anywhere. The first thing we discuss is not a screen but which detail belongs on which row.

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