New answers tagged

0

A (top/bottom) bar navigation is a pattern that can be very effective, but isn't widely popular on Android. This is exactly the reason why you were able to find multiple iOS apps who use it, while Android seems to be "lagging behind". There are multiple articles talking about this in general, mostly how this tabbed navigation should display core features ...


0

I would suggest two things: Trust your users, and continuously run user testing to see what users truly do with your application. Different from other responses, I would suggest following what YOUR users do. Google's very first guideline is "focus on the user and all else will follow". Google's guideline regarding the back button is what they hope the ...


0

Nick Butcher, a Google Design/Developer advocate, advises to clear the back stack on switching categories using the navigation drawer.


1

Nick Butcher, a Google Design/Development Advocate, has addressed this in this presentation: https://plus.google.com/u/0/photos/+NickButcher/albums/5981768132040708401/5981768199164803938?pid=5981768199164803938&oid=118292708268361843293 : "Selecting a section in the drawer should reset your task back stack". Also, the reason why the back button does ...


0

Something might be wrong with your navigation, something might be wrong with your test, or this really is a true usability problem with Android guidelines. I'm curious as to the nature of your testing -- if, for example, you instructed users to "go back to the first tab", the phrase "go back" might have prompted them to use the back button which they might ...


0

There's a who lot of detail and good analysis in your question, but there's only one answer: Ask your users Test some prototypes and see if people understand what you're expecting them to do. Depending on the audience, there's a lot of flexibility to be had with additive and subtractive tags. It could also just be way overboard. Only your target user can ...


0

It looks like the home screen lists all of the student's subjects, with one card per subject. Each card displays three upcoming events for that subject, and the users three most recent notes for that subject. Am I getting that right? This design seems ok to me but I don't know if it's the best way to display information to the user. Am I just ...


0

I think that's a reasonable concept but I suspect you'll have difficulty displaying that much information once you've increased the text size (which is obviously too small at the moment, as you hinted at). In particular I think displaying three events will be difficult. I'd be tempted to just show the next upcoming event. That will be easier to display ...


0

Not suitable for every app, but here's a suggestion:


1

This is normally done something like this... "More..." so you can just use three dots as an icon. ... This is now how iOS does it, too.


1

Question and answers here are old, but the challenges when it comes to some kind of multi level mobile navigation are timeless. The most obvious choice is the NavigationDrawer (left sliding menu). It’s the prefered pattern if you have really complex and feature rich structure from the beginning. Another scenario is when you are just starting and need the ...


0

Imagine a world where your most frequently visited restaurant moved closer to you based on how frequently you went there. How would you find it? This should not be the primary way apps are sorted because the real estate where apps are placed is an address, and people remember it. If a user is so dull they don't know how to move apps around, it's even less ...


1

Here I can see 2 cases one is when to enable the button and other one is what would be the right label for the button Here is my answer Whenever the user inputs the data, enable the 'Send Later' option. If user fills the mandatory info, enable 'Send Now' button. Hope this helps I feel you should change label from Send Now to Submit, Submit is ...


0

This is one of the option: Change name of buttons: Rename "Send Now" to "Submit" and "Send Later" to "Save as Draft". This will remove the dilemma with "Send Later" button that when to send? what does later means? In what time?. In this case, what you can do that is on clicking submit in offline mode save it as draft and in flash message tell user "You are ...


0

Why not keep the feature? I personally hate it when the mobile version of a website has dumbed down functionality and/or I have to switch to the full site just to make it useful. For devices that handle this nicely and have a real file system (Android, BlackBerry, Windows, FirefoxOS...) they get the desired functionality out of the box. For iOS the user (...


0

What does someone do with the .csv file? Does it make sense to download a .csv file on an Android device? The answer to these questions should guide your solution. One of the challenges with responsive design is working out what features should be available on desktop vs tablet vs smartphone. Just because you can do something doesn't always mean it makes ...


0

As per the standard its always better to show visual indicator on expansion or collapse of the list. Keep the arrow/chevron indicator on the left whenever the count exist. So that both the icons are visually balanced.


1

Not sure the use case for this. what are the tabs? what does the app do? I think perhaps there is a way to prompt your users to move to the next tab without auto-moving to the it. The issue is it's an action that the user can not undo, if i'm scrolled at the bottom of a long list, then auto moved to another list...i just lost my place. Also it's not a ...


0

Does the landscape mode offer a significant better user experience? If not, is it worth the effort and compromises? It's acceptable to restrict the app to portrait mode only.


1

I feel you need to refer the UX.stackexchange.com, after submitting the comments, it shows process icon with message. For submission of article, showing the progress/process icon would be better. Showing as background save would not fit here. Background task best fits in File sync, download and etc.


0

I like HKYL's suggestion, but I would add that even if something is happening in the background, you should indicate that it is happening to the user, no matter what the conditions are. For some users, having no indication of any progress can create anxiety and uncertainty about how the system is working and if their work is going to be retained. We can ...


0

You should put it in the background. When it fails, pop up a notification and/or a black bar that says something like "Publishing failed. Retrying...". And also, if the user requests the list, and the app knows it's still uploading, it just should add a little mark, that says "In progress...".


0

I only fancy having the back button on the toolbar. As a user, it's hard to reach for the confirm/save button if it's in the toolbar. Isn't the whole of this screen to confirm/save? It should be placed in the area where it is easier to reach. A floating action bar perhaps? On the landscape view, the toolbar should still be placed on the top area. The ...


-1

According to me, The toolbar should only contain the back button. Devices are getting taller and taller, so the save button on the top would be a bad User Experience for the user when he uses your App one handed. So I would go for a FloatingActionButton in Bottom|Right of the Screen I would also suggest a FloatingActionButton which would be hidden till all ...



Top 50 recent answers are included