Tag Info

Hot answers tagged

12

It is generally accepted (and well proven) that shorter forms are completed more often than longer forms (with all else benig equal of course). However there are exceptions where some information is expected by customers, and leaving it out leads them to question the validity of the form. 'Shorter = better' is a good starting hypothesis, but one that you ...


7

I think it mimics iOS UI style (at least I don't remember such a component before iOS, please correct me if you have some other information): source It is UITableView with style Grouped. Or you can call it "text field group".


6

They could be referred to as Grouped Form Fields. It is partly a design trend. I think most people would argue that while it may be visually pleasing, it is not great from a usability standpoint. You could closely group fields without needing to combine them in that way. For example, someone may not realize that they need to tap again to type in a second ...


4

Consider: Start: Mon 9/1/2014, 8PM Ends: Tue 9/2/2014, 12AM (28 hours long) Although not directly in your question, be prepare for 12AM to confuse users - is it midnight or midday (the former is the convention, but many people don't know this). By the way, if your event is never more than 6 hours long consider: Start: Mon 9/1/2014, 8PM Length: 4 ...


4

If you don't need the information (e.g. the emergency contact details) then why collect it? Every extra field on a form increases the burden on the form-filler (they have to at least scan it to see what it is), increases the chance of error (as mentioned on UXMovement) and reduces conversion (as JohnGB refers). As it is, I would suspect that significant ...


3

I would recommend determining the key fields which would have to visible at all times keep this in a separate section. The remaining fields can be shown using an accordion which may be viewed as the user needs to. This would allow the user to jump to any section at any time and expand and collapse the content and edit it as he needs by providing him the ...


2

As the above answer mentioned, if you don't need it why you collect it? And I want to expand on that can try to give you a better solution. Most of the time, you need those optional information because the user might need to use some optional features that would require those optional info. So the question is not "do you need the optional info," but rather, ...


2

First of all is there an need for you to show the unfilled fields in your view mode since the user cannot technically fill the details there. I would recommmmend going with either of these approaches : Dont show the unfilled fields if the user has no use for them - For example you might be filling out the address details and you might have a field company ...


2

I expect to see a specific start date and time and a specific end date and time. Leaving all guesswork out of the equation. Example Start: 13th June 2013 at 20:00 hrs End: 14th June 2013 at 09:00 hrs. Duration: 13 hrs. I previously ran a nightlife orientated social network and events could be nightclub events, after-parties, festivals for example, all ...


1

I fly accross the Atlantic quite often, and I always get the (+1) after the date added to inform me I land the next day. I don't even see it anymore as an actual statement saying "Add one day" but just as a reminder that I land the next day. I expect that to happen every now and then so I am prepared for this. For events like you describe I think people ...


1

First of all I would suggest to be very careful with assumptions. According to my experience it is not so hard to develop a good and handy table/tree-table customization approach, but users tend to ignore that anyway. I've solved this issue by providing a predefined set (a library) of columns with the ability to switch between libraries in real-time. 9 of ...


1

You are really faced with two problems in these situations. The first is with usability, and the second is with business. If the information you are collecting has no business value, then you can get rid of it and "maximise" usability. Otherwise, you need to think again. I think the real problem comes with the traditional notion that most of us have about ...


1

Should there be seperate interfaces for editing public and private fields? No, I like the approach of having an explanation under. Perhaps you could steal the icons from facebook (eg, globe from facebook), but a hover for that icon wouldn't be that effective. Perhaps hover for the field (but hover, not focus). So, private fields with different ...


1

Two places you can improve on. 1. Microcopy: Izhaki's comments are spot on. I'll add to them. I don't know about public and private. They can mean different things on the web. How about Visible and Hidden or Visible Fields, Hidden Fields or Active and Disabled? Display on Leaderboard/Remove from Leaderboard. (replace Leaderboard with what you are showing ...


1

I have a few comments on your ideas: 'Save Fields' is not a great name, I think 'Save Changes' or 'Commit Changes' is better. If the user drags a field to the deleted bin, 'save Fields' doesn't make much sense (are you saving the fields that are to be deleted - eah?). The 'Deleted' bin is in no way showing deleted fields. If anything, it shows the 'To be ...


1

Here are couple of ideas, some of which you may have already. I would probably place Edit at the top since if it is at the bottom of the page and there are a lot of fields, it will be below the fold (users may not see it) and even if the users know it is there they will have to scroll. I think it is a good idea to display read only view with data if the main ...



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