Tag Info

Hot answers tagged

7

The Android design resources are a pretty good resource to look through. If a frequent or important action within the context of that screen is to add a row then you should consider putting it in the main action bar. From the Android guide: Show the most important actions of your app in the actions section. Actions that don't fit in the action bar are ...


5

You can use two actions in a row, Apple does support that with its standard UI elements. Its called the Detail Disclosure button. * * Users tap a detail disclosure button to reveal additional information or functionality related to a specific item. The additional details or functionality are revealed in a separate view. * From IOS Human Interface ...


3

From a UX perspective, it looks like the table you've got is a bit dense for a smartphone screen. I would start by figuring out which of these columns people are going to want to browse by. Are they scanning for a particular concept ID, or are they going to want a list sorted by type, or are they reading all the descriptions? If you answer those questions ...


2

It depends on how and where you want to use the list. As a best practice for better usability, it is best to represent a list with alternative row colors for each list item - this makes it easy to read, which makes even bigger difference in a list of sentences as user can read each sentence and know without any confusion where it ends and the new one begins. ...


2

Your second suggestion (and as per your image) are perfectly usable and meets the requirement to be able to browse the list and jump to a specific point. Usability trumps 'looking a bit weird' in this instance. However, depending on your use case, another option would be to split all the neighborhood into expandable panels so that the user can scroll up ...


2

I think you can, regardless of the phone OS. If you take a look at Windpws Phone Call History, you have two different actions on the same row. The first item is an icon of a phone, and on key press you will call that person. The second item is the name, which on key press will lead to that persons contact information: But to make this work you'll need a ...


2

There are multiple ways to approach your problem. But first of all, I'll give advice that cannot be given often enough: Get rid of clutter first. Especially in a "data intensive" environment. The rule of thumb here is: If you have more than about 7 columns you're doing it wrong. Look at every column, find out if you actually need it and come up with ...


2

Constraints The root of your problem is that your system involves 3 states, two of which has functionality constraints (the non-manual sorts). As such, your task is to convey the constraints to the user in an optimal way. One (of many non-optimal) options I can think of is to have drag handles that will be greyed out in non-manual sort. But this requires ...


2

I don't see a problem with it. 'Consistency' doesn't mean 'sameness'. Users can handle changing interfaces just fine so long as they understand the change and there's not many states for them to remember, and changes don't compound on top of one another. After all, no-one complains when only some pages on a website have a scrollbar, or when a context-bound ...


2

Screenshots. They'd add visual appeal and might add functionality as well. I can tell from a screenshot which page on my site is being referenced more quickly than I can scan the URL. A visual way to browse popularity by screenshots could be interesting. http://pttrns.com is a site about design patterns, but the overall style (big pictures, minimal ...


2

The tradicional Windows Grid is not recommended for that use. There's a guideline for search purposes: Start app page You can use auto suggest, but filter should be placed with the results Here's an example of how your results list could be. Kinda like this For more Windows guidelines info: ...


2

UPDATE: Tog already replied to a similar question at Ask Tog. I agree with JonW. Although this might seem redundant, it supports browsing and searching in a graceful way, without getting in the way. Another interesting side effect is that it provides a better way to browse than an scroll bar would. Instead of having to scroll until you find a visual cue ...


1

I have reservations about "answer"ing this, since as user @Izhaki points out, it depends so much on the context - one cannot really say what looks best without seeing.. anything. That said - I would suggest that any more than 7 is starting to become untidy. How do I arrive at that number? I recall that on average people can perceive 7 distinct entities, ...


1

Searching is only practical with a large number of contacts. Scrolling is more practical with a small number of contacts. To facilitate the middle ground where you might only have a small number of contacts, but too many to look at each name to figure out which letter you're on there's this rolodex style annotated scrollbar.


1

Since you're working on WinForms that means that you're actually on a Windows Operating Systems. In your case with multiple choices I would go with the more conventional Windows style and use Add and Remove arrows, as the mockup below tries to explain. download bmml source – Wireframes created with Balsamiq Mockups Most Windows users, and ...


1

I would suggest you lazy-load your pagination into one list. Load up 10 initially and then when you are at the bottom of the list append a loader, fetch the next 10 items and replace the loader with the next pages results. Rinse, repeat. I think it's also known as an infinite list.


1

I think that there is no pagination on mobile devices, not the way you use it. Your use is usually covered by vertical scrolling. If that's a problem because of performance or other reasons, you put your first batch of items on the screen and either a button or a gesture that says "Load more" and gets you to the second batch - but the layout is still ...


1

You can easily have up to four or five actions in a UITableViewCell if you desire. Even apple's native apps have this (ex. itunes has a preview for the first 80px, a detail info for the next 260px and a purchase for the rest...) Like this: So you go on ahead and make as many as you see fit. Just make sure to program your touch gesture recognizers so they ...


1

This is a fairly standard approach. My phone (not a smart phone) uses a similar approach for the contacts list. On the list the names are presented next to a phone icon. Click the name and you get the contact details, click the phone and you call that person. Your users should either be familiar with this type of interaction or will soon get used to it.


1

You should check the ratio of line spacing and the height of the gap between sentences. If you can cluster each sentence and provide nice breathing space between items then you don't need separators. The more important question here is whether each item is selectable and has some signs or buttons, or something like 'disclosure indicators' next to it, then ...



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