Tag Info

Hot answers tagged

44

The problem with your buttons is that they are not raised above the background, so they don't seem clickable. I highly recommend the Material Design for details on how to choose between flat buttons and raised buttons, with exhaustive do's and don'ts. http://www.google.com/design/spec/components/buttons.html#buttons-flat-raised-buttons


13

The problem is it's not flat enough Are they icons or buttons? This is a common problem with flat design (see other answers) but one possible solution I haven't seen here yet is to remove information until the only viable option is to click. Think tiles. ...And at this point it should also become obvious that </> never was a suitable icon.


8

How about using a visual cue that users are most likely used to: an underline? Below is an example with solid underline and a dashed one.


7

On a mobile device, the current design trend uses this. Users have become familiar with the touch method to drill down for further information without having to be explicitly told to do so. Also, a "pointer" on a mobile device is redundant since there is never any other input device other than your fingers. Keep the simplicity and elegance of your ...


7

i thought of something like showing the first skill and let the user figure it out himself, that the others are clickable / tapable aswell (sorry I din't have much time on my hands to do this, but it may help) download bmml source – Wireframes created with Balsamiq Mockups


5

material design is good but they're not flat perfectly. I recommend you this, my ideal flat button p/s : if you want people consider something is a button, you need provide them "label" and "icon".With these two elements, most of users will know "ah, there's a button, let's click"


4

A few suggestions: 1. Make the Label Visually Part of the Button Labels are usually part of a button 2. Add a Light Border (optional) Highlights without necessarily adding depth 3. Group the Buttons Together Comfortably Make it feel like a group of buttons, each of equal importance 4. Use a Bolder Font Weight The icons are quite chunky, and ...


4

The first thing I'd recommend is to divide the inputs into digestible chunks. Make sure you're not presenting all of the open fields on one form. Bring the user's focus to one section at a time. For example, use gentle highlights or outlines on the first section, and disable or even hide the next sections. The second things I'd recommend is to acknowledge ...


3

First off, I prefer calling it a 'navicon', helps me to avoid hunger issues during working hours. Secondly, not all of your points are actually about the hamburger icon (3 & 4). The other ones are more about the navigation drawer in general. Anyways, let's commence.. People tend to show a lot of options with them. A lot of options isn't going to be ...


3

I don't follow the current vendor-specific security-speak, but I can try to list some UX implications related to various security measures for log in dialogs: locking accounts, even temporarily (necessary against brute force password attacks) - link to the support service must be available, email notification to the user should be generated, admins have to ...


3

I agree with both Long and DesignerAnalyst that a bit of styling makes them pop more as buttons. While I like the icons in your edited version, I would suggest adding the text below the icon, for those who may not know what the icon means. Icons are great when their meanings are obvious, but I program in JQuery and Javascript everyday, and didn't ...


2

You could also give a textual clue You could change "more information" to something more specific


2

This is a standard verification scenario, the most common example of which is domain verification. i.e. when setting up Google Analytics a user must paste a meta tag in the homepage on the site to prove they have access. The key is to require a verification or confirmation step on Site A, and to make sure it's obvious from the interaction design that the ...


2

This may not be an answer to the specific question you are asking ("Any specific site, application or book...?"), but perhaps it can help... A drag-n-drop, graphical interface for Set-Manipulation should have a strong mapping of screen-geography to some aspect of the data being represented. When viewing a selection of Sets, the arrangement of those Sets on ...


2

Well in short - and I'm sure your team has come to this conclusion already - users won't be able to run all of these in one fell swoop. The closest you could get would be to mimic Excel-like functionality whereby users can add cell-level functions to manipulate the values. My gut reaction/solution: Grids. 3,000-5,000 records is a trivial amount. Minuscule ...


2

The requirements sound like a good fit for a spreadsheet-like application to me: the primary focus should be on the data - display as much info as possible about the records (5000 is not that many data, but you could use infinite scroll techniques) autofilter-like search on the data, saved searches and tick-box selection would provide the best way to ...


1

One should simply not use the same term for items that are not the same. Users will not understand why they get different functionality between the two instances of the term. Filtering functionality is not uncommon in apps, so many users will understand the term. For those who don't, are tooltips possible for the control, or explanatory text in the UI?


1

Definitely sample 2 — it's much more economical in terms of real estate (doesn't waste space like sample 1). I don't see much clutter provided by the sample 2 but if you are worried about non-matching amount of rows, I'd merge Street and House number to eliminate one row in the right table. Many vendors do it, allowing one common entry form for both of ...


1

Wizards are very good ui patterns for :- 1) collecting info from user in a sequential (as well as non sequential manner) like a hotel/flight booking 2) Grouping of related input in each step like:- Product customization Name, shipping address in one step, Payment details in next step Summary and confirmation in final step. 3) It provides user ...


1

"Any specific site, application or book where I can find more about such an approach?" None I know of. Your best bet may be some Ph.D/M.Sc visualisation research thesis. To get the UX design right need to understand the Users Domain and create a model of this in the system that they can interact with. What not many people realise is that SQL is a textual ...


1

Even though you will save space by combining both fields onto a single page, I would be inclined to present each field on it's own screen. The user elects to pay The user is prompted for password - the user enters password The user is prompted for OTP This way each page could have it's own intro text and help links if required. Otherwise you would need ...


1

When they enter all their details and click on pay, show them the password field as well as the OTP field. At the same time you should send the OTP to their mobile. When they click confirm or submit, they should be able to do the transaction. You are reducing the number of clicks. You are doing all operations on a single page. No complexity for the user ...


1

Companies such as Apple and Facebook can somewhat get away with being trendsetters and dictating behaviour to their users. This is because they have such market penetration and users will spend more time using them than others. ie, if you propose a different 'Like' button behaviour on your low-traffic website than Facebook or Google+ do, then you are likely ...


1

for a first-time user, who never worked with any computer, its really confusing I don't think that's Apple's target demographic. For that matter, I don't think that, in 2014, that's any OS manufacturers target demographic. So, if accommodating that demographic results in a cluttered UI for others, it's understandable why they may omit it. As for ...



Only top voted, non community-wiki answers of a minimum length are eligible