Tag Info

New answers tagged

0

To answer your question, UX is not all about making a mockup. UI is what you see in the app/website and UX is what you feel when you are using it.UI play a role in the way you feel about the app.A mockup define the way UI looks. This is just a part of UX.


1

What you describe is more like the user interface. The mockups and the motion the flow etc... are the result of how you are going to communicate the desired user experience. User Experience is what emotions, what state of mind or usability you want to achieve for the user that will interact with your website/app or whatever you design. So the person who is ...


1

If the type of some fields depends on previous choices/answers you can populate the form accordingly (= based on previous choices) using a framework like jQuery of plain old JavaScript. But if I understand it correctly the only elements in the form are 20 fields? If so, you could try grouping similar fields and use -for example- collapsible divs? So users ...


3

Seeing you are already using categories, and what I understand is you don't want to have scrolling inside your popup? If your user does not need to see all the information filled into your form, depending on the process I see two options where the form fields are divided into smaller blocks (for example your categories?), tabs or wizard style process. Many ...


2

What platform would this be in? For mobile devices? For desktops? If it is just for desktops, a box with a scroll-able region should suffice. Or if there are so many fields, then it probably deserves its own page. For mobile devices, I think it would be preferable to group the fields into logical categories and separate them into pages For example, a user ...


3

The problem seems to be related to the (third form of) database normalisation. Each rerasonably disjunct set of data (like information about a book) should/could be editable on its own without the user's need to touch any other set of data (like the author page) In general you want to decide what information belong together and make it visible to the user ...


0

There’s been a centuries-long tradition of proofreader’s marks. They’re not universal, tough, with several standards having emerged (ISO 5776, BS 5261, DIN 16511 etc.). Teachers, perhaps without knowing it, often employ a subset of their local standard when picking up their red pen. This includes for a good part the intuitive symbols that partially are also ...


1

Why not embed the prerequisites into the modules themselves? That way you can see all prerequisites at one place. No lines to other places, no other place to look up associations. I added one possible draft using a drop-down box for addding prereqs and an X button which will remove it again. Depending on further factors (size of list, knowledge about ...


0

I have also participated in a project involving large amount of data input on multiple types of devices. And our solution is using Responsive Web Design, so users can choose to input data on mobile, tablet or desktop, through accessing the same URL. Also one thing we found is that although mobile devices are relatively small, users under certain ...


1

Design for people not device. You might prototype a few scenarios that involve mobile + desktop pairing. Wearable UXD is a good example of this paradigm. Generally desktops are better for data entry. While mobile has the benefit of being always on the user. Take something like Fitbit for example. The device is optimized for collecting data in an ...


3

Web or Mobile? This sounds like a really useful native mobile application as I'm guessing it will be notification-centric that will alert the user when action is required. Things to consider before diving into native mobile development: Will this be OS-agnostic (i.e. will it run on iOS, Android, and possibly even Windows devices) Will it be a universal ...


1

I recommend that 'Cancel' should be removed and retain the "Back to..." link. Currently, initiating either the "Cancel" and "Back To..." actions invoke the same abandonment of the use case of making updates to this user profile. The only difference is that the "Back To.." link is more explicit in where the user will be taken compared to the "Cancel" button. ...


1

The answer to this is going to heavily depend on the transition between the list and the details view. For example, if the details view slides in (not a hard refresh), then it makes more sense for the buttons to be "Save" and "<- Back", indicating that it moves you back to the list view. If the details view appears above the list view, then "Save" and ...


0

Think of it as if you have a list of values and you wish to segregate them into different buckets depending upon some condition. You can then have a table of all these values with the four buckets right below it as shown in the picture below: This layout will also prove to be useful when you try to make your design responsive for tablets. You can keep ...


0

Personally I would go for an Office style approach / Career style approach - as the majority of people would understand this. You start at the bottom of the ladder and have to work your way up - getting benefits etc as you go along. I got the idea from the TV series SUITS a little - I have to admit. You start off at the ground floor and have work your way up ...


1

Designing in an enterprise setting, we frequently distinguish between "Administrators" and "Business Users", the latter meaning users who do not change system settings, but rather pursue business goals with the help of the system. Needless to say, Administrators are Users as well, and usually we talk not of Business Users (because the category often is too ...


-2

I'am using 'public' as a namespace for non-logged-in users.


1

In most cases one cannot integrate all administration controls with end-user view. Things which definitely must have their own view to be managed are actions and settings respecting whole site. We can however integrate actions and settings respecting objects (eg. articles) on their end-user "read-only" view. Object view Generally such integration is ...


1

Buttons initiate a process: Submit, Cancel, Save, etc. Submit buttons can be used by the keyboard to interact with a server, mapped to the Enter/Return key. Links are anchors that connect one HTML document to another. This is a subtle but important distinction. If hitting the button does not save (Post) a current new item (like Save & Continue) then I ...



Top 50 recent answers are included