Laayo's tech stack, part five: seeing what happens
The dashboards, metrics and crash reports we use to know how Laayo is doing right now, and what is planned next for the backend.
Engineering
How we build the systems that move food, riders and payments across town.
Search that understands "chicken momo" and "chiken momo"
People type the way they talk. We rebuilt Laayo search so briyani, chaumin and panir find the dishes you meant, without letting the noise in.
Laayo's tech stack, part four: going native
Why we rebuilt the customer app in Swift and Kotlin, how we moved screen by screen without logging anyone out, and why the rider and partner apps stay on Flutter for now.
Making the Laayo app open fast, even the very first time
We timed a brand new install from tap to home screen and found a chain of small waits. Here is how we cut them, from GPS and duplicate calls to images and one bundled home request.
Open, closed, or somewhere in between
"Is this restaurant open?" sounds like a yes or no question. In a delivery app it has at least five answers. These are the rules we use so every screen gives the same, honest one.
Laayo's tech stack, part three: realtime
Order status, chat, rider positions and store open or close now reach phones in a fraction of a second. Here is the Go hub behind it and the fallbacks that keep it honest.
Support calls that reach a human, faster
We run our own phone line for customers, riders and partners. When we timed it, too many callers hung up before any phone rang. Here is how we cut the dead air.
Laayo's tech stack, part two: Go on the hot path
How we moved the busiest API calls from Laravel to Go one endpoint at a time, by running Go in the shadow first and comparing every answer before letting it serve.
Order alerts riders cannot miss
An order that nobody sees is an order that gets cancelled. How we traced every way a new order alert could go silent, and the receipts that now tell us when one did.
Laayo's tech stack, part one: the foundation
The servers, edge, databases and deploy habits that every order on Laayo runs through, and why we chose a boring, well-understood base before anything clever.
Rider GPS that never gets stuck
A rider's dot on the map is a promise to the customer, the restaurant and our dispatch team. Here is how we found the ways it silently froze, and what we built so it heals itself.
How we estimate when your food will arrive
A delivery time is a promise. Here is how Laayo turns kitchen history, rider GPS and road distance into an honest ETA that updates while your order is on its way.
A support assistant that knows when to hand over
Our AI assistant answers most support chats in seconds. The hard part was teaching it never to promise help that is not coming, and to bring in a person at the right moment.