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

CMS · Tuzla

CMS for Tuzla businesses

Whoever steps up to the screen is between two jobs: on their feet, gloves in hand, a few minutes to spare. Asking that person to install an app, open an account or leave an email address is, in practice, asking them not to look. Heavy industry around Tuzla's shipyard belt runs at that pace, and the minutes in front of a screen go to what is being shown rather than to a form. The KGM SsangYong showroom kiosk drops all of those steps.

Get a quote Tell us about your project

CMS — Tuzla

Shipyards and heavy industry set the rhythm in Tuzla, and a display surface in that setting is a shared screen at the edge of a working area rather than a polished shopfront. Nobody standing in front of it introduces themselves, signs in, or leaves a trace behind. The closest work we have to that condition is the KGM SsangYong showroom kiosk. Where it does not reach, plainly: it was made for an automotive shop floor, we have no ship or shipyard software to show, and production tracking is not this screen's job. What carries over is that with nothing collected, the whole burden of explaining rests on the content. The app runs from one React Native (Expo) code base. We keep no office and work remotely.

  • There is no download, no account and no personal data step, so with neither a consent screen nor a form standing in the way, the content has to be complete on its own.
  • The interface is not a phone app scaled up: touch targets, type size and navigation depth were set for short use while standing.
  • When a detail changes no brochure is reprinted, because the update reaches the devices from the same React Native (Expo) code base.

Why Algoriel

  • Print becomes editable

    Çatalca Merkez Kasap moved a printed menu to a QR page, so a price change is an edit rather than a reprint.

  • Content gets an address

    Each menu section carries its own address, so a customer can link straight to the section they came for.

  • The institution authors

    Teachers on Vipkurum write their own lessons, tests and exams, so publishing does not wait on a developer.

  • Fixed code, editable page

    QRVizit fixes the printed address once; the page behind it stays editable. We are still building it.

What we build

CMS

  • Content modelling

    Which content types exist, and which fields each one carries, follows your own publishing work. At Vipkurum the assessment type is not hard-coded, so European and Turkish standards sit side by side on the same foundation.

  • The editorial interface

    The person writing and the visitor reading see the same information, with no second copy waiting to be synchronised. Keeping the admin panel and the published side in one application means the content is not held in two places.

  • Addresses and links

    Every page and every section carries a permanent address of its own, so a shared link always opens the same place. At Çatalca Merkez Kasap the menu is split into sections, and codes on different tables land on different points of the same page.

  • Access and permissions

    Who sees what, and who may change it, is defined together with the content type. At Vipkurum a teacher, a student, a parent and an administrator read the same lesson programme at their own level of permission.

  • An update is not a reprint

    When a price, a phone number or an address changes, the printed material stays as it is and the page is updated instead. Çatalca Merkez Kasap keeps its menu as text, so a price change never reaches the printer.

  • Repeat reads

    When the same page is opened again and again, it is served from a ready copy rather than rebuilt each time. QRVizit, still under development, opens a repeatedly scanned card that way.

Work like this

CMS · Case study

KGM SsangYong showroom kiosk — no download, no account, content carrying the explanation

A vehicle browser running on a touchscreen on the KGM SsangYong shop floor. It sits on the store's device rather than the visitor's, and nothing stands in between: no download, no account, no personal data left behind. That puts the whole burden of explaining on the content. A visitor walks the full range and compares trim differences at their own pace, and the number of cars on the floor does not limit what the screen shows. The interface was built for short use while standing, and it runs on React Native (Expo), so a changed detail updates the screen instead of a brochure.

Read the case study →

Working with Tuzla 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 we collect a name or a phone number from whoever uses the screen?

    Not in this arrangement, and that is the distinction: the visitor reaches the content with no download, no account and no personal data step. A flow that collects data is separate work — the record, the consent text and the retention duty arrive together, and we scope those before promising anything.

  • Who updates what appears on the screen? Do the devices have to be handled one by one?

    The update comes down from the same code base. On a printed brochure a changed trim detail meant a new run; here the detail moves to the screen and the device on the floor stays as it is.

  • Do you have kiosk work built for a shipyard in Tuzla or for heavy industry?

    No, and we say so plainly: the work we have was made for an automotive shop floor. We have no ship, shipyard or marine software to show. What carries across is not the sector but the working condition of the screen.

  • Do you install the screen? Does someone come to the site?

    We do not supply hardware. We keep no office and nobody travels to a site; our part is the application running on the device and how its content gets updated.

CMS in other cities

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

Other services for this location

Let's talk about who will manage your content.

Get a quote or open the service