Google Search: Bottom's Up

(first published Nov 11, 2008 in The Freewheeler blog)

I suggest Google put its Page of Results navigation (as seen here)

At both the TOP and the BOTTOM of each result page. Google tends to put such navigation only on the bottom. For example, I was in Google Calendar and chose to view calendar details/settings. Within the setting page, I couldn't find a way to exit -- and return to the calendar. The link "Return to Calendar" is at the bottom.

It would be convenient to have the option of jumping through results pages without having to scroll through each page. It would also give the results pages more consistency:

The text input field resides at both the top and the bottom. Actually, different versions of the search input appear in the top versus the bottom.

The top just has the simple search input field:

The bottom has search tips, filtering options and language tools:

Another issue, which I discussed in an earlier post, is the ambiguity of what the links "Web" "Images" "Maps" do. Are they links to other Google products/services (nouns), or search result filters (i.e. "show me results within Images."). If you experiment, you will find inconsistent results. For example, if I click "Gmail" it doesn't search my gmail for "gold" (search term), but if I click "Maps" it does. And how does the set of links above the Google logo differ from the set of links below the logo?

Trader Joes Checkout Line

Trader Joes is an awesome store for many reasons. One of them is the way checkout is handled. The clerk takes your cart and empties it for you. That makes sense, and it removes that awkward discomfort of positioning yourself behind or in front of your cart as you strain to remove the objects. That's how it's done at "legacy" super markets. Most of the major chains have remodeled their stores over the past 5 years.

Many of these stores are very pleasant places... and yet the checkout lines remain narrow passageways where the shopper is left to remove the items and place onto the conveyor belt. It's got to change. Thanks, Trader Joes, for showing the way. And also, for those 3 sample coffees I had last week.

Google Calendar: Time Zone Snag - No Absolute Time

(first published Feb 14, 2009 in The Freewheeler blog)

Google Calendar is terrific. But a major problem I've found is a Time Zone is set not to the Event, but to the Google Calendar User. Thus, any event that user creates, is set to his user setting timezone.



So, if I live in Los Angeles but schedule an 8pm Monday London event, it will show up as a 3am Tuesday event to Londoners. As long as my user setting is PST, I have to do this: set the event for 1pm. In Google Calendar, a user can have more than one calendar. Each calendar can have its own setting for Time Zone.

Thus, I thought a bad but working solution would be to temporarily set a calendar to time zone London. But, that setting just dictates the Display of the time, not the absolute date time start. The absolute is still based on the user's time zone.



The issue is all the more confounding because the Calendar gives much weight to an Event's Location field. It wants specific information so that it can map it and offer directions or other services. Yet it's not interested in the time?

Here I create a 9am New York City event. But to Google, it's a 9 am PST start -- 12 pm in NYC and 5pm in London.


Here's how it's published, in London Time:

The solution is: Google should let viewers / subscribers to a calendar set a timezone for "Viewing"-- thus all events are translated into a time relative to that user's view. In that case, if I'm looking at a 5pm New York event as a Californian (PST) I see it as 2pm.

The absolute time should be defined by the manager per event. When entering the time there should simply be a field to enter the time zone, which Google could 'predict' once location is entered (that would also require an alteration in the Form inputs so that Location is entered before Time).

Suggested:

As it is, Google Calendar cannot be accurately deployed by a manager of an entity that crosses time zones (sports teams, performers) or has subscribers across multiple time zones.

Oh Google! Yours is such an awesome, awesome company, and yet snags like these make me think you might spend just a wee bit too much time drinking your own Kool-Aid and not actually engineering for humans.

Phamper Presents a Magic Trick

My pal Bill Chott told me a version of this trick, and I've used it to explain some basics about data and how I--as Phamper--can figure out a situation. * Flash required

Partial Fix: Myspace Friends Categorizing

Myspace is now letting its users place their friends into categories that they create. That's a big improvement. I lamented last year (see post) about Myspace only allowing its users to place themselves in one category (Musician, Comic, Regular Person), and disallowing any labeling of a user's friends.

My suggestion was:
1. let users label their personal profile(s), and to also label their external profiles (friends) WITH MANY keywords.
2. Allow users to Sort their Friends based on the Labels.
3. Allow users to make Lists/Groups, a feature presently available in YouTube.

Myspace's recent change is an improvement. But, it still limits a user to categorize himself into a single, pre-defined Category. And it only allows you to place a friend into a single category.

The Myspace system apparently has trouble with such cutting-edge database structures as "many-many" relationships.

Even as it now is, though, it could greatly help a user navigate his list of profiles. At the least, she could have a Category: "Added for Quantity" and "Added for Quality (actual friend)."

New users will find this feature handy. But will legacy users, with thousands of friends, categorize all the existing friends? Only if it was Easy to do, or the user was aware of an Incentive.... Alas, and this comes as no surprise if you know Myspace, it is TEDIOUS AND TIME-CONSUMING to categorize existing friends... The user has to do it ONE AT A TIME!

Myspace's failure to recognize the value of multiplicity has failed it again.