Tag Info

New answers tagged

1

Answering your question in one word: Adaptive layout.


0

I wouldn't change the interface much between the desktop and mobile. You just need to collapse the desktop version into a single column. So that these options on the desktop Greene Team > Option One (2) > Option Two (3) > Last Option Are then presented like this on mobile Greene Team > Option One (2) > Option Two (3) > Last Option ...


0

The system seems quite complex. Many levels, many users. If you don't need a flat list of all the end nodes (like your design has), I suggest keeping the breadcrumbs. A vertical breadcrumb\drilldown will make it a lot easier to navigate. BTW, I'm guessing that in this product the hierarchical levels are selecteable nodes themselves. Meaning, the user can ...


1

The 10 Usability Heuristics are as close to a 'Bible' as you can get. Visibility of system status: The system should always keep users informed about what is going on, through appropriate feedback within reasonable time. and Help users recognize, diagnose, and recover from errors: Error messages should be expressed in plain language (no codes), ...


1

Yes, it's a normal practice. As you mention with an activity indicator and the option to cancel it'd be okay. A reason for this is because if something goes wrong you want to communicate it to the user as the first step after the "Submit" action. If you introduce more actions "in the middle" of that process, and that action can also have errors, it'll broke ...


0

Yes, you want an activity indicator. Your typical user won't know what's going on behind the scenes and may assume that it froze if there isn't an activity indicator of some kind.


1

