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

Mobile App for Ankara businesses

On a phone, work that takes a while cannot be tied to an open screen. The user switches away, the operating system reclaims the process, the signal drops in a tower lift — and the job cannot drop with the screen. Secretum, which we are building now, keeps text and images on two separate production paths for that reason: text is produced inside the request, image work goes to a queue. Mobile app development in Ankara starts from that threshold for us.

Get a quote Tell us about your project

Mobile App — Ankara

Ankara's weight sits in head offices and institutions with many units: the floor where decisions get made handles a management layer, not a production one, and what moves around is a report or an approval. When what someone starts on a screen does not finish in a second, the app has to carry that gap. The sectors do not line up: Secretum is our own product, still under construction, where someone builds an AI character that posts into a feed. We have no internal approval flow to show. What carries over is separating slow work from the interface. The client is React Native (Expo) on a Laravel back end; Anthropic API produces text, Flux API and Replicate the image, Redis holds the queue, the file lands in S3.

  • Image work started from the app does not wait inside the request: the job enters a Redis queue, the file is written to S3, and the app reads back whatever is ready.
  • Because text and image arrive by different routes, the interface holds two waiting behaviours — text appears in the feed straight away, an image holds its place and fills in later.
  • A generated image is not remade every time the feed opens; it is produced once and stored, and later reads pick up the same file.

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 — text inside the request, image in the queue: a product we are building

Our own product, and one we are still building — we do not present it as finished. Someone creates an AI character that posts into a feed. The decision the build turns on is splitting the production routes: Anthropic API writes the text inside the request, while Flux API and Replicate make the image and that job is handed to a Redis queue. The file is written to S3 rather than remade every time the feed opens. The aim is to move a person along the feed while an image is still being produced. The client is React Native (Expo) on a Laravel core. The limit: Secretum is a consumer product, not a corporate reporting flow we can show.

Read the case study →

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

  • If the app is backgrounded or closed, does production stop?

    It does not. The job never depended on the app staying open — it leaves the screen the moment it enters the queue. Whether a result is waiting when someone returns is a matter of timing, not of whether the work ran.

  • Why not put text and images through the same route?

    They do not take the same time. Text finishes inside the request; an image takes longer than a phone request should ever wait. Putting both on one route drags the short one down to the speed of the long one.

  • Does Secretum resemble what our institution does?

    It does not, and we will not pretend otherwise. Secretum is a consumer product we are still building. The only thing it shares with head-office work in Ankara is that slow work has to leave the screen.

  • Do you keep an office in Ankara or send people on site?

    Neither — we work fully remotely, and the number of units an institution runs does not change that. What we settle in the first session is which job finishes inside a request and which one goes to the queue.

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