Hot answers tagged

58

The physical mute and volume buttons affect all other apps too. It's better to have a mute button in your app because as a user I may only want to mute the notifications from your app and not others. For example, there's a chance I want to mute Facebook notifications but not those from Twitter. So for that I'd need a mute button in Facebook because the ...


24

I'll make this an answer so I can expand on my comment. Your main problem is not an arrow, icon, color or emoji thing. Your main problem is a conceptual one: you're mixing taxonomies with gradations that might be (they actually are!) absolutely opposed. Thus, you're adding a load where user has to make an interpretation of whether your taxonomy and your ...


19

Perhaps you could use only black for the arrows so that the user knows of the increase or decrease, place them on the left, and then on the right use a "health-bar" style status report which would look professional and could indicate the positive/negative aspect and even severity. (Use colors other than Red/Green if you are worried about color blind issues) ...


12

TL;DR: An app forcing me to use the global mute would be uninstalled in the blink of an eye. So they better have a mute function if they want to use audio at all. EDIT: The previous was a bit too short for an answer, here's an explanation: Audio is in essence quite intrusive, that is, you can hardly block it out. That's different from vision - you can ...


11

The Apple Human Interface Guidelines are 'Guidelines', not 'rules' - you don't have to follow them entirely, design and build what you like.


9

Just a small extra consideration but I'll make it an answer anyway. I tend to listen to the radio via an app whilst playing casual games so need to be able to choose which app's volume to control. If I had to use the volume control for all apps I wouldn't be able to complete half of my objective (as I want to do both). This goes beyond the other answers that ...


8

I have always liked these icons, which indicate a trend on a graph. The combined shape and direction of the arrow indicate how the trend is progressing. I got these from Ionicons: http://ionicons.com/


7

Mobile OSes usually have broad scoped sound controls instead of app specific ones. Android (AOSP) sound volume has three separated controls: one for general effects and notifications, another one for multimedia apps and the last one for alarms. But those are system-wide, so adding sound controls into the app you can control the app specific sound volume ...


7

Put the good at the top and bad at the bottom (or maybe reverse this if you want to attract more attention to the bad). This way, you will have two sections divided by a clear conceptual mapping. I would imagine that the main question is more along the lines of "In what areas are we struggling?" rather than "Did this section increase or decrease?" This ...


5

Typically, the top performing apps have shorter (branded) titles The average for the top 200 free apps are: 26 characters 4.5 words But it probably doesn't matter App title length – if penalized at all by Apple, is easily offset by increased downloads or other variables weighted by Apple’s app store algorithm. It is up to the ...


5

In your UX approach, users have to be your top priority. An Android user will have different habits to an iOS user and vice versa. You are talking about a "feel". I understand this to mean a graphic feel, and the answer is YES: keep the "graphic feel" common between platforms. If you're talking about interaction design (navigation, action buttons, ...


4

Guidelines are guidelines. If you follow the guidelines, you are leveraging the platform's consistency. This reduces the cognitive load for your users because they already have an innate understanding of how to use your app, and because your app is more likely to feel like it fits along with everything else on their phone. If you choose not to follow ...


4

Summary: Carousel control has some drawbacks on mobile. More straightforward solution could work better. Still, A/B test is the best way to evaluate the idea. Some consideration on using carousel control: Interaction style People interact with a mobile in a specific way. You can find some insights in the How Do Users Really Hold Mobile Devices? ...


4

Generally, for mobiles, breadcrumbs are not recommended; the back button is what the users are familiar with. Also, it is said that; if your app needs a breadcrumb then your app is not easy to use. Even though, if you really want to introduce one - try what Windows does for the deep hierarchies:


4

Yes. It is a pain and iOS is doing it wrong. You should never impose your rules on user. They won't like you and this is the fact that most Android user hate iOS. Sites should definitely allow case sensitive usernames, but you should never assume that all users will have their first character capital. Edit: Here's a good workaround to avoid that - it's ...


4

