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

Web Software · Pendik

Web Software for Pendik businesses

A technician walks down into a boiler room and the signal stays at the door. The job gets done, but the record of it waits until street level or until the office that evening, by which point it holds whatever memory kept. If your crew covers several addresses in a day, that gap repeats daily, and it is the part we describe for Pendik's multi-site service texture. On AlgoKlima the field app writes the record into a local queue on the phone first, and the queue drains in order once the connection returns.

Get a quote Tell us about your project

Web Software — Pendik

Pendik's texture puts Anatolian-side manufacturing SMEs and multi-site service organisations side by side. If you install as well as repair, a unit fitted one season becomes a breakdown call the next and the same crew moves between several addresses in a day. Where signal drops is physically predictable: a basement boiler room, an outdoor unit on a roof, the rear blocks of an estate. The work closest to this district's sector profile is AlgoKlima, our own product, kept in repair by the same people who wrote it. It was built for air conditioning, boiler and appliance service. Watching a production line or running a supply flow falls outside that, with nothing on our side to show. The office panel is built with Laravel and Inertia, the field app with React Native (Expo); both write to one MySQL core with Redis carrying the cache.

  • A record is written to the phone's own queue first, so the technician closes the form without waiting for a signal and can leave the address once the job is done.
  • When the connection returns the queue drains in the order entries were created, and edits arriving from the field and the office merge into one record through conflict resolution.
  • Warranty, maintenance and fault records hang under the unit, so three units at one address keep separate files, and a unit moved elsewhere takes its file along.

Why Algoriel

  • Brochure and requests together

    The pages that present your business and the screens that handle incoming requests sit in one application, as they do at Diotek.

  • Listings built on the server

    Product and stock listings are assembled on the server rather than in the browser, as they are on Plastik ve Makina.

  • A second way in

    A calculator, a filter or a listing page has an address of its own, so people arrive there straight from search.

  • Every page has an address

    On Günlük Hava Durumu every date and location keeps a permanent address of its own.

What we build

Web Software

  • A web application of your own

    The parts working behind the site are built around your own way of operating: incoming requests, approvals, lists, the admin panel. At Diotek a pre-sale site survey and a post-installation service call were built as two separate flows.

  • Pages rendered on the server

    Lists and pages are assembled on the server and arrive ready to display, so nobody watches an empty screen fill itself in. Plastik ve Makina refreshes its results in place when a filter changes, rather than reloading the page.

  • Performance and findability

    Every page carries a permanent address, and headings and content come out in a form a search engine can read. Günlük Hava Durumu publishes each date and location breakdown at its own address.

  • Validation on the server

    Form validation is never left to the browser; it happens again on the server. A request that arrives outside working hours still lands in writing instead of in a phone note.

  • Catalogue and filters

    A product, listing or content catalogue follows the distinctions your own trade makes, and the filters answer questions buyers actually ask. On Plastik ve Makina new and second-hand machines share one list, with condition as a filter.

  • Life after launch

    The team that writes the application also keeps maintaining it. Adding a section, or absorbing a busier season, does not mean standing up a second system.

Work like this

Web Software · Case study

AlgoKlima — records opened out of coverage, queued until the link returns

Our own product, maintained by the people who built it. A technician opens and closes a record while out of coverage: it goes into the phone's local queue first, and the app carries on without waiting for a connection. When the link comes back the queue drains in creation order, and an edit made in the field merges with one made in the office into a single record through conflict resolution. Warranty, maintenance and fault history hang under the unit itself, so files at one address never blur together. Laravel and Inertia run the office panel, React Native (Expo) the field app, both on one MySQL core with Redis holding the cache.

Read the case study →

Working with Pendik 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 technician gets no signal in a boiler room. Does the record still wait until the evening?

    No, it is opened there. The phone writes into its own local queue, the app stops hunting for a connection, and the form closes when the job does. The queue starts draining the moment signal comes back.

  • If a technician and the office both change the same call, which one survives?

    Neither is dropped. Because the queue drains in creation order, edits are applied in the order they were made, and fields that clash are settled by conflict resolution into one record — not two competing copies.

  • We run service from more than one location. Does each one need its own program?

    In AlgoKlima the office and the field work on the same customer and unit records. The record belongs to the unit, so which crew attends does not move where it lives, and no second copy is kept.

  • We also manufacture. Do you cover production tracking?

    We do not. What AlgoKlima describes is field service: the call, the unit, the warranty and the maintenance record. Production lines and supply flows are not something we have work to show for, so we make no claim there.

Web Software in other cities

The other cities where we publish this service are below, grouped by province.

Other services for this location

Let's work out what your site needs behind it.

Get a quote or open the service