Map This is a FireFox add-on that allows the user to quickly send an address from a Web page to Google Maps. After being installed, Map This adds a menu item to the FireFox context menu. When the user selects an address then right clicks and selects "Map This," the feature passes the address to Google Maps and opens a new window.

This is a pretty simple little feature, but because of it's narrow focus it is able to do something quite powerful. It is acknowledges a specific type of data on a Web page, an address, and allows the user to perform an action on that data in a way that intelligently matches matches the data type. Actually, I give the widget too much credit. It cannot tell the difference between an address and any other selected string of text. However, the concept of the widget is moving in the right direction.

I wrote about a similar convenience widget, the Skype Toolbar, that detects phone numbers on a Web page and allows the user to initiate Skype calls from the context menu. Again, the feature understands the context of the text string and provides actions that suit the data type.

From a conceptual view, very compelling interactions could be created if the browser understood different types of data and was able to provide actions to match the context. For example the browser might recognize a string of selected text as an address, a person's name, or a song title and allow the user to act on that data in context. If the user highlighted a classified ad, the browser could understand that the user might want to save the ad, respond to it, print it, compare it to similar ads, etc.

There are many identifiers used by the browser to create awareness of data type, but none, to the best of my knowledge, are used to identify how textual data could be employed in a useful way. Web 2.0 style tags offer a classification system which is useful for searching and grouping similar types of data. However, tags do not have an awareness of the user's context. The HTML OBJECT tag allows the browser to acknowledge data types like movie or audio files but not the semantics of a string of text.

To get at the user's context and offer functionality to match, the meaning of text strings will have to be understood on a programmatic level by the browser, an add-on, or the Web site which contains the text.

Labels: ,

posted by Shawn Elson on Saturday, April 21, 2007

0 Comments


Share/Save/Bookmark



There are several small browser widgets I have been using recently that have made my life seem so much easier. I call them "convenience widgets" because they are small, lightweight, and make very specific cumbersome tasks much simpler.

I have started using Skype Out quite a bit this last year. This is a service from Skype that allows the customer to call any landline or cellphone from a computer. I paid $15 for a year of unlimited calls (seems like a great deal to me).

When making calls to businesses using Skype Out, my typical task flow is this:

1. search for a company's Web site on Google
2. open the site
3. click their "Contact" link
4. highlight the phone number
5. right click to copy the phone number
6. open Skype
7. paste in the phone number
8. initiate the call

It's a lot of steps for a pretty simple task. In particular, switching from the browser to Skype is a mode shift I do not like because it takes me away from the browser.

Last week I installed the Skype Web Toolbar. This toolbar highlights every phone number on a Web page. In addition, it adds a context menu to each phone number from which the user can quickly initiate a Skype Out call. This tool reduces the task flow to:

1. search for a company's Web site on Google
2. open the site
3. click their "Contact" link
4. initiate a call from the context menu

This is a big time saver and also it keeps the user from having to interact directly with the Skype application.

One problem with this design is that by highlighting phone numbers, the Skype toolbar alters the visual look of Web pages. An alternative would be to not highlight the phone numbers but add the Skype commands to the browser's context menu when a phone number is right clicked. The benefit would be that the page's visual design would not be interfered with. The tradeoff would be that this interaction would be less discoverable for users.

Taking the concept further, wireless companies could offer the same kind of interaction. When a phone number is seen on a Web page on the computer, the computer could initiate a call on the cellphone via Bluetooth. Any form of information could be added to the cellphone from the Web browser with a simple contextual menu: maps, calendar items, pictures, etc. This type of data sharing functionality would make for a pretty useful application.

Labels: ,

posted by Shawn Elson on Wednesday, February 07, 2007

1 Comments


Share/Save/Bookmark