Effective vs. Ineffective Design
My example of effective design is Google’s weather app that shows up as the first result when searching “[city title] weather.” When I frantically search up the weather right before I head to class, this graphic very quickly and efficiently summarizes the information I need to know; I immediately can grasp what the current weather is and how it will change throughout the day. Moreover, even if I search up the weather of a city perhaps for an upcoming trip, I also get access to the next few day’s weather forecast from the start, without clicking a single button. In this sense, the amount of knowledge presented is perfect for what most people search for in a weather report. Moreover, the graphic is very well balanced, with enough spacing between graphics to not confuse daily forecasts with long term forecasts.
To give contrast with my example of good design, I showed this website as an example of ineffective design — the AccuWeather forecast website, which is the first link after the Google weather forecast. Although taking up about the same amount of space (in fact more space when you are on the actual website), the user gets substantially less information: the change of weather throughout the day is not shown, not as many days future forecasts are represented, and much of the screen is filled up with graphics that would not necessarily be useful to the average person looking at weather (for example, most people wouldn’t necessarily care that the wind is facing East). Moreover, the general graphic seems to be lacking overall unity which the Google weather app seemed to have more of — the tabs are not well centered, the color schemes are not really kept consistent, and the breakdowns between tabs seem to be a little random.