We run an accounting program that works. Does it have to go?

The program is not the question; where the invoice's basis sits is. If the lines are typed into the work order and again into an invoicing screen, that second entry is the problem. The scope limit is written down too: AlgoCar carries operations, stock and the trading record, while production planning and supply flow stay outside.

When the technician closes the job on the phone, is the invoice raised by itself?

The decision to raise it stays with a person. What disappears is not the decision but the second typing: because the invoice comes off that work order, its lines never have to be entered again.

It was written for vehicle servicing. What does it say to a mechanical service firm?

It speaks about the chain rather than the screens: the work order is a container, the work done and the part consumed are written into it, and the invoice comes out of the same container. Rename the container a unit or a plant and the chain holds. The plate and chassis record is AlgoCar's own context and does not travel.

Do you have a team in Dudullu, and do you come out to install?

We keep no office and run the work entirely remotely, so nobody comes out. We do not begin with screen designs either: first we write down which information lives in which record, and the interface follows.

Mobile App · Umraniye

Mobile App for Umraniye businesses

A service job closes in the field and the invoice starts on a desk. In the workshops of Asagi Dudullu the same information gets typed a second time at the end of the day: the lines a technician closed on a phone are keyed again into an invoicing screen. Mobile app development in Umraniye, Istanbul answers that from ownership of the record rather than from interface design. In AlgoCar the invoice opens on no separate screen; it is raised off the work order itself.

Get a quote Tell us about your project

Mobile App — Umraniye

Mechanical contracting, air conditioning service and small manufacturing work out of the same streets in Umraniye. Where a job happens on the customer's premises and the invoice is raised back at the workshop, the second typing appears there. The work closest to this district's profile is AlgoCar, our own product, code and upkeep with us. It was written for vehicle servicing: a mechanical contracting agreement, production planning or a supply chain fall outside it and we have nothing to show there. What carries across is where the invoice comes from. The core is Laravel, Inertia brings the panel screens, MySQL holds the records, Redis takes the cache, and the React Native (Expo) side writes into that same core. We keep no office and travel out to install nothing.

The invoice opens in no separate module: the record it is raised from is the work order itself, so its lines never reach an accounting screen a second time.
The moment the job is closed from the phone, what the invoice rests on is ready, and the step of returning to a desk to re-enter the same detail falls away.
The phone writes into the same core as the panel, so a job closed in the field produces no second record waiting to be confirmed on a desk screen.

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.

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 invoice is raised off the work order itself

Our own product: not a handover, but vehicle service software whose upkeep we carry. The invoice is no separate module. A work order opens, the work done and the parts consumed are written into it, and the invoice is raised off that same record, so its lines never reach an accounting screen a second time. The field side sits in a React Native (Expo) app: a technician closes the job from the phone, and what the invoice rests on is ready then. The panel runs on Laravel, Inertia brings its screens, MySQL holds records and Redis the cache. The vehicle context is plain: what travels is not the screens but where the invoice comes from.

Read the case study →

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

We run an accounting program that works. Does it have to go?

The program is not the question; where the invoice's basis sits is. If the lines are typed into the work order and again into an invoicing screen, that second entry is the problem. The scope limit is written down too: AlgoCar carries operations, stock and the trading record, while production planning and supply flow stay outside.
When the technician closes the job on the phone, is the invoice raised by itself?

The decision to raise it stays with a person. What disappears is not the decision but the second typing: because the invoice comes off that work order, its lines never have to be entered again.
It was written for vehicle servicing. What does it say to a mechanical service firm?

It speaks about the chain rather than the screens: the work order is a container, the work done and the part consumed are written into it, and the invoice comes out of the same container. Rename the container a unit or a plant and the chain holds. The plate and chassis record is AlgoCar's own context and does not travel.
Do you have a team in Dudullu, and do you come out to install?

We keep no office and run the work entirely remotely, so nobody comes out. We do not begin with screen designs either: first we write down which information lives in which record, and the interface follows.

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

Mobile App for Umraniye businesses

Mobile App — Umraniye

Why Algoriel

The field team works from the phone

A screen instead of a brochure

A state change pings the phone

One app, both stores

What we build

The platform follows the job

An interface built for the moment of use

The services behind the app

Who made the entry, and where

Working with no connection

Which device it lands on

Work like this

AlgoCar — the invoice is raised off the work order itself

Working with Umraniye teams, remotely

Frequently asked

We run an accounting program that works. Does it have to go?

When the technician closes the job on the phone, is the invoice raised by itself?

It was written for vehicle servicing. What does it say to a mechanical service firm?

Do you have a team in Dudullu, and do you come out to install?

Mobile App in other cities

Ankara

Istanbul

Izmir

Tell us where your app will be used.

Mobile App for Umraniye businesses

Mobile App — Umraniye

Why Algoriel

The field team works from the phone

A screen instead of a brochure

A state change pings the phone

One app, both stores

What we build

The platform follows the job

An interface built for the moment of use

The services behind the app

Who made the entry, and where

Working with no connection

Which device it lands on

Work like this

AlgoCar — the invoice is raised off the work order itself

Working with Umraniye teams, remotely

Frequently asked

We run an accounting program that works. Does it have to go?

When the technician closes the job on the phone, is the invoice raised by itself?

It was written for vehicle servicing. What does it say to a mechanical service firm?

Do you have a team in Dudullu, and do you come out to install?

Mobile App in other cities

Ankara →

Istanbul →

Izmir →

Tell us where your app will be used.

Ankara

Istanbul

Izmir