Specific usability barriers emerge: chatbots, apps, ordering gates
4 Today 7:58 AM · 15h ago · 10 comments · 1 source · development 4 of 5
Comments detail intrusive design elements: persistent chatbots blocking interaction, requirements to download apps or start orders just to view menus, and paywalls around basic information.
“Don't tell me where all the ingredients come from if you're not going to let me find out what food they'll be in!”
alicefraser.bsky.socialMark Watson Comedian
The whole story postscomments the bright band is this development · numbered dots are the others · click one to jump
What people said 10 voices · verbatim
-
Don’t tell me where all the ingredients come from if you’re not going to let me find out what food they’ll be in!
-
No I don’t want to download the table booking app. You’re a kebab shop!
-
"30-year breakdown" is a good description of my adult life.
-
also, the owner of any restaurant who prints their actual menu (on paper or card) in small font in sepia tones and then has low 'mood' lighting meaning that it defeats my reading glasses and I have to take a photo of the menu and enlarge it and everyone takes the piss - jail's too good for them.
-
The prices are also bloody useful. Surely the primary role of a restaurant is to sell meals? Some seem to have forgotten that.
-
I don't mind it, as long as they stop serving food on roofing slates and don't write the food descriptions in such a way you need a cryptic crossword fan to work out it's actually beans on toast !!!!
-
Address, hours of operation, phone number, menu. Anything else is fluff
-
Good gawd, yes! You should easily, on the first page, find a link to the menu, WITH PRICES, the address, the hours of operation & any silly dress code rules they may have
-
And who wants to get there, look at the menu & have to walk out? Why do that to people?
-
And put opening hours and address where they can be seen right away.
All 5 developments of Mark Watson on restaurant websites: prioritize the menu →
Bluesky