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

CMS for Basaksehir businesses

A mould shop with two machines in its display corner keeps the rest of the range in a printed folder, and whoever walks up to that folder is not stopping to install anything on a phone. Machine build and tooling work run dense around Basaksehir's Ikitelli estate, so once the screen belongs to the business the content question moves: who edits what it says, and off which record? The KGM SsangYong showroom kiosk was written for exactly that condition. Nothing is installed on a visitor's device; the app sits on the shop's own touchscreen.

Get a quote Tell us about your project

CMS — Basaksehir

In Basaksehir a machine or mould shop can keep very little floor for display: a couple of bodies fit, the rest goes into a folder, and the folder ages the day a specification moves. The work closest to this district's sector profile is the KGM SsangYong showroom kiosk. The limit belongs in the open: the job was done on an automotive shop floor. Bench loading, production scheduling and drawing archives are not things we can show, and the kiosk takes no orders. What carries across is ownership of the surface: because the screen belongs to the business, changing what it says stops being a print run. One React Native (Expo) codebase feeds the device.

  • The screen is the shop's own hardware, so a corrected specification reaches it from a single codebase rather than going back to a printer.
  • The interface is not a phone app scaled up: touch targets, type size and navigation depth were set for a short visit taken standing.
  • The surface stays deliberately narrow, browsing only, with no basket and no payment step, while the number of bodies on the floor never caps what the screen can show.

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 — the shop owns the screen, one codebase feeds it

The app runs on a touchscreen on the shop floor. A visitor walks the whole range without waiting for an adviser and compares trim packages on the same screen. Nothing is installed on the visitor's device: the app lives on the shop's own hardware, and because the surface belongs to the business, refreshing it becomes a publishing job. When a trim detail changes, no brochure is reprinted — the change reaches the device from the one React Native (Expo) codebase. The scope is small on purpose: browsing only, with no order, payment or stock layer.

Read the case study →

Working with Basaksehir 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 build moulds and machines in Basaksehir, not cars. What does this kiosk say to us?

    It was written for an automotive shop floor and we say so plainly. What carries across is not the vehicle screens but the shape of the surface: the whole range lives in one place, and a body too large for the display corner is still walked through on the screen. Swap the vehicle for a machine and the arrangement holds.

  • We do not want visitors installing anything on their phones.

    They do not have to. The hardware already stands in the room, so a visitor touches the screen and starts. Who owns the device shapes everything above it, and content management stays behind that same device.

  • Who edits what the screen says afterwards?

    The business does. A corrected trim detail never reaches a printer; it travels from one codebase down to the devices. That is the honest measure of a content system: when one attribute changes, how many separate places have to be edited.

  • Would you not need to come to the workshop to set the screen up?

    No. There is no office of ours to visit and we do not work on site. The hardware is already on site; what we build is the model behind what it displays.

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