3 ms·
I think the two prior comments about having a robust system with 100% uptime are on the money. It definitely can't be laggy, either. I'd suggest the following
by gallerytungsten 15y ago
I think the two prior comments about having a robust system with 100% uptime are on the money. It definitely can't be laggy, either.
I'd suggest the following reality check. Set up a "head to head" test vs. a cash register. Give someone basic training, and have them run through a list of transactions. Is your app as snappy and responsive as the hardware of the cash register? How does it compare to the cost of a cash register? I'd suggest doing this competitive analysis of the cost and performance before going any further.
- davidjairala 15y agoThe head to head test vs. a cash register is a fantastic idea, thank you! Basically, from what I've seen thus far, cost-wise I'd like the webapp to be the affordable solution, 'cause most of these POS setups can get really pricey from the get go. Speed is pretty snappy right now, but this can vary once it's running with a couple of actual clients on, so I'll have to look into it a bit more carefully, start caching whatever's possible to, and so forth, so thank you for that suggestion as well.