Tag Info

Hot answers tagged

6

To avoid ambiguity I would go for something like this: The benefits of doing this is that the user is given a clear message that something is going on and more importantly that they should not leave the current page until it has finished. Maybe even give a lighter green for the "not yet completed" portion of the bar.


5

No, it's not always necessary. System-defined screens are not obligatory, and there is no need to reproduce clone pages/elements with minor changes. Alternatives to hi-fi prototypes are lo-fi wireframes, user journey maps, PRDs. Yes, paper sketches/prototypes are legitimate prototypes if they are detailed enough and capture/highlight on all important parts. ...


2

You're right that one practice might not suit every single company. What's more, it might even differ from dev to dev. The simplest way you can go is just ask the devs what's their preferred way of working. Some people hate having someone else looking at their screens, while others may have lots of questions and would rather have you around. It varies from ...


2

Regarding "Perceived Speed" - research shows that you should never start a progress bar at zero regardless of how long a process will take to complete. Edit: this research is actually talking about a different use case, however, I noticed that Apple always starts their generic progress bar with a little bit filled in so I'd say it applies in this case as ...


2

In fact, this should be written in your agreement, where you agree to provide the system design services and they agree to get you info that you require. When it comes to UX or UCD (user-centered design), requirements, including TA description, PRD and use cases are the most crucial info you can get from your employer/client. That would be the first thing ...


1

Well, I can't comment on the perceived speed/performance part because you can make it as fast and smooth by just playing with the animation. Beauty is subjective, so I can't really comment on that. The only thing I can note is this, the distraction levels are quite high when the button suddenly turns into a circular loader. This issue can be resolved by ...


1

This sounds extremely frustrating and a very old-school way of developing. Bringing in agile methodologies might just save you and your sanity. Start by working with the client about what features they want developed. This needs to include all dependencies and acceptance criteria - documented! All stakeholders (Marketing etc. ) need to sign-off these ...



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