Is convention wifi ever reliable enough to depend on?

Rarely, and not predictably. Even venues with paid wifi tend to degrade once the hall fills, which is exactly when a dealer needs their tools to work. Treat any available connection as a bonus for syncing later, not something your table relies on to make a sale.

What's the difference between an app that's offline-first and one that just caches data?

Caching lets you view data you already loaded, but usually still needs a connection to write anything new, like a sale or a trade. Offline-first means every core action, searching, selling, trading, buying, happens on the device with no network required, and syncs automatically once a connection is available again.

How does Show Mode handle syncing after a show?

Everything logged during Show Mode, whether that's a sale, trade, or buy, syncs automatically the next time the device has a connection. There's nothing to manually trigger or reconcile by hand.

How to Keep Selling When the Convention Wifi Dies

The wifi always dies at the worst possible moment: doors open, the room fills, and every phone in the building is fighting for the same weak signal. Your table doesn't get to stop.

Ask any full-time dealer what actually breaks a good show and "wifi" comes up before "bad pulls" or "lowballers." Convention centers pack thousands of phones into a hall built for foot traffic, not bandwidth. The venue's network buckles right as doors open, which is exactly when you need to move fast: look up a price, log a trade, ring a sale, and get to the next person in line.

If your table depends on a live connection for any of that, a bad wifi day turns into a bad sales day. The fix isn't a better hotspot or a prayer that the venue upgrades its router. It's running your table in a way that never needed the network in the first place.

Why convention wifi fails on schedule

It's not bad luck. Convention and hotel wifi is built for occasional use, not for a room full of vendors and buyers all pulling up price checks and payment apps at once. The failure pattern is predictable: the network holds fine during setup when the hall is empty, then degrades the moment doors open and stays unreliable through the busiest hours of the day. That's the exact window where you can least afford it.

Some venues throttle or charge separately for vendor-grade bandwidth, and even paid hotel wifi chokes under a packed hall. Cell signal isn't a reliable backup either. Convention centers are often built with materials that block or weaken cell service, and a room of a few thousand people all on their phones will saturate local towers the same way it saturates the venue's router.

What actually breaks when you lose signal

The real damage isn't one dropped connection, it's what that connection was holding up. Walk through what a typical sale needs if your inventory system depends on the network:

Looking up a card. If your catalog or pricing lives behind a live API call, a stalled connection means a stalled search while a buyer waits.
Logging the sale. An app that needs to sync before it confirms a sale can leave you unsure if the transaction actually recorded.
Tracking trades and buys. These happen fast and often in a crowd. If logging one requires a signal, you're stuck writing it on paper and hoping you remember to reconcile it later.
Knowing your numbers. Per-show profit only means something if every sale, buy, and fee actually made it into the ledger. A dropped sync can quietly leave gaps you won't notice until you're doing math after teardown.

None of this is a hypothetical edge case. It's the normal operating condition of a packed convention hall, several hours a day, at nearly every show.

Build your table around offline-first, not offline-hopeful

There's a real difference between a tool that tries to work offline and one that's built offline-first. "Tries" usually means it caches a little data and falls over the moment it needs to write something back. Offline-first means the network is optional, not a dependency: everything you do at the table happens on the device, and any syncing happens quietly whenever a connection shows back up.

This is the whole idea behind Show Mode in CardOps. It runs the table entirely offline: you search your inventory, sell, trade, and buy in seconds, and see your running per-show profit, all without waiting on a network call. When you do get signal again, whether that's a lull between doors or back at the hotel that night, everything syncs on its own. You never have to think about it mid-sale, and you never lose a transaction because the room's wifi buckled at 11am.

A pre-show checklist for dead-wifi days

You can't control the venue's network, but you can control how much your table depends on it. Before doors open:

Assume there's no wifi. Plan the day as if the connection won't be there, so a working one is a bonus, not a requirement.
Load your inventory before you leave. Whatever you're selling from should already be on the device, not something that loads fresh at the table.
Charge for the whole day, plus a backup. An offline-first workflow still runs on battery. A dead phone stops a table just as fast as dead wifi.
Know your sync habit, not just your tool. Even the best offline-first setup benefits from a quick check-in during a lull, just to confirm everything's caught up before you pack out.

The upside: you stop noticing the wifi at all

The dealers who stress least about convention wifi aren't the ones with the best hotspot. They're the ones whose table doesn't depend on a connection to function in the first place. Once selling, trading, and buying all run locally, a dead network stops being an event. You keep moving the line, and the syncing happens on its own time, not yours.

That's the whole point of building for the table instead of the desk: the room is loud, the line is long, and the network was never going to be there when you needed it most. Plan around that instead of hoping it improves.