Week 8 reading

In chapter 12 the author gives a detail explanations of not asking the users too much information, especially personal data, just get what you really need for the task. If one force the users to give out a lot of information, it is what might happen: they will give out fake information; you will get fewer complete information in return; and more importantly, it made you look bad. Instead, what one ought to do is to: only make the users provide what you really need to use; do not give out too many options; and show the users something in exchange for what they gave out.

 Over whelming graphics and sound effect site does not work well on any kind of websites, except entertainment sites, pure branding sites, and portfolio sites for web developers. Other than those on the list, sizzle effects, crazy graphics would not work do well on the other sites. It is more important in terms of function that “looking good” on a site sometimes when it is for people to get things done on there. If a site contains sizzle graphics and it takes a long time to load up, it will probably not provide an excellent experience to the users.

The author however, is not asking us never to do those things when we practice. It is to depend on what we are working on, when we are sure of what we are doing and always test it before it launches.

I enjoy reading the letters of this chapter since I can certainly learn a lot from the author. It is also helpful to imagine yourself using the site when you build it, how would you feel if that problem occurs to you. It is also vital to get feedback form everyone else because sometimes you would get lost in your own work. 


* Selling the steak, not the sizzle
* How much information is reasonable?
* Do not ask for too much sign up data
* How much information should you ask?