You are right to avoid the use of colour alone - especially when considering red/green states of the same shape. The way to approach this is by changing the shape of the arrow and there are a number of ways you could do that. As a few of suggestions: 1) You could bring left and right into play, where right is progressive and left is retrograde - an arrow ...


4

To build on @Adriano Repetti's answer, and again borrowing from Information Dashboard Design by Stephen Few, I would like to highlight some assumptions about your view and make a suggestion. As someone who is not colour blind, it still took me a while to figure out what all the arrows mean! Your interface confused me, so I tried to think about what you are ...


4

Perhaps instead of unprofessional emoticons, you can use a simpler symbol to indicate a good or bad result. In this case, I used a tick and a cross: But since the indication is probably more important than the direction, we can place greater emphasis on the ticks and crosses: Note how the arrows are now smaller and faded towards the background colour, ...


3

I encountered an issue similar to this with a shopping app where the cards for items were a perfect fraction of the page space meaning that the last item on the page in its default state ended just clear of the fold (page break). During user testing most users reported that there was a lack of items available because they didn't realise they could scroll ...


3

It's not capitalizing form fields but automatically running sentence case. If you break text with a '.' or start a piece of text in a new field it will automatically capitalize the next letter as it guesses that you've ended one sentence and started the next. In cases where you don't leave a space after the '.' it assumes you're typing a web address and ...


2

In general, it is useful to have shortcuts on desktops because you are use the keyboard anyway. On a smartphone or tablet on the other hand, you are not continuously using a keyboard. Therefore, you would need to open the keyboard, to be able to do certain actions, which would simply result in an extra step for the user in the process (opening the keyboard, ...


2

You can add an "Action" image in the table view cell. That can make users understand that will be a Share Extension. This is an example from Reeder.


2

I'm not aware of any studies for this but I would say there are a couple of possible answers. If you're displaying time in 12hour format (i.e. 10:00AM and 10:00PM) then you could easily display hours below 10 as a single digit. On the other hand, if you're displaying time in a 24hour format (i.e. 10:00 and 22:00) then you're more likely to find that a ...


2

I think it would be totally fine with the Edit button contextually relevant to the content or segment. You can try to disable or hide the Edit button when users switch to other segments. But it's true that the location of the button makes it a bit like for the whole page. The alternative approach would be that having the Edit button in the header of the ...


2

Firstly, colour should never be the only way of distinguishing different messages. One of my pet hates is coming across system status indicators that simply show red or green! You haven't done that - You have three different ways for users to distinguish the different messages: The 'urgent' flag sits to the right of the list item, the validation failure ...


2

If you want to make it available to "dig deeper infinitely through the application", it's really gonna be difficult to use. But if there are only 2 or 3 levels of hierarchies, you can do some indentations. (courtesy of IMDb app) The screenshot here only has two levels, but if you want to go deeper, you could have a sub-level with more indentation. (Just ...


2

I'd avoid to convey information only with colors. Green for "up" and red for "down" is not an universally worldwide accepted pattern (and color blind people may not see them). Given the fact that you don not need color then I'd simply drop it. Use a gray symbol, color is not needed. To better give sense of trend (and to clarify symbol meaning to don't ...


2

Consider separating the list into two sublists, one of "things which are good when they increase" and one of "things which are bad when they increase". I'm not sure what your exact business domain is here, but it sounds like you have income generating items and liability generating items, so why not just make two lists? This could be done "in-line", i.e. ...


1

"Consistent UI as opposed to native experience" is a contradiction in terms: if you break the native interface conventions, you are by definition not providing a consistent UI for your users. Your application doesn't exist in a vacuum. Users switch between apps frequently, especially on mobile devices, so it is important that your app follows the same ...


1

Just look at it. Stack exchange UI design that isn't platform specific. So should your design be, but only if you make a simple appealing design, and not an overcomplicated grey mess of buttons (seen that one before). If it's good than yes, use custom UI, if no, then use built in UI.



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