Timeline for Address Autocomplete - Shouldn't city come before street?
Current License: CC BY-SA 4.0
15 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Feb 7, 2019 at 20:23 | comment | added | O. R. Mapper | Let us continue this discussion in chat. | |
Feb 7, 2019 at 19:33 | comment | added | John Zabroski | The title of the question literally starts with the word "Address AutoComplete", not "Address Ordering". I'm not going to respond to you further. | |
Feb 7, 2019 at 19:26 | comment | added | O. R. Mapper | @JohnZabroski: I won't, because that would be off-topic here. This question is about the specifics of entering postal addresses, in particular the ordering. If you are interested in learning about particular asynchronous UI programming problem, I suggest you open a separate question. Feel free to post a link here if you do, please, that will help following-up on the discussion; I just think this comments area should not be sidetracked to switch to all kinds of other UI issues just because they might also occur in address forms. Thank you. | |
Feb 7, 2019 at 14:55 | comment | added | John Zabroski | Can you please provide some constructive comments about how to improve auto completion? Discussing overhead of asynchronous calls is relevant to auto-completion and gives the UX designer additional things to think about before handing off work to a developer, such as what affordances to provide the user with the paradigm shift. | |
Feb 7, 2019 at 12:47 | comment | added | O. R. Mapper | @JohnZabroski: It's unrelated to address input, as it occurs the very same way in any other input scenarios where pressing tab triggers an asynchronous call whose result is used to influence the next input field. Thus, it's a general issue, nothing specific to writing addresses as opposed to other kinds of data. | |
Feb 7, 2019 at 12:36 | comment | added | John Zabroski | @O. R. Mapper - The whole reason to change the order of fields on the form is so that "one field influences something about another field". This is not a general low-level issue and calling it such doesn't make it one, either. I've provided real usability data with a detailed analysis of what issues users ran into in this UX problem domain. Perhaps you can constructively add something by providing examples of high level issues? | |
Feb 7, 2019 at 11:15 | comment | added | O. R. Mapper | @JohnZabroski: "common problems users have when you try to auto complete addresses, such as, what do you do if the user tabs fast and the city address web service does not come back in time?" - that sounds rather like a general low-level issue of input fields where the content in one field influences something about another field; it's an issue entirely unrelated to addresses or ordering of fields. | |
Feb 7, 2019 at 2:22 | history | edited | Lucas | CC BY-SA 4.0 |
Answer to John comment
|
Feb 5, 2019 at 2:00 | comment | added | John Zabroski | I recommend reading Luke Wroblewski research on this, in particular the bottom of the PDF where he discusses common problems users have when you try to auto complete addresses, such as, what do you do if the user tabs fast and the city address web service does not come back in time? | |
Feb 3, 2019 at 18:09 | history | edited | Lucas | CC BY-SA 4.0 |
deleted 250 characters in body
|
Feb 3, 2019 at 14:13 | history | edited | Lucas | CC BY-SA 4.0 |
added 4 characters in body
|
Feb 3, 2019 at 13:57 | history | edited | Lucas | CC BY-SA 4.0 |
Added an example in response to a comment.
|
Feb 3, 2019 at 12:24 | history | edited | Lucas | CC BY-SA 4.0 |
corrected spelling
|
Feb 2, 2019 at 12:51 | comment | added | Big_Chair | Wow, that's actually interesting. Do you have any example website by any chance? Here in Germany I have honestly never seen it done other than the standard. | |
Feb 2, 2019 at 10:29 | history | answered | Lucas | CC BY-SA 4.0 |