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

Mobile App for Sisli businesses

A product record in a brand's app never holds still. One season adds a field, the next adds another. When every addition means rebuilding the schema and shipping a store release, the delay is not in the code but in the shape of the record. Where a campaign calendar in Sisli turns over quickly, that threshold comes back every season. We are building Secretum right now, and the character record is set up against exactly that: the document widens instead of being rebuilt.

Get a quote Tell us about your project

Mobile App — Sisli

Central trade and cosmetics retail overlap in Sisli. Where what a product carries on it changes with every campaign, the shape of the record is tested at that same pace. Where an app's record shape is rigid, that change becomes a migration first and a store release second. The work closest to this tempo is Secretum — our own product, and we will not describe it as finished: it is under construction and we show no running installation. The mismatch is plain too. Secretum is a platform where AI characters live in a feed, so for cosmetics retail, a shop catalogue or a loyalty scheme we have nothing to show. We keep the character as a document in MongoDB, write the phone client in React Native (Expo), and a Laravel core receives the records.

  • When a character picks up a new attribute the document opens one more field for it, so we neither rebuild the schema nor write a migration for records already stored.
  • Because the record shape gives, an addition on the product side is not tied to a store release: the phone client keeps reading the same document.
  • We write down what the flexibility costs: a free-form document enforces no required field, so that decision is made in the application layer instead.

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 character document gives, no schema rebuild per new field

Our own product, under construction; we show no running installation. Somebody builds their own AI character, which picks up attributes over time. So we keep the record as a document in MongoDB: when a character gains one more field the document widens, and records already stored are not moved into a new structure. The gain is rhythm: an addition on the product side does not become a rebuild of the record's shape. The cost is stated too: a free-form document enforces nothing, so required fields are decided in the application layer. The phone client is written in React Native (Expo) and a Laravel core receives the records.

Read the case study →

Working with Sisli 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 install and use Secretum today?

    No. The product is in development and we say so in the same words everywhere. What we can show is not a finished installation but the decision we took about the shape of the record, and what that decision makes cheaper.

  • Will a flexible document structure not turn messy later?

    It can, which is why the limit is stated at the start: the document requires no field of its own. Which fields must be present is decided in the application layer, so the give sits in the record and the checking sits in the code.

  • We are in cosmetics and brand retail. Where does this leave us?

    It speaks about the shape of the record rather than the sector. Secretum is not being written for a brand shop or a loyalty scheme, and there we have nothing to show. What carries across is this: where the information a product carries keeps changing, a record built to widen keeps each campaign from becoming a migration.

  • Does every content change force a new store release?

    Not for a change that touches what the record holds; the client keeps reading the same document. A release is needed when the interface itself changes, and we keep those two apart.

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