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

Software Consulting for Esenyurt businesses

A request heard often in a takeover is a new screen: we would like an app as well. Yet an app built as a second system brings its own records, its own login and eventually a person reconciling one against the other. Software consulting in Esenyurt looks at that first: can the new surface attach to the existing install, or does it get set up beside it. In Tahlil.com the site, the panel and the app all read the same records.

Get a quote Tell us about your project

Software Consulting — Esenyurt

Esenyurt's fabric leans on small businesses, multi-branch operations and private education. If your branches close at different hours there is no point in the day when the system sits idle, and improvement gets planned on the live version. The work closest to that condition is Tahlil.com. The gap, written down: the platform sits on the health technology side, and we have nothing to show for a course branch's timetable or its attendance register. What carries across is how a surface gets added: the app does not open a second set of records, it reads the same ones. Underneath sits Laravel, with MySQL holding the records and Redis the cache; Tailwind carries the interface, React Native (Expo) the mobile side, OneSignal the notification.

  • The website, the admin panel and the mobile app all attach to one Laravel install, so adding a surface does not open a second set of records.
  • React Native (Expo) ships one codebase to both stores, and OneSignal pushes a notification to the user the moment a record is ready.
  • The limit is written down: timetables, branch attendance and course collections sit outside this work and we have nothing to show there.

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

Tahlil.com — the site, the panel and the mobile app read one Laravel install

A patient enters test values; a specialist doctor writes the interpretation. The website, the doctor's panel and the notification-sending app attach to one Laravel install, so a new surface never means a second system. The tahlilmatik calculators open a second way in without an appointment: a patient enters one value and sees which reference range it falls into. AI prepares a first reading, the doctor writes and approves the interpretation in the panel, and OneSignal pushes a notification when it is ready. The text reaching the patient leaves the doctor's hand.

Read the case study →

Working with Esenyurt 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 work without stopping the system? Our branches do not all close at the same time.

    That is how we work. We break a change into small pieces and write down which record each piece touches. The order starts at the shared records and the surfaces follow, so one surface can be updated while the others keep reading the same record.

  • We want a mobile app but we do not want to throw away the panel we have.

    You do not have to. In Tahlil.com the app is not a copy of the panel; it is another face of the same install. React Native (Expo) ships one codebase to both stores and reads the records from the same place the panel does.

  • Was Tahlil.com built by your team alone?

    No, it was a joint build. The question worth carrying over is the next one: can a surface be added without opening a second system? On Tahlil.com the notification app attached to the records the site was already reading, and that is the test to put to your own system.

  • Tahlil.com is health technology. We run courses and branches.

    The sector does not travel. What does is this: how many surfaces read a record should not change how many times it gets typed. On a course floor there is still one record, and the site and the panel read it from the same place.

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