- Paperback: 224 pages
- Publisher: Addison-Wesley Professional; 1 edition (May 9, 2008)
- Language: English
- ISBN-10: 0321509188
- ISBN-13: 978-0321509185
- Product Dimensions: 7 x 0.6 x 9 inches
- Shipping Weight: 15.5 ounces (View shipping rates and policies)
- Average Customer Review: 5 customer reviews
- Amazon Best Sellers Rank: #1,804,147 in Books (See Top 100 in Books)
Enter your mobile number or email address below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
To get the free app, enter your mobile phone number.
Designing and Engineering Time: The Psychology of Time Perception in Software 1st Edition
Use the Amazon App to scan ISBNs and compare prices.
Fulfillment by Amazon (FBA) is a service we offer sellers that lets them store their products in Amazon's fulfillment centers, and we directly pack, ship, and provide customer service for these products. Something we hope you'll especially enjoy: FBA items qualify for FREE Shipping and Amazon Prime.
If you're a seller, Fulfillment by Amazon can help you increase your sales. We invite you to learn more about Fulfillment by Amazon .
"Warlight" by Michael Ondaatje
A dramatic coming-of-age story set in the decade after World War II, "Warlight" is the mesmerizing new novel from the best-selling author of "The English Patient." Learn more
Customers who viewed this item also viewed
From the Back Cover
Build Applications, Websites, and Software Solutions that Feel Faster, More Efficient, and More Considerate of Users' Time! One hidden factor powerfully influences the way users react to your software, hardware, User Interfaces (UI), or web applications: how those systems utilize users' "time." Now, drawing on the nearly 40 years of human computer interaction research-including his own pioneering work-Dr. Steven Seow presents state-of-the-art best practices for reflecting users' subjective perceptions of time in your applications and hardware. Seow begins by introducing a simple model that explains how users perceive and expend time as they interact with technology. He offers specific guidance and recommendations related to several key aspects of time and timing-including user tolerance, system responsiveness, progress indicators, completion time estimates, and more. Finally, he brings together proven techniques for impacting users' perception of time drawn from multiple disciplines and industries, ranging from psychology to retail, animal research to entertainment. - Discover how time and timing powerfully impact user perception, emotions, and behavior - Systematically make your applications more considerate of users' time - Avoid common mistakes that consistently frustrate or infuriate users - Manage user perceptions and tolerance, and build systems that are perceived as faster - Optimize "flow" to make users feel more productive, empowered, and creative - Make reasonable and informed tradeoffs that maximize limited development resources - Learn how to test usability issues related to time-including actual vs. perceived task duration "Designing and Engineering Time "is for every technology developer, designer, engineer, architect, usability specialist, manager, and marketer. Using its insights and techniques, technical and non-technical professionals can work together to build systems and applications that provide far more value-"and create much happier users." Steven C. Seow has a unique combination of experience in both experimental psychology and software usability. He joined Microsoft as a User Researcher after completing his Ph.D. in Experimental Psychology at Brown University with a research focus on human timing and information theory models of human performance. Seow holds Bachelor's and Master's Degrees in Forensic Psychology from John Jay College of Criminal Justice, and wrote his master's thesis on distortions in time perception. For more information about Steven Seow and his research, visit his website at www.StevenSeow.com. informit.com/aw
About the Author
Steven C. Seow joined Microsoft as a User Researcher after completing his Ph.D. in Experimental Psychology at Brown University with a research focus on human timing. Prior to Brown, the Singapore native completed his Bachelor’s and Master’s degrees in Forensic Psychology at John Jay College of Criminal Justice with a thesis examining the distortion of time perception. Steven constantly confers with colleagues across his company to talk about time and timing issues. Coupled with his scholarly interest in psychology is his passion for computer technology. In his spare time, Steven enjoys tinkering with computer hardware, dabbling with programming languages, and building websites. He lives in Maple Valley,Washington, with his wife and son.
For more information about Steven, visit his website at www.StevenSeow.com.
Top customer reviews
There was a problem filtering reviews right now. Please try again later.
While there is no one uniform definition of what is "good performance", an application that is designed to interface with the user - that is, accept input, and provide feedback - has well defined physiological and psychological constraints: maximum and minimum response times for instant feedback, types of progress notifications and when each should be used, and much more. The critical point to highlight is that great experiences can be engineered: it is not just the raw speed of execution, but how the user perceives the speed of the application. There is big difference between the two!
Great read for anyone who cares about delivering the best experience to the user: short and simple chapters, lots of great citations for further research. I'm surprised this book has so few reviews.
I probably found two or three concepts interesting throughout the book. In general I think it already states the obvious, uses too much comparisons and has too much images (just for the sake of it - without adding value). A MSDN article with say, 20 pages, would have been more than enough instead of a 191 p book. I expected to get some examples from real life software and to get more insight in software and how to handle time.
After reading the book I wanted to get the sense of "Hey! We can do even better software, now let's go and do it!" But instead the book left me feeling like I had wasted my time reading it from cover to cover.
When reading Designing and Enginering Time I though that it appears to be a report from a student, like a master thesis report. When discussing the book with a colleague in the book club he said the exact same thing!
The last two chapters was ok but it is still a "Don't like it" from me.
Why the four stars? IMHO $30 seems expensive for what might've been a great MSDN article.