OSPOS

About OSPOS

WHAT IS NEW IN THIS BUILD One feature: a kitchen screen. A spare iPad or iPhone in the kitchen shows paid orders as tickets. Plus a shop can now hold several paired devices at once, and the iPad layouts have been reworked. MOST OF THE APP NEEDS NO ACCOUNT OSPOS works as a cash register with no account, no sign-in and no network. Build a menu, ring up an order, take cash, email a receipt, see the day's sales. You can review the majority of this build without signing in at all. REVIEWING THE KITCHEN SCREEN — PLEASE READ, IT IS OFF BY DEFAULT Kitchen tickets do nothing until they are switched on, and switching them on is one toggle: Settings > Send tickets to the kitchen With it off, the app behaves exactly as the previous version. With it on, any order you pay for appears as a ticket. A kitchen screen is a second device, so seeing tickets arrive needs two. With one device you can still switch the setting on, ring up and pay for an order, and confirm the app is unchanged otherwise. HOW TO LEAVE THE KITCHEN SCREEN — IMPORTANT A device set to Kitchen screen (or to Reader) replaces the whole app with one full-screen surface and no tab bar. That is deliberate: it is mounted on a wall or handed to a customer, and a stray tap must not navigate away from it. To get out: PRESS AND HOLD THE TOP-LEFT CORNER of the screen for about a second. A menu appears with "Exit kitchen mode", which returns the device to the normal app. The same gesture works on the customer-facing Reader screen. This is the only way out by design, and we would rather you knew than discovered it. PAIRING TWO DEVICES Settings > Pair a device. One device is the Counter (where you ring up), the others are a Reader (customer-facing) or a Kitchen screen. Both devices show four digits; you confirm they match ON THE REGISTER FIRST, then on the other device. The second device's Confirm button stays dim until the register has confirmed — that is the intended order, not a bug. Pairing uses the local network, which is why iOS asks for Local Network permission. Nothing is sent to us; the devices talk directly to each other. Info.plist declares three Bonjour services, and a fourth thing worth saying plainly: `_ospos-sync._tcp` and `_ospos-sync._udp` are Apple's Multipeer Connectivity, which carries pairing between two Apple devices with no router needed. `_ospos-lan._tcp` is a direct connection between devices on the same Wi-Fi, added in this build so a kitchen screen need not be an Apple device. Every frame on it is encrypted end to end between the two devices; the shop's Wi-Fi carries nothing readable and nothing reaches our servers. PAYMENTS — PLEASE READ BEFORE TESTING A CARD The demo merchant is connected to a LIVE Stripe account, so: - Test card numbers will NOT work. Live Stripe rejects them. - Test mode cannot be enabled for this account. The server refuses it for any account with a connected Stripe account. - Tap to Pay on iPhone has no card-number field. It accepts only a physical contactless card or a device wallet. - The demo merchant is capped at $1.00 per transaction so an accidental real-card tap cannot move meaningful money. Cash payments have none of these constraints and exercise the full order, receipt, kitchen-ticket and sales flow. NO NEW PERMISSIONS OR DATA COLLECTION This build requests no permissions the previous version did not. Local Network was already required for the two-device register in 1.3. Kitchen tickets carry an order number, item names and modifiers — no customer data, no prices, and nothing leaves the merchant's own devices. Privacy nutrition labels are unchanged.

App privacy

The developer, TTTS Co LLC, reported these privacy practices to Apple.