this post was submitted on 18 Jul 2025
1234 points (98.7% liked)
People Twitter
7708 readers
1248 users here now
People tweeting stuff. We allow tweets from anyone.
RULES:
- Mark NSFW content.
- No doxxing people.
- Must be a pic of the tweet or similar. No direct links to the tweet.
- No bullying or international politcs
- Be excellent to each other.
- Provide an archived link to the tweet (or similar) being shown if it's a major figure or a politician.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
If every self checkout was similar to others, but each of them want to make things different.
Different and worse. How do designers keep seeing other checkout system and think: "You know, I think I see a way that we could make this process slower and more complicated...."
Well for starters because their job title is designer. Gotta earn that $$$$.
If they just copy and pasted it would be "What are we paying you for"
See every single UI/UX change on a modern operating system, or website in the past 30 years.
Trust me it's not the designers choosing to do it this way. There's management above them saying "hey this other company makes them put in their phone numbers, it must be for SOMETHING, we should too"
I don't understand why the card reader and the screen are separate units, just combine them like those Square kiosk things that counter order places have.
Because at the scale these stores work at. It's cheaper to have different units you can replace, repair and upgrade at different intervals as needed.
Security is a big reason to never combine payment processing and user (the store) defined ui.
Could you clarify? Because I'm pretty sure that's not a thing.
stripe recommends it for card reader to smartphone at least, and it looks like home depot is an example of why it should be done between the card reader and the pos.
https://stripe.com/ie/resources/more/how-do-card-readers-work
https://listings.pcisecuritystandards.org/documents/accepting_mobile_payments_with_a_smartphone_or_tablet.pdf
I get the phone thing, because phones are relatively insecure devices, but they could have functionally separate systems in one box.
The main problem I'm trying to solve is the weird UX where I need to select a payment method even after paying on the payment device. If it was designed as a complete set instead of separate units, I think they'd fix that.
This is doubly true for the card payment terminals. The on screen options are all in different places, orders, and with random questions thrown in. What’s your phone number? Do you want to round up to donate a car to starving kittens? What’s your zip code? Debit or credit?
Also, because this system is apparently developed by a maniac: where I live (might be national and not state level, not sure) EBT cards have to be used on some terminals by swiping, not the chip that comes on the card. But to swipe, first you have to use the chip and let that fail. So if you see someone using an EBT card that looks like they have no fucking clue how to use a card, it’s probably that they’re actually using it the only way they can.
Absolutely insane design choice, especially for people who may already be facing delays like separating items into two separate transactions for non-covered items, having to remove items that seem like they should be covered but aren’t, etc.
why would a store need a zip code?
Sales metrics, I guess. Ikea always asks for it when you check out, and I remember having to ask people when I worked at a retail clothes store untold ages ago.
wow, I guess it has been about a decade since I was at an IKEA l