You can download Google Chrome at google.com/chrome.

Some of the neat features include:

• one bar for searching AND typing in urls,
• a very skinny tab and title bar combination,
• a set of commonly used pages immediately viewable when you open a new tab,
• independently-run tabs…that is, there’s no way for one tab to crash the entire browser,
• Google’s new V8 JavaScript engine,
• and use of WebKit to render webpages.

Here’s a quick picture in case you’re a little interested, but not interested enough to install it.

Google Chrome

IE8 Compatibility View Button

It’s interesting to note that  when it comes to Intranets, IE8 defaults to this compatibility setting.

Compatibility View Settings

One assumes Microsoft’s reasoning behind this is that they believe that the typical Intranets are not usually known as bastions of standards-based web design, and tend to be given the lowest priority in an organization. Has anyone ever worked at a place where you had full Intranet functionality on a non-IE browser? There must be some out there. I know that there are some state colleges in Florida that have banned IE from the workplace - I wonder what their Intranets look like?

In their analysis, Sohn et al dissected 421 information needs and analyzed the heck out of them. But the most interesting findings are probably just the information needs themselves. They placed each need into one of 16 categories. The following categories occurred most frequently:

1. Trivia (e.g. How did Bob Marley die?) : 18.5%
2. Directions to a known destination: 13.3%
3. Directions to a Point of Interest (destination unknown): 12.4%
4. Friend information: 7.6%
5. Shopping: 7.1%

Of course, you can make the common academic comment that people would make about these types of studies, which is:

“But people only think of these information needs because it’s the type of information that’s actually available on the web…if their minds were open to reporting any information need, we’d probably see a lot more variation or a lot more needs over a period of two weeks from 20 people.”

After reading the article, though, I can tell you that these researchers did a lot to try and not bias the results. I’ll let you read about their methods in the article though (linked below).

At any rate, the raw categorical data does shed some light on how you can design a site’s mobile profile to better address mobile users. For example, if you’re designing a site for a floral shop, you may want to make directions and pricing information more prominent in the mobile profile than in the large screen profile. The directions section would ideally ask someone to type in their “from” address, and submit the form to take them to a mapping service with directions to your store. The pricing section might have three elements:

• a search box at the top for quick flower or arrangement lookups,
• a list of 3 to 5 of the most popular flower arrangements or flowers,
• and perhaps a one-click reservation button that allows users to reserve a flower by entering their name and date. (I can think of several friends whose anniversaries would be saved by such a feature)

Their study goes into a lot more detail about the reasons people do or don’t address their information needs while mobile, but I found those conclusions didn’t help as much as understanding the type of information users need in the first place. If you want to read more about the study, you can download it at Tim Sohn’s page at the University of California, San Diego.

Please, let me know if this type of post jives with the rest of the site and Refresh Tallahassee’s goals. If not, I could always find something else that’s closer to our mission.

Cheers!

References

Sohn, T. et al (2008).A diary study of mobile information needs. Conference on Human Factors in Computing Systems, 433-442.

After seven years, IDEO launches a new design. Thoughts?

CSS Inspiration (25.8MB)