Why We Obsess Over Loading Speed on Tablets

Nobody Praises a Fast-Appearing Menu

No customer has ever said "wow, that app loaded fast." But they absolutely notice when it does not. At 6:50 a.m., when the first customer of the day stands at the counter waiting for their first coffee, the app is loading for the first time since yesterday. Every second that screen takes to appear is a second of a paying customer standing in silence. We treat those seconds as the most expensive thing we ship.

Cheap Tablets Are the Real World

CrescendPOS is built for cafes and restaurants in Indonesia, and the tablet on the counter is rarely a flagship model. It is more often a device bought for a few million rupiah — a chipset that was mid-range four years ago, 2GB of RAM, and a screen that has seen a thousand fingers and a few drops of syrup. That is the real world of F&B here, and it is the hardware we design for.

This changes our priorities completely. We do not care how fast the app feels on a brand-new flagship tablet, because our users are not running it on one. If a feature works smoothly on the weakest device we support, it will feel effortless on everything else. Testing on slow hardware is not a chore; it is the only test that matters.

The Quiet Enemy: Payload Size

Most people think app speed is about code. In practice, on a cheap tablet, it is mostly about payload — how much data the device has to receive and process. Menu images are the heaviest part of that. A menu with a hundred items, each carrying a large photo, is megabytes of data that the tablet must fetch and decode every time something changes.

We do a few unglamorous things about this. Images are compressed and sized for a screen, not for print. They are loaded only when they are needed, so the tablet is never decoding a hundred photos just to show the first page of the menu. And the app remembers what it has already downloaded, so when the kitchen changes one item's photo, only that item is refreshed — not the whole menu.

Warm Starts: The Morning Routine

The most important loading moment is the first one of the day. The tablet was switched off overnight, or the app was killed to save battery. The first order of the morning has to come through a cold start — and a cold start that is fast is different from one that is merely possible.

We design the startup path the way a shift actually begins. The app renders the essential first screen — the grid, the categories, the cashier's name — before anything optional is loaded. Sales history, old reports, unused modules: they can wait a beat. The cashier cannot. On a tablet that has been sitting in a drawer since closing time yesterday, this is the difference between opening in about two seconds and opening in eight.

Offline: Speed Is Also About Not Waiting for the Internet

There is a second kind of slowness that has nothing to do with loading screens: waiting for the network. Indonesian venues run on local wifi, and local wifi is not always kind. Routers sit in kitchens, signals fade behind refrigerators, and connections stutter during peak hours. If the POS freezes whenever the network blips, the counter does not freeze with it — the queue does.

So the app treats the network as unreliable by default. Orders are recorded on the tablet first and synced when they can be. If the wifi drops mid-rush, orders keep coming in, and when the connection returns, everything catches up in the background. To a customer, the cafe never appeared to slow down.

The Math of a Few Seconds

Let us make it concrete. Say the counter serves 300 customers on a busy day. If every one of them waits three extra seconds because of slow loading, that is fifteen minutes of cumulative waiting — spread across the day as individual moments of impatience, one by one. And it compounds: a slow morning start while the app boots, a slow image refresh mid-rush, a freeze when the wifi blips. None of these is dramatic alone. Together, they decide how many customers leave impressed instead of annoyed.

We also know that speed is a revenue feature in a direct sense: the faster the counter turns, the more orders fit in the rush window. A customer who is served and paid in four minutes instead of five frees a minute of capacity for the next one.

We Treat Every Second as Revenue

Obsessing over loading speed sounds like a technical hobby. For us it is a business decision. The counter is where your revenue physically happens, and cheap tablets are the hardware your business actually runs on. Every second we save there is a second your cashier spends taking an order instead of staring at a screen. We will keep making that trade — a little less flourish, a lot more speed — because in F&B, speed is not a performance metric. It is service.