this post was submitted on 18 Jul 2025
986 points (98.5% liked)
People Twitter
7707 readers
1741 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
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.
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
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.