Where in the USA is this?
191–200 of 240 posts
Re: Where in the USA is this?
#192Earlier quoted context omitted.
OTOH I understood the instructions immediately. This is a fundamental issue in UX. Some users will know right away and others will not. Maybe a better sentence structure? Maybe something like "Guess the 1 location where all these photos were taken" (?) From my experience, most people don't read the instructions or text notes anyway. So its possible that an even better UX is one where the user figures out what they ca…
> From my experience, most people don't read the instructions or text notes anyway. This fascinated me ~90s computer gaming. There were clear camps of "people who always read the manual" and "people who never never read the manual."
Re: Where in the USA is this?
#19317 miles. I don't even live in the US.
Re: Where in the USA is this?
#194Earlier quoted context omitted.
OTOH I understood the instructions immediately. This is a fundamental issue in UX. Some users will know right away and others will not. Maybe a better sentence structure? Maybe something like "Guess the 1 location where all these photos were taken" (?) From my experience, most people don't read the instructions or text notes anyway. So its possible that an even better UX is one where the user figures out what they ca…
I think some crowd that come to this come from geoguesser which will have 5 locations in a row.
Unfortunately, that sucks even more from a UX design perspective, since it means even if you absolutely nail the instructions you need to know all of the surrounding context and find a way to address it.
Re: Where in the USA is this?
#195I got 0 mi! [1] After the first 2 I stopped attempting cities and figured the picture didn't matter, it was a game of triangulation. Nice game, I like it, even though I've never set foot in the US. [1] Spoilers! - https://i.imgur.com/azCWc3i.png
Re: Where in the USA is this?
#196I don't understand what I'm supposed to do. On my phone, almost nothing responds to taps. It's like the interface is broken.
Re: Where in the USA is this?
#197Earlier quoted context omitted.
for some, reading the manual was also fun. For most, reading the manual was an admission of failure.
Manuals in the 90s were sometimes actually fun . I still occasionally reminisce about that time in primary school, when one of the classmates bought (well, his parents did, I suppose) an original, boxed copy of StarCraft. He used to briefly lend the CD, and at some point copies of the CD started circulating, and he would just share the CD key with a few people - but in between, he lent me the manual . I think I was t…
Pretty interesting idea that eschewed technological tricks to prevent copying.
Re: Where in the USA is this?
#198This is a late comment. I don't understand what I'm supposed to do. On my phone, almost nothing responds to taps. It's like the interface is broken.
You have to make a guess after each photo. This will display the next one. You have to tap the large button at the bottom "show map to guess".
Re: Where in the USA is this?
#199Earlier quoted context omitted.
i think it's auto-generating a problem based on geotagged pictures. the indoor one isn't supposed to be a good clue, it's just a photo that happened to be in the dataset.
Could maybe pass the pictures through an object detector. Too many faces and it skips the picture. It may already be doing it to remove pictures with words as one "clue" containing a sign would spoil it. Though I'd rather it keep the picture but blur the sign in that case.
Re: Where in the USA is this?
#200Earlier quoted context omitted.
OTOH I understood the instructions immediately. This is a fundamental issue in UX. Some users will know right away and others will not. Maybe a better sentence structure? Maybe something like "Guess the 1 location where all these photos were taken" (?) From my experience, most people don't read the instructions or text notes anyway. So its possible that an even better UX is one where the user figures out what they ca…
>From my experience, most people don't read the instructions or text notes anyway. This happens in my life constantly when dealing with family IT problems or mentoring juniors at work (and sometimes working with seniors too!). People just do not read the output of their computers.
If you can constantly guarantee that everything work the same all the time, then there are fewer issues. However, it does not, and because computers are prone to both bugs and marketing gimmicks, it is easy to burn out on a mental model of things.
People who do read the output of their computers experiencing situations where the computer doesn't do what it says it does, can quickly burn out. Not to mention, reading only what the computer says is a good way to diagnose the wrong thing. You observe something similar when a feature or bug is exposed and the first response is "well it used to work before" - which is often (partially) true, but that does nothing to explain why it doesn't work or did work.
Then there is social and linguistic familiarty (often iconographic). It's telling that the way the IQ test is most flawed is that it scores those with more cultural familiarity higher - things that seem "easy" may only be so because of a certain familiarity, with where things are commonly placed, common functionality, etc.
And again, as UX designers destroy these foundations in the hopes of making their UIs "easier", it only makes things more difficult, not less, to understand.