Member Avatar for dongtrien

For example, you can order dishes on handheld devices that run on your Iphone, Androi, winphone, restaurant, coffee shop, and so on. Any programming language that runs on the above devices, for example simple you have to share yourself with.

  • 4 Contributors
  • 4 Replies
  • 289 Views
  • 3 Weeks Discussion Span
  • Latest Post Latest Post by GrimJack

Dani AI

Generated

For the tablet/handheld ordering workflow described by , a low-friction first step is a responsive web order page that can be installed as a Progressive Web App. That follows 's point about avoiding installs while keeping the option to add offline caching, push, and a home-screen shortcut. A native app makes sense later only if certified hardware access, robust offline-first operation, or kiosk lockdown is required.

A practical, production-ready architecture usually looks like this: a touch-optimized SPA front end (large targets, clear modifier flows, quick-cart UX) with a service worker for offline cart and background sync; an idempotent REST API layer for orders and authentication; a relational schema for Orders/OrderItems/Modifiers/AuditLog (SQL Server or equivalent); a background job queue to handle printing and payment processing so the UI never blocks; and a realtime channel (WebSockets or SSE) to push kitchen status to devices.

A minimal JSON order payload and a simple POST pattern (idempotency key) can make integration predictable:

POST /api/orders
Headers:
  Content-Type: application/json
  Idempotency-Key: 3fa85f64-5717-4562-b3fc-2c963f66afa6

Body:
{
  "clientOrderId": "abc-123",
  "location": "counter-1",
  "items": [
    {"sku":"WING10","qty":10,"mods":["extra-sauce"]}
  ],
  "total_cents": 1999,
  "notes": "no celery"
}

Operational tips and cautions: implement optimistic UI and clear network-state indicators to avoid duplicate orders; use idempotency keys on the API; never store raw card data (use a payment tokenization provider); add audit logs for reconciliation; and use device management (kiosk mode, auto-launch) for staff tablets. The clarifying questions from are common, and 's usability joke underscores the importance of large buttons, confirmation/undo flows, and hygiene-aware UI design.

Recommended Answers

All 4 Replies

Member Avatar for rproffitt

The usual is to start with a web order page. Apps require more time and may be specific to the handheld plus you have to get the owner to install them.

Make a web order page and there is no install required and should run on almost any smart device today and for many years.

Member Avatar for gentlemedia

I really have no clue what you're after.

¯_(ツ)_/¯

that run on your Iphone, Androi, winphone, restaurant, coffee shop...

¯_(ツ)_/¯

for example simple you have to share yourself with.

commented: (☞ຈل͜ຈ)☞ +15
Member Avatar for dongtrien

I find the software for ordering in the cafe, ... they use Ipad to order food. Employees bring out an Ipad to order food for customers choose the items, when selected will save to SQL Server, do you go to the coffee shop called dish like this ?

Member Avatar for GrimJack

It seems to me that would get pretty messy right off the bat. My cell could only hold a stack of about 10 wings before they started falling off; plus how do you use the phone with all that food stacked on it? and your greasy fingers from the wings?/s

commented: Obvious, really. +15
Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.