Tag Info

New answers tagged

0

The Volume up and volume down buttons should be next to each other, for the simple reason that when users adjust volume they press these buttons alternately and blindly until the desire volume is set, so you don't want any other bottom to be literally in the middle of that interaction. For me this is a must. About the mute icon, I would personally go with ...


0

On the bottom, and just a speaker. Photo of the Macbook keyboard fragment UPD: I've submitted my answer and then noticed you've edited the question and added pretty much same photo.


1

Mute button at the bottom as this is going to be used less than your standard volume controls, and should also follow a logical flow: Volume up -> Volume down -> Mute. If this is in the middle a user could accidentally press mute which would be annoying. A mute button should follow conventional design so a speaker crossed out would be fine. Check out the ...


2

Having built a few apps in a similar space many years ago, the underlying UI/app framework is unhelpful. Essentially what you have is both a "List UI" and "Item details" on the same screen. Two basic options: 1. Have two separate screens - List & Item Simplest to implement. Arguably could be less efficient. download bmml source – ...


2

Tabs usually contain different data. For example different sections of a form, like @staccato said. Now each tab is a new annex which the user add. When adding a lot of annexes it will be difficult to distinct different tabs. Instead of tabs you could have a list of annexes and a plus button below it. (For creating a new annex) You can have a list of ...


1

I would display [1][+0] for inbox only and [0][+20] for reputation only updates, to keep the title consistent with both-updates situation like [4][+30]. I would probably not include seasonal promos like the current WINTER BASH, but if you want to include it, something like [1][+0][1] should be sufficient..


0

To display the latest information would be more user friednly, since the user would be accessing his own accout. Users would be more interested what new things have occured since his/her last visit, than looking at the complete old data.(As per human nature this looks more suitable)


1

I understand that this is a data entry form for inserting and updating system entities into a database. Seems like a tool that people would need to work with on a daily basis and it's therefore imperative that the UI they use doesn't cause too much cognitive load, which results in unhappy users. The form you're presenting is over 20 fields long. I first ...


0

There is not very much you could do without changing the architecture of the menu. You could change the way you have designed the menu, if you have all of your content in one box then you can segment them as below, so levels with less content will not have lots of empty space. So instead of having your sections rest as vertical sections per level you could ...


1

I just have to throw in my two cents here, despite the fact that this question is so old. If you have a bunch of data that is ALL necessary for the user to make decisions, then obviously there's a decision-making process that's based on that data. Rather than putting the onus on the user to make those decisions based on raw data, what you should probably ...


0

Why not both? Consider these two scenarios: User has decided to add a few new players. They then want to generate a new team with those players in the roster. They don't care so much about the existing teams, because they were generated before the new changes. User is looking for a specific team. They want to know if it exists. They go through the list, ...


0

The question is actually simpler: Does the player list require interaction from the user (i.e selecting players) or are the big lists just for display purposes? Button placement depends on the users flow. In the case of a typical form for example, the flow is this: input required data > button indicates the action to take when complete Does the user have ...


1

First of all: I understand you're under pressure and under some limitation. I will try to offer some improvements, but this is not the best solution, and might be problematic. Try to make the best of this by Monday, but try to get another timeframe for improvements. Suggestion: If you must view, edit and add on the same UI, tread carefully. You're ...


1

I wouldn't display "No Tip" as an option in a list of tip amounts, that is a form of social pressure. To avoid social pressure, do not require the user to say yes or no, in this way by not taking any action, the decision is to not leave a tip. One idea might be to provide a button at the bottom when reviewing the total payment. "would you like to leave a ...


3

Tipping varies wildly between countries, and even between industries. I would suggest two alternatives: If possible, have the operator cofigure the menu according to his particular indusry's customs. Perhaps he could choose between placing the "No tip" item at the top or at the bottom (I think it's usually very inappropriate not to tip, or very uncommon ...


1

It looks like you can't do much to make this easier. If these are the only options you have than I would go for option 1 and leave it up to the seller to explain the tipping function. Your option #2 is misleading and #3 is confusing. Explaining the tipping function can be done in a very approachable way: Press the arrows to choose a tip if you will and ...


0

This totally depends on your culture. In some regions/countries, tipping is seen as normal whereas in other areas, tipping is totally up to the customers and not taken as an offend it a customer doesn't tip (some places in europe e.g.) So depending on your culture I'd go with option 1 or 2.


-1

I personally like the table checkout at Chili's Restaurants. They use Ziosk. Once you've swiped your card, you're taken to a tip selection screen. If I recall correctly, 20% is selected by default. To not leave a tip, you have to move the slider to zero. You then click "Tip This Amount" to get to the signature step. I feel that making the tip selection an ...


4

For text, it's because of how many words/characters per line are comfortable to read - much research has been done and many blogs written... For images (think Facebook), if they were wider, they would get higher as well and you couldn't see much content without scrolling. I believe multi-column designs have been tried, users didn't know how to navigate ...


3

What you're talking about is "fixed width layout". There is a lot of debate around this. See this article for starters: http://www.smashingmagazine.com/2009/06/02/fixed-vs-fluid-vs-elastic-layout-whats-the-right-one-for-you/ I think the main reason is that people with sufficiently large screens often don't maximize their browsers, but have them in parallel ...


1

I'm just guessing, nothing too formal: Looking at the Facebook-style "content column" design, what would be the opposite of that? I think a Michael Bay film would come close. Bay want's to make you feel lost in dynamic imagery. Have you sense the motion, intentionally making it impossible to grasp every detail. When you consume content, you want the ...


1

Keep DRY With categorical information, you do not necessarily have to show the category label repeatedly. Use proximity to group the category and subject. My guess based on your img your users are very savvy and will recognize icons. Leverage them to save space. This way even if things are three or four levels deep you can still relate them with {icon} / ...



Top 50 recent answers are included