I would agree with most of the comments already written, but I'd like to add a little more in case it's useful to you. There are some great articles that suggest you 'delay requiring the user to login until absolutely necessary' (see: http://www.sitepoint.com/improving-apps-onboarding-ux/). Similar to the iTunes store, AirBnB, Quora, and others, try to ...


1

In a way, this is very similar to how online purchases are made. The store, or in this case the municipality, would prefer if the user created an account. In this case the municipality asserts that the user would prefer to create an account but that probably won't be the case as complaints are reactionary and usually preferred to be made anonymously. ...


2

Provide a default action and update to the user's preference from there. The least amount of information required is an e-mail, so just let them enter that inline with the rest of the complaint/concern form. The user can now just enter an e-mail, enter their complaint and hit submit. Quick and easy. download bmml source – Wireframes created ...


0

I think you have to differentiate between 1 / Unable to Use and 2 / Don't want to use. PC's up to about 2005 were pesky complicated things, which required lots of user fiddling with to keep going. So anyone over a certain age (probably about 50) is going to associate smartphone = computer = complicated and unreliable. So I think part of the issue is ...


0

How I will handle that is making the puzzle follow your finger... and add buttons at the bottom and a indicator in the bottom center


0

I must say that I am personally very sensitive to rollover states as my main personal computer is a Windows 8 touchscreen convertible laptop (similar to MS Surface), and I often find myself interacting more with touch than the touchpad. That said, hover is a dying interaction. As we've seen with the hamburger drawer menu, out of site is out of mind. ...


2

I would say there there is just as much change of a user missing a poorly sign-posted rollover on desktop as mobile. I use a + symbol to indicate more in these instances, and sometimes where there is a series of rollovers containing more info, I have the first one open by default to show the user what's there. Generally I really don't think we should be ...


1

There isn't really a need to change the look of the icon, as users experienced with "hamburger" menus know that most of them close the same way that they are opened: by pushing the hamburger button. However, if you really want to change the button icon to help improve the user experience by providing more information to the user, then why not change the ...


1

I will first leave this article, taken from WWDC 2014, which discusses Apple's attitude on using hamburger menus: http://blog.manbolo.com/2014/06/30/apple-on-hamburger-menus Here is another article that actually discusses user engagement in a real application that switched to a drawer (aka: hamburger menu) and then promptly switched back when they realized ...


0

My gut feeling is that if the whole page slides to the right, revealing the new menu, then the arrow facing left makes sense, because I want the page to slide back to the left. (That's also consistent with left arrow typically representing "Back"). If the menu covers up the content, then I want that button to tell the menu to hide itself again, in which ...


1

Well, there's a couple of ways you could go. An obvious one, just leaving out some less important columns when scaling down Flip scroll. When scaling down, the headers at the top 'flip' to the left and allow the table to be scolled horizontally. Important note, the header labels stay in place. It looks something like this: I've used this method before ...


0

One thing nobody's mentioned so far: Our experiences with non-animated user interfaces are degenerate. We old-timers are the weird ones. The real world is "animated", everything constantly gives feedback by moving, and our minds were created to take advantage of that. As we barely had the CPU cycles to reflect changes the user made in real-time in the past, ...


1

I'm not sure if you can control that the site is opened in a webview under other apps (I don't think so). There is no way to deal with it, some apps open the sites in-app, some others do it in the browser (safari). You can't do anything about it. Maybe the best way to deal with it is basically avoid fixed headers in mobile webs, so you will have only one ...


0

Here's how I solved this in a similar app: When the default keyboard is presented, you also present a second subview above the keyboard with the buttons [1][2][3] etc. horizontally across the top row. Those buttons essentially act as a "faux" keyboard row that shows/hides with the keyboard. You can also bypass the default keyboard altogether and design your ...


0

I'd prefer the navigation tabs approach, but if there are just two possible modes you could simplify it by just giving the option to select the mode in which you are not positioned.


0

There might be a case when the number of links in one of the panels of the accordion is so large that the user ought to scroll to see all them. In which case, using an accordion instead of a long list seems futile. But, at the same time, when using a long list the user may not be able to view all the sections and links in one go. Accordion, at least ...


1

A couple of solutions may help you here but it depends on the level of control you have over the user flow between the app providing the key and your app receiving it. QR Codes If the user is getting an API key from a service in a desktop browser to passing this to your mobile app you could consider implementing QR codes in the desktop view and a reader ...


1

Object-oriented actions In all examples of Material Design that implement the floating action button, we've seen an object-oriented concept at play within apps: Email (Inbox) Document (Docs/Drive) News (Newsstand) Direction (Maps) Arguably the concept of a singular most important action creates a nicely hierarchy of user actions surrounding the key ...


2

It's hard to say one way or the other. We can list pros and cons and offer opinions but at the end of the day, it's going to be heavily opinion based. All that said, do be careful of judging screen shots. A big hurdle we in UX have to face is feedback coming to us based on static documentation...wireframes, mockups, screen shots, etc. None of these provide ...


7

It's tempting to say that because we're not used to it, it must not be a good experience. I think we mean that change is necessarily a good experience... it's not comfortable, but the end result may actually be better than what we had before. We are used to toolbars, but how often do we get lost in menus or confused by a row of buttons? The single floating ...


1

In some cases I could see it blending in with whatever's behind it, which would be a bad thing. People who are left-handed could still potentially have to change how they're holding their device in order to press the button since it may be out-of-reach, depending on how far they can reach with their thumb.


5

The good: Fitt's Law: The bad: The biggest flaw in Google's Material design resides in feedback when you press a button. In the physical world a pressed button recedes into the background; in Google's Lollipop the opposite happens, when you press a button, it floats, which is contrary to what the user is accostumed to.


0

There is no reason to give a preview option on text-only posts. The content of the post is nothing more than the text entered. By "previewing" it, the user just sees the same text again on a different screen. What benefit does that give? "Preview" only makes sense when there is something about the content's appearance that you won't be able to see in the ...


0

There may be value in temporarily doing it to allow new users to get familiar with the appI would say do it the first time or 4 and then have a never do this again option. That way when they are still getting familiar with it they can undo. High risk publications may also benifit from a preview. Ie changing your relationship status or your place of ...


1

Great question. This won't be a definitive answer by any means, but here are a few key things I would keep in mind. Note that some of what I'm about to say has already been covered very well in the following two articles: How Should Your Mobile and Desktop Sites Differ? Your Content, Now Mobile Which information should be left on the map? Short answer: ...


1

At first glance, this appears to be similar to having a carousel within a browser window. This pattern works well for browsing a series of items. There are in-page indicators of scrolling progress and the UI is arranged in a way that delineates between window-level and component-level scrolling. In other words make sure your target areas are designed to ...


0

I have never seen a good mobile web experience any good that had horizontal scrolling. Never. Just don't do it. If it's an app, you have some more leniency, but it's critically important to be highly cognizant of where you place those horizontal scrolling sections. A good example for a place is for photos that scroll horizontally...it's an actual object ...


1

disclaimer: I am a developer, with personal interest for UI and UX. So my main competencies are on the dev side: feel free to comment and let me know if something I say is questionable. What kind of style you want your UI to have? Using rounded corners VS square corners have IMO more implication than just solving the "blend with background" issue, I'm ...


0

The solution that will suit your case seems to be Lazy Loading. Instead of loading all required data in one go, load it in a staggered manner. Also, if your dashboard consists of independent sections visually separated by tiles, then instead of having a single loading gif in the center of the page, you may consider having a separate loading symbol on each ...


0

The question is...confusing. If you are able to store the poll data in an app, then you're able to do so on the web as well. However you store the poll data should in theory be visible and editable (add-only, like 1-vote adding per mac address for example) and then the two would be relatively in sync. Then all you have to do is just make sure that the app ...


1

As a phone is an "smart" device I would expect that there would be a better UX than mapping a static paper/digital map into phone format. I would approach design from a goal driven point of view e.g. A fire escape plan has key information if there is fire, but this information is just ancillary. The goal is to get out of building safely and as quickly as ...


0

In general, all solutions except for B work. B requires specific hand placement on the device (size of the handset was not considered) to reach the buttons comfortably. C, F, and G don't deliver enough context because of the lack of text; you're right, the notion of a room versus a conversation needs to be expressed in text because the icons do not express ...



Top 50 recent answers are included