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

Mobile App for Izmir businesses

Where a manufacturer in the Aegean also services what it sells, the after-sales record grows as the export target grows. The trouble is where that information is first written down. The work happens at the machine or the vehicle, but the details get typed again at a desk in the evening. On AlgoCar we cut the entry down to one point: whoever does the job opens the record once on a phone, and service, stock and accounting read that same record. Mobile app development in Izmir starts there.

Get a quote Tell us about your project

Mobile App — Izmir

Trade in Izmir sits where export-facing manufacturing and retail overlap: the same firm builds a product and then takes it back in for service. In a business shaped that way, how many times a record is typed turns straight into cost. The closest work we hold is AlgoCar, our own product, whose upkeep we carry. It was written for vehicle servicing, so export paperwork, customs and foreign-trade flow are not things we can show, and production planning stays outside too. What travels is the single entry point: a record opens once and the rest of the chain reads it. The field side is React Native (Expo); the panel runs on Laravel with Inertia and Tailwind, MySQL keeps the records and Redis carries the read load.

  • The record opens on a phone where the work is happening, so no copy gets retyped at a desk that evening and there is no second entry step at all.
  • One record feeds the service, stock and accounting sides together, so nothing is kept twice and no list waits to be reconciled at month end.
  • The scope is written down: operations, stock and accounting are inside; export documents, customs and production planning are outside.

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

AlgoCar — the record opens once and the whole chain reads that same record

Our own product: service management software whose upkeep we carry, not a build handed over. The decision the chain turns on sits at the entry point — the record opens once where the work happens, and after that the service, stock and accounting sides all read it. Nothing is kept twice, so the cost and the income of one job close in the same system. The field side comes out of one React Native (Expo) codebase; the panel runs on Laravel with Inertia and Tailwind, both on the same MySQL core with Redis carrying the read load. The limit: AlgoCar was written for vehicle service, and foreign-trade flow is not something we can show.

Read the case study →

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

  • The crew writes on paper and someone types it into the system at the office. What is wrong with that?

    There are two records. The difference between the paper and the system only shows when somebody notices it. Move the entry to where the work happens and the second typing step disappears, leaving no list to reconcile later.

  • We export what we make. Does the system cover the foreign-trade side?

    It does not. We have no work to show for export documents, customs or trade flow, and we do not promise past our evidence. The scope is operations, stock and accounting, and the service record feeds all three.

  • We build machines and handle after-sales, not vehicles. What does AlgoCar tell us?

    AlgoCar is vehicle service software and we say that plainly. What transfers is not the vehicle screens but the single entry: the record opens as the job starts. Whether the thing being serviced is a machine, a plant or a car, the place it is read from does not move.

  • Do you have people in Izmir, and do you come to the site?

    We keep no office and work fully remotely. Instead of visiting, we settle together where the record starts: which detail is entered as the job starts and which is read later. We do not draw an interface before that is decided.

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