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

Mobile App for Besiktas businesses

On the head-office floors around Balmumcu and Dikilitas the same piece of information sits in two places at once: on the screen at the desk, and on the phone of whoever just walked out of the meeting. One of them changes; the other stays stale until somebody pulls to refresh. That gap opens wherever two surfaces are fed by two separate update paths. In Secretum, the product we are building right now, we do not duplicate that path.

Get a quote Tell us about your project

Mobile App — Besiktas

Head offices and multi-brand groups are dense in Besiktas: a decision gets made centrally, and the person who needs to see it may not be in the building. The evidence here is Secretum, and we state its status as it stands — our own product, under construction, not finished, with no delivery date given. Where it does not line up is plain enough. Secretum is a social platform where AI characters live in a feed, so we have nothing to show on corporate communication, brand management or agency workflow, and no agency or media client in the district. What carries across is the broadcast layer: the Reverb broadcast set up on the Laravel side is listened to by the Vue 3 web interface and the React Native (Expo) client alike.

  • Live updates leave one broadcast layer, so no second update path gets written for the mobile client.
  • Both clients listen to the same broadcast, so a change visible on one surface does not wait for a manual refresh on the other.
  • Secretum is under construction right now, so what is described here is the arrangement we are working on rather than a finished product.

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

Secretum — the product we are building: one broadcast layer, two clients

Our own product, under construction right now; we do not describe it as finished and give no delivery date. A user sets up an AI character and the character posts into a feed. The part that decides the mobile build is this: web and mobile both want live updates at the same moment, and we did not want to write two broadcast paths. The Reverb broadcast set up on the Laravel side is listened to by the Vue 3 web interface and the React Native (Expo) client alike, so when something lands in the feed both surfaces hear the same event. The scope line: this is a social platform build, not a corporate communication or brand management tool.

Read the case study →

Working with Besiktas 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 use Secretum today?

    No. We are building it and we give no date. What this page describes is not the product but the arrangement we are working on: one broadcast layer feeding a web interface and a mobile client together.

  • We already have a web interface. Does a mobile client create a second update job?

    Not if the broadcast layer stays single. A change is published once and both clients listen to the same broadcast, so there is no separate update path and no second trigger rule to keep alive for mobile.

  • Do you take on agency or media work?

    We have no agency or media client in the district and nothing to show on that side. Our work is software: where a record sits, and which path an update travels down.

  • Why show your own product instead of a client build?

    Because we carry its upkeep. On our own product we pay for our own decision — had we written a second broadcast path, we would be the ones feeding both of them.

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