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

Mobile App for Catalca businesses

Out in Catalca a printed piece of promotion is not just a cost line, it is a journey: designed in the city, printed in the city, then carried out here in boxes. Change a price or a specification and the same route gets walked again, and because what was handed out never comes back, the old version stays in circulation a while longer. The KGM SsangYong showroom kiosk shortens that route. The promotion sits on a screen, and an update reaches the device from the same codebase.

Get a quote Tell us about your project

Mobile App — Catalca

Catalca runs on food retail and small-town commerce, at some distance from the city. Merkez Kasap really is here, and Catalca is the only district where we can name a client beside it. That work is not the evidence for this page, though. Its QR menu is a web page a visitor opens on their own phone, not an application on the shop's device. The evidence here is the KGM SsangYong showroom kiosk, and it does not line up everywhere: it was written for a car showroom, and we have no screen application running in food retail. We have never built farming or livestock software either. The kiosk itself is a React Native (Expo) application.

  • When what the screen says changes, nothing has to be reprinted, carried back out to the district and handed round again.
  • A content update reaches devices from the same codebase, so no separate file gets prepared for each screen.
  • Somebody browsing the screen creates no record, so no personal data is collected that would have to be deleted later.

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

KGM SsangYong showroom kiosk — promotion on a screen, updates off the print route

A vehicle presentation application running on a touchscreen on the showroom floor. The part worth telling on this page is the update side: when equipment or specification detail changes, no brochure is reprinted, because the change reaches the device from the same React Native (Expo) codebase. The route a printed piece travels — design, print, distribution, collecting the old one back — has no equivalent on a screen. Anyone browsing it leaves no record behind either. The scope line: we built this for a car showroom and have no screen application running in food retail.

Read the case study →

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

  • Have you actually worked with a business in this district?

    We built the QR menu for Merkez Kasap and the shop really is here. That is a web page, though, not the screen application this page is about, and we do not blur the two. We keep no office and work fully remotely.

  • Our menu already opens from a QR code. What does a screen application add?

    They sit in different places. A QR menu opens on the customer's own phone; a screen application runs on the business's own device inside the shop, and nobody has to take a phone out to read it.

  • What has to happen when the content changes?

    No print run. The change reaches the device from the same codebase, so there is nothing to reprint, transport and hand out again.

  • Do we buy the screen, or do you bring one?

    The business supplies the device and we write the application. Having no office, we do not travel out for installation; the application is prepared remotely and reaches the device from the codebase.

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