Get a quote

Web Software · Umraniye

Web Software for Umraniye businesses

A booking does not fit one mould. In one workshop an appointment lasts minutes at a bench and two can run back to back; in the next, taking measurements eats half a day and nothing else can be scheduled. Off-the-shelf booking plugins fix the duration and the calendar it lands on before anyone asks, so one of those two always sits wrong. That is where to look when you look for web development in Umraniye, because along the Dudullu stretch the constraint can be a bench rather than a person. AlgoRandevu starts from exactly that gap, and we are still building it.

Web Software — Umraniye

Umraniye's texture is the Dudullu industrial estate, where mechanical contracting, air conditioning service and small manufacturing sit together. Work of that kind can have a booking held by a resource rather than a person: the second job waits for the bench to clear, and measurements wait for the lifting gear. The closest we stand to that condition is our own product, AlgoRandevu, and we will not hide where it stops: it is still in development, there is no live installation to point at, and it was not written for mechanical contracting. What we can show is the ground under it — the same Laravel and Inertia setup that carries the AlgoKlima and AlgoCar panels, records in MySQL, cache in Redis, interface in Tailwind. We keep no office and send nobody to Dudullu.

  • How long a booking runs and how closely two can follow each other are product settings, so changing the rule changes a setting rather than the code.
  • In the structure we are working on, a booking can attach to a person, a room or a piece of equipment, which lets a business point the calendar at whatever is actually scarce.
  • We are building it on the same Laravel and Inertia ground as AlgoKlima and AlgoCar; those two panels run live, while AlgoRandevu is still under construction.

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

AlgoRandevu — duration and resource defined in the product, still being built

Our own product, still being built — we describe it as work in progress, not a finished installation. Rather than baking the length of a booking, the resource it occupies and how closely bookings follow one another into a single trade, we keep all three definable inside the product, so a change in the rule is a change in a setting. A booking can attach to a person, a room or a piece of equipment, which puts the calendar in the hands of whatever is actually scarce. The ground is the Laravel and Inertia setup familiar from the AlgoKlima and AlgoCar panels, with records in MySQL, cache in Redis and the interface in Tailwind.

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

  • Can you install AlgoRandevu for us today?

    No. The product is under construction and we say so plainly. What we can show today is live work standing on the same ground: the AlgoKlima and AlgoCar panels. We will not call a booking product ready before it is.

  • Our calendar is set by a machine, not a person. Does that fit the model?

    That is precisely why the model is open. A booking attaches to a person, but it can attach to a room or a piece of equipment just as well. The business picks the resource, so if the bench is the constraint, the day is set by when the bench frees up.

  • Why is an off-the-shelf booking plugin not enough?

    It falls short on where the duration and the resource are defined. Plugins fix both up front, and changing a duration then turns into developer work. Once the setting lives inside the product, the same change happens on a screen.

  • Do you have anyone in Dudullu?

    No. There is no office and no team that goes out to a site. We do not derive booking rules by watching a floor; we write down together which resource holds which job and for how long.

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