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

Mobile App for Esenyurt businesses

Along the Kıraç and Yenikent stretch of Esenyurt, private course rooms do not grade the same way. One institution reports letters, another points, a third a list of outcomes, and a parent reads the result on a phone. The interface is not the hard part. The hard part is where the rule lives: bake an assessment type into code and every new exam format becomes a developer task. On Vipkurum the institution writes that rule itself, and the app renders what it finds.

Get a quote Tell us about your project

Mobile App — Esenyurt

Private training institutions and small multi-site businesses sit together along the Kıraç stretch of Esenyurt. Where one brand teaches at more than one address, the marking criterion can differ by address. What reaches the parent, though, is a single application. Vipkurum is the work of ours that sits nearest that shape. Where it does not overlap is worth stating: Vipkurum was written for schools and training institutions, so a multi-branch retailer's till or a small manufacturer's bench is not something we can show. What does carry is the shape of the record. Lessons, tests, questions and exams are records the institution defines. Underneath sit a Laravel core, MySQL and MongoDB for records and Redis for cache; the panel is React and the mobile side React Native (Expo), both on that same core.

  • Adding a new exam format is a definition job rather than a code job: the institution writes its own assessment criterion and the app reads that definition back onto the screen.
  • Lessons, tests, questions and exams live in one record set, and a teacher, a parent and an administrator each reach that record only as far as their role allows.
  • The mobile side comes out of one React Native (Expo) codebase and attaches to the same Laravel core the panel uses, so nothing separate is stood up to serve the phone.

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

Vipkurum — the institution defines the assessment, the app reads the definition

Seven training institutions run the same core under their own brands. Each builds its own lessons, tests, questions and exams, and because it defines the assessment type itself, European and Turkish criteria sit side by side on one platform. Adding a criterion waits on no code change. Panel screens are React, the mobile side is React Native (Expo), and both attach to the same Laravel core; MySQL and MongoDB hold records while Redis carries the cache. The scope is stated plainly: Vipkurum covers timetables, exams, students, parents, payments and reporting. Retail selling and workshop production sit outside it.

Read the case study →

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

  • Our exam format is not standard. Can the app show it?

    In Vipkurum the institution defines the assessment type itself. The criterion is written in the panel and the app reads that definition onto the screen, so a new exam format opens no work on the code side. That is why European and Turkish criteria sit on one platform.

  • Do parents, teachers and administrators use the same application?

    They reach the same record, not with the same rights. Timetable, exam, student and payment records sit in one data model, and each role opens the part of that record it is allowed to open. No second list is kept on the side.

  • Does covering iOS and Android mean two teams?

    No. The mobile side comes out of one React Native (Expo) codebase and attaches to the Laravel core the panel already uses. Nothing separate is stood up to feed the phone.

  • Seven institutions share one system. We are one. What does that give us?

    Not a count of installs, but where the rule sits. If an institution defines its own lessons, tests and exams, a new criterion stops being a code job even with one institution. Running several is a side effect of that, not the point of it.

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