New answers tagged terminology
I am trying to come up with some common terms and definitions that are suitable to use for specification or design documents I don’t think i can come-up with a better suggestion than the one you mentioned "formatted' numeric input field" Its the best possible outcome and I don't think you should worry too much because its long, though you can make ...
The term used for these format-constrained inputs is masked inputs or mask input. Here is a demo which includes a broad range of masks (date, time, phone number, etc). If you Google 'masked input' you will find plenty more examples. http://igorescobar.github.io/jQuery-Mask-Plugin/ And a screenshot for posterity in case the link dies in the future. It ...
If I understand what you are asking why not just use what is called in HTML - type Why not just go by the actual input type name and call them types The tech name as in <input type="text" The type values/names are pretty clear even to non-developers HTML5 added several new input types: color date datetime datetime-local email month number range ...
A sitemap hierarchy can involve many levels. It won't be unimaginable to find a sitemap made of 6 levels (although not all are navigation levels). A high-level sitemap usually involves the first level, and possibly the second one as well. Being top level, these are somewhat the more critical levels - as it is imperative they are mapped to user needs and ...
These are units or formats you are talking about. For example a date is a numeric format that consists of three units: years months and days. It will depend on the context which term to use actually. Since the question got edited it is now clear that it is about inputs that guide users to a valid format. In that case guided/guiding inputs could be an ...
From my understanding (and this does seem to be a subjective issue) UCD is all about designing purely for the users' needs so that they can achieve what ever it is that they want/need to. Whereas UXD is all about crafting the join between user and business. If an online bookshop used purely UCD techniques, you would go there, easily find the book that you ...
I found an article today on A List Apart where the author describes it in this way: The terms “user experience design” (UX) and “user-centered design” (UCD) are often used interchangeably. But there’s an important distinction. UX design is the discipline: what we do. User-centered design is a process: how we do it. Source: ...
It's a List builder Resources: Designing Interfaces by Jenifer Tidwell, page 383 https://msdn.microsoft.com/en-us/library/windows/desktop/dn742407(v=vs.85).aspx#usage https://mockupstogo.mybalsamiq.com/projects/controls/List+Builders http://en.wikipedia.org/wiki/List_builder
Adding a hyperlink divert the user from your app. Better embed the google map on your app instead of adding hyperlink. Or If you only want to add a hyperlink, then add a text saying Locate our property on Google Map and upon clicking that link it should open PopUp to show your google map.
Another term used for this is slush bucket.
We refer to it as a Swap List, specifically because there are occasional use cases where there are more than two total lists (as mentioned in the above comments). A good example of this is setting security levels for fields. Fields can be hidden, read-only, or editable.
Seems to be known as Dual Listbox or Dual Multiselect http://www.virtuosoft.eu/code/bootstrap-duallistbox/ http://www.laurent-laville.org/index.php/pear/qfams/example?id=m1
To my mind, "preferences" are a subset of settings which make some actions more convenient and others less convenient, but do not make any actions impossible. Consider two programs' font-size behavior: A "font-size" dialog sets the default font size which is used to show newly-opened documents, but enlarge/shrink buttons will change the font size for the ...
A term that comes to mind is panel or pane, but looking at your "web application” it looks more like a website to me. The fact that it loads pages dynamically and slides them in doesn’t mean people will see it as an application, that depends more on it’s contents. So I think the term page will be generally understood in this case.
I would word it as "Choose section", which indicates a grouping of a given content type which is likely to include "pages" in the content. There is no hard and fast rule on this, so I would strongly suggest doing some basic UX testing with your potential customers to see which is more intuitive to them.
Just use Photos (ref screenshot from Dropbox app for iOS)
The idea of having two ‘baskets’, one for paid products and another for free items, seems too complicated to me. You’d be asking the user to maintain two separate groups of products and making the transaction harder. A customer wouldn't be expected to carry two baskets around a shop in the ‘real world’. Instead, I'd present the free items and the paid items ...
Before a selection is made: All items should have a clear price label, when the item is free of charge then in lieu of price tag, explicitly mention that the item in question is free along side a £0.00 price tag*. *During the selection process clearly indicate the number of elements that have been added to the basket to provide adequate feedback. After ...
There are a number of things I would say about this. Firstly, I don't think you need to worry about the linguistics - whether you call it a basket, trolley, cart, handbag, trug, low-loader... the issue is always about what is 'not seen' by the user. For them, putting a free item into some sort of collection makes no sense ("If it's free, why can't I just ...
Top 50 recent answers are included