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

Software Consulting · Kadikoy

Software Consulting for Kadikoy businesses

The hardest part of an inherited system is often not the code but the box screwed to the door. Kadikoy's fabric leans on clinics, studios and small retail that runs by appointment. If your entry record lives inside such a box, it runs all day, it cannot come off the wall, and its data stays in its own memory. Software consulting in Kadikoy starts with a blunt question: does this step really need hardware, or is it only habit? On a building site we had no choice but to answer it.

Get a quote Tell us about your project

Software Consulting — Kadikoy

In a business that runs on appointments the door stays open all day, and staff cross the same threshold as customers. The work closest to this district's working conditions is the construction workforce attendance system. Where it does not match is plain: it was written for building sites, not for a clinic or a studio floor, and it was a new build rather than a system we inherited. What carries across is where the record starts: an entry forms from a QR scan joined with a location check, with no fixed reader behind it. Laravel takes the records, MySQL holds them, and the site app runs on a phone through React Native (Expo).

  • On a takeover we mark which step depends on hardware, because a step tied to a device does not get fixed by editing code: the record has to come from somewhere else first.
  • On the site system an entry comes from a QR scan joined with a location check; duration falls out of a matched entry and exit pair, and an entry left open stands as an incomplete record.
  • Nothing gets installed at the door: the app runs on the worker's own phone, which takes a maintained piece of hardware out of the setup you inherit.

Why Algoriel

  • We read the code first

    We did not build the KGM SsangYong corporate site; we read the inherited codebase and left the parts that worked untouched.

  • Fix where the load sits

    The same catalogue query hit MySQL on every page open; that read moved to a Redis cache and nothing else was disturbed.

  • We stay inside your framework

    On the KGM SsangYong site the inherited Laravel, Tailwind and jQuery set was kept; the cache layer was the one addition to the stack.

  • We reconnect broken chains

    At Resterm the calculation sat in a sheet, the catalogue in a file, the quote somewhere third; selection now runs to cart, project, and customer.

What we build

Software Consulting

  • Reading the code first

    We read the inherited codebase through, then name what moves and what stays untouched, one item at a time. The scope of the change comes out of that reading rather than a template.

  • Staying on the existing framework

    A library the maintaining team has never worked with would be a cost we left behind on our way out. KGM SsangYong's corporate site arrived with its framework and front-end libraries already chosen, and not one dependency was added to that set.

  • The limit of the change

    Only the slow places get opened; heavy spots are handled one at a time and the rest stays where it is. Where that limit falls is written down for you once the reading is done.

  • Tidying the file layout

    Scattered files move into a single naming and folder scheme. Which model uses which file becomes visible without reading code.

  • Taking weight off the reads

    The same query repeated for every visitor can be run once and shared from there. On KGM SsangYong's catalogue pages that query no longer runs until the data changes.

  • The decision taken before code

    Some decisions are made before the first line and are expensive to correct later. Resterm's software was built on the manufacturer's own product structure, because it was clear from the start that a general-purpose quoting tool would not carry it.

Work like this

Software Consulting · Case study

Construction attendance — a QR scan and a location check in place of the turnstile

A building site is temporary ground: no turnstile goes up and crews move between sites. Entries and exits are recorded through a QR scan and a location check: the code says who scanned, the location says which site. Duration comes from a matched entry and exit pair; an entry left open stands as incomplete until its exit is scanned. Progress payment is not held in a separate sheet, it is produced from those pairs. The site app runs on the worker's phone through React Native (Expo); Laravel takes the records, MySQL holds them. When the site closes, no hardware is left behind.

Read the case study →

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

  • Can you change anything without removing the device at the door?

    Things can change while it stays there, but as long as the record lives in the device's memory it cannot travel. On the site system we moved the record out of a device and onto a phone: the QR scan says who, the location says where. The same decision applies to an installation that keeps its reader: we change where the record comes from first.

  • What does a construction system offer a clinic?

    Nothing directly, and we say so; it was written for building sites. What travels is the shape of the record: an entry and an exit as a matched pair, duration derived from that pair, and an open entry standing as incomplete. A threshold on an appointment floor is still a threshold.

  • Was the site attendance system written by your team alone?

    No, we did not. Development on the construction workforce attendance system was shared with another team. What matters on your side is that the design of the record sits in writing: an entry is created from a QR scan joined with a location check, and duration falls out of the matched pair. A takeover conversation runs off that same document.

  • We do not want to drop the program we already use.

    You do not have to. In consulting we trace which record comes from which screen. If a staff entry is written both into the door device and by hand onto a sheet, the thing to fix is that second writing, not one of the programs. Once there is a single source, the old program can stay where it is.

Software Consulting in other cities

The other cities where we publish this service are below, grouped by province.

Other services for this location

Would you like us to read the system you already have?

Get a quote or open the service