Tag Info

New answers tagged

0

In relation to your question, I think that the solution two its more right than first solution (maybe the buttons All and None, like landonz said, would be better delete it if it not are necessary or found other solution for that buttons) but it have keep in mind the colors of buttons. There are accessibility guides for use colours in web applications (W3C) ...


0

I don't think users should edit their posts in any other app which isn't the official one (or something from third part that replaces it), because I think it could be confused. But in that case, have you thought about the possibility to implement it as native system extension, like in iOs? The user could upload its photo to your website with a caption, and ...


1

A term that comes to mind is panel or pane, but looking at your "web application” it looks more like a website to me. The fact that it loads pages dynamically and slides them in doesn’t mean people will see it as an application, that depends more on it’s contents. So I think the term page will be generally understood in this case.


1

I would word it as "Choose section", which indicates a grouping of a given content type which is likely to include "pages" in the content. There is no hard and fast rule on this, so I would strongly suggest doing some basic UX testing with your potential customers to see which is more intuitive to them.


0

Just use Photos (ref screenshot from Dropbox app for iOS)


0

Only having it on the "scan" tab sounds perfectly acceptable & is the way most tab-separated apps work, esp in iOS. Each tab has a distinct associated view for a different mode or sub-task. If the "Scan Options" functionality only makes sense to use inside the "scan" tab then put it there & nowhere else. That said, if you wanted to have a dedicated ...


0

I will say I can't tell the active state by the contrast of yellow and white. Maybe add some shadow/darker border to indicate a pressed button. If use the visual indicator as a states indicator, keep in mind the visual style should be consistent with the rest of the pages. Different visual styles will confuse users.


0

You should provide the " fastest and easiest " way for your users to get into your application. I recommend doing what the SE sites do: This let's me sign in with whatever method I want. You can look at Using OAuth 2.0 for Installed Applications for more information: iOS specific resources: Google+ Sign-In for iOS Facebook Login for iOS


0

Username/Email: With mobile experiences, the most important thing is to reduce typing and reduce unnecessary steps. It's a pain, and therefore anything you can do to cut down on text entry will be useful. Equally, what information do people need to provide before they can use your service? Imagine Flickr, a profile could just be empty - except for a ...


1

I kind of feel like if you have to ask, then you should be doing more to visually indicate which buttons are active than just using color. Google has some good guidelines along these lines: http://www.google.com/design/spec/components/buttons.html#


2

Well, I think there are a few factors that need to be considered. What does the rest of your layout look like? What colors are you using? Where are these buttons placed? All of those things (and more) will come into play when your users are trying to determine whether the button is active. My suggestion would to do some AB testing with your potential users. ...



Top 50 recent answers are included