Tag Info

Hot answers tagged

79

With regards to your question of whether a bot can actually go and submit a form automatically, this is what I found on an answer on Stack Overflow. It is comparatively harder to automate data submission within native apps. This is due to the fact that you cannot just write an automated script to discover elements within the source code and then ...


62

This study of 1,333 people has some great information on how users hold their phones, and which areas of the screen are most accessible. Their data showed that people held their phones in 3 basic ways one handed — 49% cradled — 36% two handed — 15% The accessibility heatmaps looked like the following: Single Hand Cradling in Two Hands ...


46

Some phone numbers are tailored to use a mnemonic "lettered" version to be more easily remembered. Think of an insurance company running a commercial on TV and its goal is that you call their number. If they use 1-800-INSUR-ME, it'll probably be more easily remembered than 1-800-4678763.


33

If a multiplatform app has an iPhone-ish UI because it was first developed to iOS, I see that as a cheap solution and negligence of the other platforms. If a vendor takes the time to develop the application to integrate properly with the OS, have a native UI, use differentiating features (like notifications in Android) etc., that's much more appealing than ...


22

Snapchat recently added image recognition: (http://venturebeat.com/2014/01/22/snapchat-find-the-ghost/) Note: As most captchas, this is also breakable. But until your app becomes a popular target, this is a pretty nice alternative ;-)


16

Because whitespace is important. Being able to quickly skim the list and pick out who said each response is important. By adding left and right whitespace it makes the list of messages far easier to scan. It also makes the application instantly accessible from the very first sight; if it were just white and green with no justification, then people seeing the ...


15

If you are going to be prototyping for iPhone, there is a very interesting iPhone Mockup tool I found recently. You might also want to consider the listing provided by this article, it has a lot of stencils and tools on the subject.


15

Less an answer and more a word of caution: Be careful not to let your personal experience and preference cloud your judgment for what's best for the actual users of your products and devices. Which orientation helps them get shit done? Prefer that. I find it a little concerning that the first few answers are all: "I like portrait better. I like landscape ...


14

Rather than asking the user to answer a question or choose a correct picture or enter something, another option is to simply delete something from a regular text field. From an implementation perspective at least, it could not be easier!


13

You shouldn't rely on just color for this. Most colorblind people cannot differentiate red and green, especially on very small icons. One possibility is to have some sort of network connectivity symbol to show when the connection exists and put a large red "X" over it when the connection is off. Use color to reinforce the symbol shape. Even spell out ...


11

This blog post links to the Windows Phone 7 Series UI Design and Interaction Guide, which is probably of interest to you. If you are building a native app, you probably want to make it in accordance with the device's UI guidance. An exception might be if you are making an application that provides an interface to a website (like the Twitter and Facebook ...


11

Apple calls it a "Picker" in its iOS Human interface guidelines. Picker A picker displays a set of values from which a user picks one. To learn more about defining a picker in your code, see UIPickerView Class Reference. Appearance and Behavior A picker is a generic version of the date and time picker. As with a date and time picker, ...


11

If the gesture is easier than the code, why haven't website login pages adopted this? Accessibility: How is someone supposed to draw a squiggle if they can't use the mouse? Recordability: Look at a numeric keypad (1 in the lower left corner). "183456" is easy to write down in a text editor for the memory-challenged. Furthermore, the only squiggle I ...


11

Here is what I would do to have A/B Testing done on Existing Customers / People who already have my app: Both the flows of the App you have in mind should be bundled as a part of the same app. You use the code injection to send information to Flurry. Use the same method to check how many users have downloaded the latest version of your App with both ...


11

Google doesn't always make the best or consistent UX decisions. Their Google Voice application (which I assume is created by an entirely different team) has "New" and "Refresh" buttons at bottom-left corner. But I agree with you, putting the "+" in the top right corner is poor usability for frequent-user of the app. However, it does make the button ...


10

For the first case, the "information", it's perfect and I recommend it. IMO the "i" icon shouldn't be used for your second case, that's meant to have a different icon! (such as something that represents "settings" or in you example, "renew/subscriptions").


10

Option B is better for the user of the device at hand. There's no way that device is going to suddenly get a camera on it, so there really isn't a reason to show the user a function that they will never be able to use. The reason that people recommend graying out options not currently available is so that a user will know that it is there and they could use ...


9

Try this: http://www.evernote.com/pub/ikonux/stuff#v=t&n=544d5d02-e7df-4efe-b4ba-9ce74717cc43&b=0


9

They do this because it is easily recognizable by their users. Apple stresses using standard interface elements in their iOS Human Interface Guidelines: In iOS, the UIKit framework provides a wide range of UI elements that you can use in your application. As you design the user interface of your app, always remember that users expect the standard views ...


9

What I've learned from observing some mobile usability tests: Don't care too much about "thumb hotspots". Which areas of a smartphone display are more accessible differentiates a lot from user's individual abilities and habits. As there are: Individual phone holding: Some users are holding their phones more at the bottom, others at the phone's mid. The ...


9

Is bot traffic from an iPhone (or Android device) actually a problem? The problem is not so much 'from an iPhone', but rather that the API you are talking too needs to be protected. At the underlying IP level there is not much you can do to prove what a remote device is, for HTTP it is really just the headers or form data, which a Bot can generate ...


8

Good question - Balsamiq Mockups may be your best bet. They have iPhone controls built in, and someone has contributed controls for Windows Phone 7. They also have stuff for Nokia platforms, etc. Not sure about Android options here. Keep your eye on Balsamiq's Mockups To Go blog for further contributions from the Balsamiq community. I also created two lists ...


8

Yes, it is using the right affordance (to be consistent with OSX Lion). This is slightly confusing implementation of what I think they are trying to achieve. I agree, it does look like the slider/switch control used in iOS. Sad news is, this is what OSX Lion is going to look like. They are changing the look of these "tabbed" controls. See below: At this ...


8

Working on the assumption that you've addressed the information architecture issues and determined that there are infact this many primary and secondary navigation options required for the application there are a few routes you can take for displaying multiple options in a tab-panel (or similar control). The first example here is from Snapseed: Here ...


8

Apple's iOS guidelines say to "Think twice before hiding the status bar if your app is not a game or full-screen media-viewing app." I think their attitude is that if you don't really need the extra space, leave the status bar visible so people can see the time and battery life. Also, from same link above, "don't create a custom status bar."


8

Let's take a step back and look at your business model. Should you even include ads in your app in the first place? Are they likely to be successful? For advertising, context is everything. In general, ads are most effective when the user has what is called "commercial intent", meaning they are looking to make a purchase. The next most effective ad is when ...


7

Dia - this is the best diagramming tool I've ever used. Kivio - a similar diagramming tool that is part of KOffice.


7

This is a very broad topic. What's the context? Is this for a standalone app or a website? It depends a lot on the platform -- a touchscreen works quite differently than a trackball interface for instance, and a hi-resolution device will behave differently than a low-res one (and remember screen size varies widely, too!). Be sure to check the web - Jakob ...


7

The question to be answered, preferably through paper prototyping, is whether the user is confused about this inherent modality of your system. (If you are ever able to switch between roles as a user, then they're modes in disguise.) In general, invisible modes confuse the heck out of users at all levels; even experienced users who understand modes want to ...



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