Tag Info

New answers tagged

1

You might want to take a look at how the Google Maps app tackles this on a phone. If you want to see it in action, I've recorded a small video from my phone: Google Maps search results UI on Android [youtube.com] In my opinion, it's the best way to execute that kind of feature. Small note: On the first time, Maps shows a small "tooltip" to indicate that ...


0

I don't know who your users are or how complex your icons are, but in my opinion, using only icons means potentially excluding or alienating the types of users who don't understand what the icons are and who aren't willing to tap on a button whose function they don't know. The only advantage I can really see is a cleaner visual design at the expense of ...


-1

You can try adding spinner instead of sub tabs like in following image. Here you can give even more options.


2

The UI is right now consistent and improper. Considering user's mind, he will have to run on the screen to perform various actions. The best option to be applied here is your first point. i.e. Hamburger icon on left side. So that the user can have access to all the options in one go. e.g. You will put everything under hamburger icon but for Home button the ...


0

You could try using a slide up drawer? Kind of like this one from Google Maps? http://cdn.pttrns.com/377/3927_f.jpg If you could solve the issue with displaying the number of events in the icon, maybe that might make the issue of navigation drawers irrelevant?


0

How about adding some interactivity to it? Perhaps you can request a detail off the user (e.g. enter your postal / zip code), then show only the closest events to that postal code? In fact if it's a mobile app you could just request that they share their location data and that way you reduce a step. If it's not necessarily helpful to know where their ...


2

Check out the Ionic framework. It's a newer framework for hybrid apps that just hit 1.0. It's built on Angular, which means it's battle-tested in production apps, and easy to pick up if you're already familiar with the framework, as well as leveraging Cordova (PhoneGap) for cross-platform binaries. Angular has modules or components for everything you should ...


4

It's best to follow current standards for mapping. That means, in this case, setting a start and end point by either dragging flags into place or tapping on the location while dragging to move the map. Most (if not all) map apps, ie Google maps, Apple maps, Waze, Bing, and more follow this behavior. At the risk of sounding like you should take the safe ...


1

If this element is important and represents a need for you, then it should be always present. Now, I have no idea what your app is about, but you could consider these choices on top of the above: Ask for feedback after action is completed Let's say your app performs X action, or you have a video or whatever. Then you could end that action with a CTA ...


0

The best place to put the feedback (theoretically) is after the user has had a chance to complete the goal/task which you want feedback about. So in most cases this would not be near the top for new users, because it would be difficult to provide feedback about the site when they haven't had a chance to experience/explore it yet. On desktop websites the ...


0

I would put some label indicating that the site is in beta near the site title. Clicking on this button could be a good way to give feedback. If you want a separate feedback button, near the top of the site would make sense. This would be especially effective if it was a "sticky" button, i.e. it stays at the top of the screen even when scrolling.


0

I think if you have a touch interface and you are willing to explore options, I think circling items would be a pretty interesting way to do multi-selection. This probably wouldn't work so well on a mobile phone, but perhaps a tablet would be an ideal way to explore how this might work.


1

You could have (apologies as this is crude): Switches: download bmml source – Wireframes created with Balsamiq Mockups or Suggest 'Hit Area' around the item: download bmml source


0

You could try using an accordion instead of tabs (here are some pros and cons), but it won't always work. Can't say that I see a good way of integrating tabs into the sidebar. As you mentioned,it doesn't look very good, and for a good reason - if all your objects have the exact same structure, it doesn't make a lot of sense to repeat it for each leaf in the ...


0

I think there are two main reasons content isn't organized much in a tree/folder structure in mobile designs, and they have everything to do with the device and not the content (and I disagree that the presentation needs to be similar): screen real estate and touch interaction. Tree structures benefit from larger screens because one of the features that ...


0

I saw a research on how to use users feedbacks (i.e. comments) in appstore/googleplay as a starting point for usability studies. This was presented in IEEE requirements engineering conference. Will post the link here if I find the paper.


2

They will likely use server side device detection based around the User Agent to show an alternative version of the website. This method is know as Dynamic Serving. Bootstrap uses the viewport width to change the layout via CSS, known as Responsive Web Design. There are use cases and arguments for both techniques. EDIT: I'll expand on the cases for each a ...


0

It's a tough question because it depends on a lot of things within your app. Things such as overall UX, UI elements and UI interaction you support today. Is there a wizard teaching your users design patterns of your app (eg. swipe to get to the next step in the wizard for example) and so on... Assumption #1 If you do provide some sort of a wizard ...


1

Yes, there are at least 2 good reasons If you any interactive elements in the body (even an IOS-style ellipsis °°° navigator) it can be confusing to users to "tap on interactive elements, but tap anywhere else to move to the next slide". Users often tap accidentally on mobile devices, so if you decide to do this, make sure you provide a back button of ...


0

I think that any interface with this kind of "circular" navigation is going to be potentially confusing and thus bad. Is it the case that the user could end up in an endless loop of Location 1>Provider 1>Location 1>Provider 1, or something like that? What about using a metaphor of "available" vs. "unavailable"? Think about the way online retailers display ...


0

The fair share of users use assistiveTouch to not have to go to a hardware key for home and have shortcuts at hand. This is persistent in Android too. The soft touch action on a screen vs the hard press of a hardware key offers completely different feel. Hence many users, me included choose to avoid the hardware key altogether. I have shortcuts to power off ...


1

