-
-
Notifications
You must be signed in to change notification settings - Fork 367
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add alias to can't say about nonexisting objects [PR adding strings, not mergeable before v22] #1923
Conversation
It turns out that many users were especially confused about questions referring to nonexisting objects and were unaware that the proper solution is to create a note (though many of them figured this out) this change will guide them toward note feature as applicable in case of nonexisting objects main negative is increased complexity and more work for translators but as this confusion is quite widespread (mentioned both in talks with more experienced mappers and revealed in testing with newbies) it seems to be a worth doing fixes streetcomplete#1673 fixes streetcomplete#1097 using a different method
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A bit of a comment on the grammar/wording.
Co-authored-by: Peter Newman <peternewman@users.noreply.github.com>
Co-authored-by: Peter Newman <peternewman@users.noreply.github.com>
A problem I see with this is that it always adds this option, for any quest. Even quests where it is not likely at all that it is gone, for example a street, a sidewalk, a railway crossing etc etc. Furthermore, quests that have otherwise no other answers than "can't say" have the "can't say" option right at the lower left corner of the answer bubble. Adding always this option will hide the "can't say" option in the other answers menu. So, this might actually be counter-productive as your intention is to hint users towards the "can't say" button but what you actually do is to hide it in the first place. The very first thing and almost the only thing that is explained at all in the tutorial shown to every first user is that if he can't answer a quest for one reason or another, he shall answer "can't say" to leave a note. I think the placement of this information in the tutorial is a much better place than in every "other answers" menu for every quest. |
Many reports about gone features were exactly about streets, not only in areas with bad imports (TIGER) but also in locations where area was poorly mapped for some other reasons or situation on the ground changed. Railway crossing becoming gone is also normal in regions dismanling railway infrastructure. For example in Poland many spurs, especially leading to former industrial areas in city centers are getting removed.
And it will become "Other answers...". I admit that I am unsure whatever it will have negative or neutral (positive is unlikely) effect.
Yes, all this observations that resulted in implementing this predate intro and I have never tested impact of intro for users. Though I assumed that like any intro/docs/tutorial it will be skipped/ignored by large part of userbase. |
Overall, I think that this change would be improvement but I am not 100% sure and it is partially based on outdated feedback. |
Hm I would rather not have this in the app due to the reasons given in my last comment. |
It turns out that many users were especially confused about questions referring to nonexisting objects
and were unaware that the proper solution is to create a note (though many of them figured this out)
this change will guide them toward note feature as applicable in case of nonexisting objects
main negative is increased complexity and more work for translators but as this confusion
is quite widespread (mentioned both in talks with more experienced mappers and revealed
in testing with newbies) it seems to be a worth doing
fixes #1673 fixes #1097 using a different method