Why We Designed This POS Tablet-First (Not Desktop)

The Starting Point: Why Tablet?

When we first started talking to cafe and restaurant owners in Indonesia, one complaint kept surfacing: "My counter is already full." Not because they had fancy equipment everywhere — but because the space itself was tiny. A traditional POS setup with a monitor, keyboard, mouse, and receipt printer eats up nearly half a small counter. In a warung where the entire checkout area is 80cm wide, that's a real problem.

So we asked ourselves: what if we designed the POS from scratch for a tablet? Not a shrunken-down version of desktop software, but something built natively for a 10-11 inch touchscreen.

This wasn't an obvious call. Most POS systems start as desktop applications and bolt on a mobile version later — and the result is always a compromise. Buttons too small to tap reliably. Menus nested three levels deep. Workflows that should take 2 taps end up taking 5. We wanted to go the other direction.

The Realities of Indonesian F&B That Shaped This Decision

If you've spent time in the food and beverage scene in any Indonesian city, you'll notice a few things that directly shaped our thinking:

• Space is scarce. Most F&B outlets here operate in tight quarters — a 2x3 meter booth in a food court, a street cart, a narrow shophouse. There's simply no room for a traditional desktop setup.
• Budgets are tight. A decent 10-inch Android tablet costs around Rp 2-3 million. Compare that with a desktop setup (monitor + PC + keyboard + mouse) at Rp 5-7 million minimum. That difference buys a lot of raw ingredients.
• Power isn't always reliable. Tablets have built-in batteries. When the electricity goes out for 30 minutes — which happens — the cashier keeps running. A desktop without a UPS just dies.
• Staff turnover is high. Someone who's never worked a cash register before is more comfortable with a touchscreen than with a keyboard and mouse. Training time drops significantly.

All of these factors convinced us: tablet-first isn't just a design preference — it's a market requirement.

The Touch Target Philosophy: Fingers, Not Cursors

The most fundamental difference between designing for desktop and designing for tablet is the input method. A mouse gives you pixel-level precision — you can click tiny buttons, dropdown menus, or text links without issue. A finger? Not so much.

In CrescendPOS, every tappable element has a minimum touch target of 44x44 pixels. That's not an arbitrary number — it's the established ergonomic standard for touchscreen interfaces that demonstrably reduces mis-taps. But we didn't stop there:

• Product grids use large cards. Each product appears as a generously-sized card that's easy to tap, even when hands are wet or greasy (a daily reality in kitchens).
• Custom numpad for number input. When the cashier needs to enter quantities or payment amounts, we don't use the OS's virtual keyboard — we built our own numpad that's larger and faster.
• Minimal navigation depth. Everything the cashier needs lives on one or two screens. No deeply nested menus to drill through.

The principle is simple: if a cashier has to think about where to tap next, that's a design failure.

Minimal-Tap Workflows: Every Tap Is Time

During rush hour, every second is a customer. If one transaction takes 15 taps and another takes 8, that 7-tap difference — multiplied by 200 transactions a day — adds up to hundreds of wasted taps. Sore hands, longer queues, frustrated customers.

That's why we're obsessive about reducing taps per transaction:

• Tap a product = it's in the cart. No confirmation dialog asking "add to order?" — one tap, it's in.
• Quantities are editable directly from the cart. Tap the number in the cart, numpad appears, change the quantity, done.
• Cash payments have denomination shortcuts. Customer pays Rp 50,000 for a Rp 37,000 order? Tap the "Rp 50,000" button, change is calculated automatically. No manual entry needed.
• Receipts print automatically. The moment a transaction completes, the receipt goes to the printer without any additional taps.

Every feature we add gets tested with one question: "How many taps does this take?" If the answer is more than it should be, we redesign.

The Trade-offs We Accepted

Tablet-first isn't without compromises. There are things we knowingly gave up — and we made those decisions with eyes open:

• Smaller screen = less information at once. On desktop, you could show 50 products on a single page. On a tablet, maybe 12-16. Our solution: smart categories and fast search, so the product you need is always 1-2 taps away.
• Physical keyboards are faster for long text input. For lengthy order notes, tablets are genuinely slower. But in POS operations, most input is tapping (selecting products, selecting denominations) not typing. So this trade-off is acceptable.
• Multi-window isn't practical. On desktop, you can view reports while processing an order. On a tablet, it's one screen at a time. We solved this by designing workflows that ensure the cashier never needs two things open simultaneously during a shift.

Being transparent about these trade-offs matters to us. We're not selling the illusion that a tablet can replace a desktop for every use case. But for daily F&B cashier operations? A tablet isn't a compromise — it's actually the better fit.

But It Still Works on Desktop

This is the part that often confuses people: "If it's tablet-first, does that mean it doesn't work on desktop?"

It does. CrescendPOS is a web app, so technically it opens in any browser. What we mean by "tablet-first" is about design priority — we design for the tablet first, then make sure the desktop experience is solid too. Not the other way around.

In practice, many business owners use a tablet for daily cashier operations but open a laptop to review reports or manage the menu. That's a natural workflow, and we fully support it. Admin pages and reports are optimized for larger screens too — wider tables, more detailed charts, sidebar navigation that takes advantage of horizontal space.

So it's not "tablet only" — it's "tablet first, desktop welcome."

What We Learned

After designing and iterating on CrescendPOS with a tablet-first approach, here are the most valuable lessons:

• Constraints are good. A small screen forced us to think hard about what truly matters. The result is a UI that's cleaner and more focused than if we'd started from a desktop canvas.
• Speed beats completeness. Cashiers don't need 100 features on screen. They need 5 features accessible in under a second. Tablet-first forced us to prioritize access speed above all else.
• Hardware matters. We can't control what hardware our users buy, but we can design for the hardware that's most common and most affordable. That means optimizing for mid-range tablets, not the latest flagship.

The tablet-first decision has become the foundation for every other design decision in CrescendPOS. Every new feature we build starts with the question: "How does this work on a 10-inch tablet?" And if the answer isn't satisfying, we redesign until it is.