None. Assistive Touch is built so users can drag it to wherever they like on the screen to not interfere with any app. Even if you chose to make your app "support" it, that change would also cause anyone else using the app without assistive touch to suffer. It's not a function that Apple allows you to scan whether it's active or not. Just don't do it.


1

For very long lists, it's better to use a different UX for mobile Multi-select is a complex operation, so it's difficult to use the same interface for both web and mobile. You already recognize this because you've outlined two different layouts. Your mobile design is problematic because: It requires users to tap once to add an item, and then select ...


0

I'd suggest using something similar to the iOS "Select" functionality in Camera Roll. User taps a button to activate a "selection" state. User selects all the items List A items they want to move to List B. User taps a button to move items to List B. I'd also pair this with a search box that allows the user to easily filter out the names they want. That ...


0

So first of all, the "back" button has a specific use within Android UI guidelines: http://developer.android.com/training/implementing-navigation/temporal.html. Second of all (and I would post this in a comment but you need 50 rep to do so), your question is confusing because it's hard to understand the relationship between the As and Bs. Could you update ...


3

First of all - not ABCD... but autocomplete in search (consider Cyrillic, Greek or other alphabets). Drag-n-drop is a beautiful feauter, but consider dragging aprox. 50 elements. I will be extremely time consuming. Clicking on item on the left to assign it to group will be much easier. For mobile my proposition is to switch view between Available <-> ...


1

If we're talking about mobile, maybe override the default web scroll element and implement a scroll with a native-like behaviour and then show a tag list above it. To add something to list B from list A, click on a row in list A. To remove from list B, click on the tag on list B or click again on the row in list A. download bmml source – ...


2

I'm a left hander, and in my opinion the direction of swiping is dictated by text flow, rather than which hand I use. What's more important, is that the most buttons placed conveniently for right handers are difficult to reach with the other hand. Also, I often find that my thumb is covering some content, especially on lists.


3

Some desktop applications do take left/right handedness into account, for example games often use the WASD keys for directional movement, but also have IJKL set up by default. Equally some applications don't take it into account. When I broke my right wrist and had to hold the mouse with my left hand, I soon realised how the keyboard shortcuts for a lot of ...


0

My rule of thumb (which pretty much merges with @DA01's comment), is "Do as much as you can, but don't do more than needed". Maybe, if you wanted to give each platform its different design guidelines to appeal everybody, you could simply make a native app (do as much as you can). They tend to be a better choice for users, rather than accessing a website, ...


1

Forget the "platform wars" and make the application user friendly from a touch perspective. The most important aspect you must try to achieve is to deliver a seamless experience across multiple platforms (make your app look and feel the same as much as you can on all platforms). As I see your application is not a very complicated so that shouldn't be so ...


1

2nd the call for a modal window, not only because it'll be less confusing for the user, but because on mobile it will also be faster & use less system memory. Most mobile browsers deliberately animate new windows in such a way to tell the user "you're no longer browsing that site - you're going somewhere else now, whether you like it or not!" They may ...


2

I would consider a a modal window the better practice. It keeps the user on the same page, it just gives them a quick glance. If a new tab sporadically opens up, they might get confused and try to hit back (Which won't work in a new tab) then get frustrated. I also never liked moving my mouse all the way to the top of the page just for this small ...


4

If I understand you right, this is an app for the teacher, to record attendance of students at each lesson. Put yourself into the teacher's shoes (or better, interview a few teachers) and think about the entire process: What is the teacher's motivation? A requirement by the school? The need to factor attendance into grading? You may identify ...


2

I think your beginning is a good way. I recommend you to read a short introduction into user-centered design. First you need to get your user requirements (who does what and why, what is the environment, life cycle, ...). You started already, but in your post the requirements are too generic, too formal - I guess that humans will using the app? If you have ...


0

Consider the content to be displayed in the app; you're displaying lists. This means that when thinking about navigation, the most natural way to start is by 'listing' your list choices. Your heirarchy is fine, and the tabs are a good starting point in this case. A good convention when designing for tablets is a vertical bar design, like google uses for ...


0

Depends on the Screen Size (or Resolution) Reason for this is a margin for a large screen will look more on a small screen in case when given in pixel. So it's better to decide in scale of percentage. So that it will look appropriate for different screen sizes. ( You will of course give spacing in pixel in each android layout file for different sizes) Is ...


1

We provide retail and stock control systems so accurate capture of barcodes and serial numbers at high speed is important to us. For what its worth, here's what we do, but our target market might be slightly different to yours. Use a barcode scanner. There are bluetooth ones that interface easily to most mobile devices. Of course this costs the end user ...


0

Well, if you can do this using barcode OR manual input, and you say serial numbers are sequential, so both teh barcode AND teh serial numbers will have common characters, you can do something like this: 1- Offer the user to scan the barcode (include some hint message) 1.1 - If user scans barcode 1.1.1 - on success --> stop 1.1.2 - on ...


4

Let's face it, serial numbers weren't meant to be consumed by humans. Can you imagine going to the grocery store and waiting for someone to manually enter each and every bar code number for all your items? In your situation I think option 3 is your best bet but I don't see why you couldn't combine option 3 with option 2. If the bar code scanner is failing ...


0

Here are some of my thoughts on login: Only ask the user to login if its absolutely necessary: With this in mind if the user only needs to be logged in to use 10% of your app make sure they can use the other 90% without being logged in. When your app first launches if the user doesn't need to login to start using it don't ask them to do it or if you do ...



Top 50 recent answers are included