Tag Info

New answers tagged

0

I would make it fully in-line, both before and during the edit. Pros: Speaks for itself. Saves space. User do not loose context (like with modal dialog) download bmml source – Wireframes created with Balsamiq Mockups


0

You want the user to make 1 task (to add a column) so I woulnd't "disperse" too much the actions needed to finish that task. I'd take the same approach as KanbanFlow: 1) "Add Column" button. 2) Modal with Column name Input + Position to be inserted. This way the user doesn't have to look for the column to change it's value + they know exactly where ...


1

While my spanish is a bit rusty ;-) below are some recommendations to improve UX after a brief look at your question and image: Keep the order breakdown list 'in-line' (i.e. when clicking on a specific order, the (item) breakdown will open under the order) so the eyes and mouse/hands do not need to move all over the screen. Keeping the order breakdown ...


1

In general, it's not extremely bad, but I think the problem comes from your own choice of wording, which in terms makes everything more confusing. First, what do "open" and "closed" mean? As an user, I really have no idea what you mean. I assume the English language has been added specifically for this question (if not, get rid of it immediately!) but ...


0

It sounds like you're talking about release notes. Not the customer facing type, the internal type that spells out all the nitty gritty details. You document what changed at a place in time, then come back and annotate with the results you're tracking. There's the fixed part of the doc that says what you did and the living part that says what happened. ...


0

Given scope of question the following heuristics may be useful, indeed some may have already been applied Education of BI domain? most UI's are representing a domain model or world view that a user is familiar with. This makes learning curve low, and thus a good UX. So UI's do need to educate user on a new domain, or details of a domain (for example ...


1

You can add a new column on to the end of this: download bmml source – Wireframes created with Balsamiq Mockups ... wherever the end of those columns are. The user can then try to click that save button squished inside the column header. Or add a column on to this: download bmml source


0

From the two option i like option 1 Will this help to enhance option 1. How about you drop the "Save" button and just keep the edit box and let the user key in the column name and on (focus) change the save happens. If the user wants to edit the column again he or she can click on the edit box again. You can use simple CSS tricks for micro interactions ...


0

If you have some common motives to why a user would flag content, you could use the flag button as a popover/drop-down where the user can select one of the common motives or explain it him self. This dribbble shot is a good illustration of what I mean. Regarding how the user explains the flagging him self - I don't see why you couldn't use a pop-up both on ...


0

I would make the flag explanation field optional. And the flow would be like this. Flag click/tap > Want to explain why? [Just flag] [Explain] [Undo flag] If the users decide to explain why they are flagging a course, then you take them to the new page where they can fill up the flag explanation.



Top 50 recent answers are included