But I suppose it has to be balanced with not getting in the way (as a distraction) of the next task because some users may not care to follow up on the change with visual confirmation of success or failure.And yes, I read the following, it just didn't supply a strong gorund IMO: I also agree with the concept behind making the YFT last a little longer, especially if the user has to react to the page reloading, then scroll to the point on the page where the changes were made they might miss it. And that's always a good thing (probably:).
But the good thing about YFT is that it does seem (I say "seem" since I haven't seen it tested) to be a design solution to help alleviate the mental load on the user.
It's all how you define "problem." Was it a usability problem that people couldn't remember what change they made just 5 seconds ago? As usual it depends. I saw it in action and immediately understood what it signified (newly updated content).but I never really viewed that as a problem previous. The YFT makes it super easy to spot edits/changes yet its unobtrusive nature lets people quickly get back to work once a modification is confirmed. Then, in a second or two, the highlight fades and the page reverts to its normal state.
The YFT uses JavaScript to create a yellow highlight that briefly spotlights the change when the page reloads. The problem is once the page reloads it’s often difficult to spot and confirm the change (especially if the change occurred somewhere in the middle of the page). Why does this matter? When you edit or move something on a web page it usually forces a reload of that page. It’s a nifty way to subtly spotlight a recently changed area on a page. That’s why we’ve pioneered the Yellow Fade Technique (YFT) inīasecamp. “Because something is happening here / But you don’t know what it is / Do you, Mister Jones?” -Ī lot of web sites & applications make you feel a bit like Mr. Web Interface Design Tip: The Yellow Fade Technique by Matthew Linderman
0 kommentar(er)
