google

You are currently browsing articles tagged google.

So I’m pretty close to never opening any Microsoft Office apps. I’ve moved completely from Entourage to Gmail and Gcal. All of my presentations are done in Google Presentation, the vast majority of my spreadsheets in Google Spreadsheet, and, naturally, my documents are written in Google Document.

With the awesome Manymoon providing a seamless layer of organization to all of these Google apps (as well as being a kick ass product management app), I really don’t miss MS Office at all.

Except for a few minor annoyances, there’s really no reason to open Office. One such annoyance was the inability to change the standard size, color and font choices for the Headings. This irked me, because the supplied heading qualities really look sort of terrible in the context of most docs; too big, too bold, too much deviation between the point sizes from Header 1 (VERY big) to Header 2, (not proportionally big), and so forth.

Here’s a screen grab of the standard headers:

As you can see, Header 4 – at 10pt type – is a smaller point size than typical 12 point body text type. This means it looks terrible.

Happily, Google recently made it easy to alter the CSS of the doc. Go to Edit > Edit CSS, and you’re greeted with a blank screen where you can add any CSS elements you want.

To change the Heading Styles, I added this:

h1
{ font-family: Calibri;
font-size: 16pt;
color: #336699; }

h2
{ font-family: Calibri;
font-size: 15pt;
color: #336699; }

h3
{ font-family: Calibri;
font-size: 14pt;
color: #336699; }

h4
{ font-family: Calibri;
font-size: 13pt;
color: #336699; }

Now the headers look like this:

It’s obviously very easy to change the elements for Headers (or anything else). Do note that all you’re doing is changing the CSS for the document you’re actively working on, and not globally. I have a feeling that option will show up soon.

Another steak in the heart of MSFT.

Tags: , , ,

My post on the Coder/Manager dilemma got me thinking about the unintended consequences of feature additions to products (specifically web-based, but not exclusively). I’ve come up with a theorem that is very much a work in progress.

I hereby thus propose “George’s Law of the Inverse Relationship between Features and User Friendliness.” For every added feature above base functionality, user friendliness is reduced by .075 of the existent base unit total for user friendliness.

Let U = user-friendliness. Let F = features.

So, if we assume (for easy math), a base of 10; that is, you have a site/UI where the features (F) = 10 and the user friendliness (U) = 10, and you add a new feature, your features = 11, but your user friendliness = 9.25; another feature added: F = 12; U = 8.55. And so on.

Don’t get me wrong, new features are crucial, and can increase user friendliness, but only if the new feature(s) replace(s) an older feature. In this manner, your feature list doesn’t grow, and thus your user friendliness is not reduced.

The best example I can give of this doesn’t come from the web world. Rather, it’s the Flip Video Camera.

This camera strips away all the features that 99.9% of the video camera owners never use anyway, and takes a dead-simple approach. Customers love it. The NYT calls it “One of the most significant electronic products of the year.” It’s wildly successful. It succeeded because it focused on what the customers really wanted/needed, and worked to give those features to them in the best way possible. Axiomatically, the only way you can give these customers their most cared-about features in the best way possible is to eliminate ALL of the features they don’t care about. Flip’s challenge moving forward is to innovate, and, yes, add features without screwing up what makes their offering so great. This will mean not only adding features, but also subtracting older ones that are no longer relevant.

Want a web example?

Tags: , , ,

TechCrunch’s Michael Arrington discusses and disses on Yahoo/Google:

Tags: , , , ,

Nicholas Jitkoff, The developer of my all-time favorite app, Quicksilver, works at Google (big surprise, huh). He offers up a good introduction on QS in this Tech Talk.

Check it out:

Tags: , , , ,

Bad Behavior has blocked 1130 access attempts in the last 7 days.