How We Developed Google’s Search Options Panel
Posted on : 21-11-2009 | By : JortK | In : Movies, google
0
Youtube Direct Screencast
Posted on : 21-11-2009 | By : JortK | In : Movies, google
0
Webinar: Introducing Google Chrome OS
Posted on : 21-11-2009 | By : JortK | In : Movies, google
0
How to use Google Website Optimizer
Posted on : 20-11-2009 | By : JortK | In : google
0
Why would an FAQ page rank above a site’s homepage?
Posted on : 20-11-2009 | By : JortK | In : google, seo
0
Webinar: Google Chrome OS demonstration
Posted on : 20-11-2009 | By : JortK | In : Movies, google
0
Does Batman uses Google?
Posted on : 20-11-2009 | By : JortK | In : google
0
When I first started at Google, Craig Nevill-Manning, engineering director here in New York, said to me: “The Google homepage doesn’t belong to us. It belongs to the millions of people who use it.” Besides the fact that Craig can make one of those insanely cool leaf patterns in his latte, I find the simple truth of his statement inspiring. I often refer to it as a guidepost for our work.
So when we got together with the search team to brainstorm ways to talk about our latest innovations (like music in search results), we decided to feature them through stories inspired by our users. Because while we’re proud of the innovations we’re making in search, we’re proudest of the things people use search to accomplish. In other words, the best search results don’t show up on a webpage — they show up in somebody’s life.
So in that spirit, we made a bunch of videos. There’s one about grandma dipping her toe into technology. One about friends taking a Kerouac inspired road trip. And yes, there’s even one about Bruce Wayne.
Here’s the first one:
You can see them all here.
As they say in the movies, all the characters in these videos are fictional, any resemblance to persons alive or dead are purely coincidental.
We hope you enjoy them.
New Google Analytics feature: Analytics Intelligence
Posted on : 20-11-2009 | By : JortK | In : google
0
How would you like to have 24-hour a day access to a dedicated assistant who is focused exclusively on your site’s analytics? Your assistant would be so diligent and detailed that they wouldn’t miss a thing. Sound too good to be true? We’re giving you one. Say “Hello” to Analytics Intelligence.
Your new hardworking assistant, Analytics Intelligence, can’t replace you or a professional analyst. But, it can find key information for you and your professional analysts — so that your team can focus on making strategic decisions, instead of sifting through an endless sea of data.
Analytics Intelligence constantly monitors your website’s traffic. Anytime something significant happens, it adds an automatic alert in your Intelligence reports. If your bounce rate suddenly jumps on one of your referrals, Analytics Intelligence creates an alert. Of course, it’s up to you to go find out that the bounce rate jumped because someone inadvertently changed the landing page. But you might not have noticed that there was a problem that needed fixing if your trusty assistant hadn’t alerted you.

Behind Analytics Intelligence is a sophisticated algorithmic intelligence engine that detects any anomalies in your traffic patterns. That means it’s smart enough to know the difference between a change that’s actually part of a larger trend versus a change that you might need to look into. But, from a user perspective, Analytics Intelligence couldn’t be simpler.
Navigate to the Intelligence reports and you’ll see three reports — Daily Alerts, Weekly Alerts, Monthly Alerts. Daily Alerts contains all the alerts that are based on daily data. Weekly Alerts contains alerts based on weekly data. Monthly Alerts contains, you guessed it, alerts based on monthly data.
When you look at your alerts, you’ll notice that your trusty assistant has already gone through your historical data and posted alerts. This highlights a key feature of Analytics Intelligence: you don’t have to do anything — alerts automatically get posted to your account.
The best way to come up to speed on Analytics Intelligence is to take a look at the alerts that are being created for your data. You can learn everything you need to know about how to interpret your alerts in this 2-minute video.
You can also instruct your assistant to be on the lookout for specific things that you want to monitor. Let’s say you are running a billboard campaign in New York’s Times Square. You want to be proactively informed regarding how the campaign is impacting traffic from New York. To do this, go the Manage Intelligence Alerts page,

and set up a custom alert (see the example, below).

You might even want to set up a second alert that checks for decreasing New York traffic, so you can see if the campaign is starting to wind down.
You’ll then receive a custom alert, posted in your Daily Alerts, whenever one of these things happens. You can be notified by email as well, so you’ll know what’s going on even if you’re not checking your reports.
If you’re ever unsure about how to set up an alert, try starting with one of the templates on the Manage Intelligence Alerts page. Just click Copy, and then modify and rename the alert to fit your needs.
As with automatic alerts, the best way to learn about custom alerts is to try them out on your own data. You can also refer to the articles on Analytics Intelligence in the Google Analytics Help Center.
Sign in to your account to try it out. It’s time to meet your new assistant!
Introducing Google Closure Tools
Posted on : 19-11-2009 | By : JortK | In : google
0
Millions of Google users worldwide use JavaScript-intensive applications such as Gmail, Google Docs, and Google Maps. Like developers everywhere, Googlers want great web apps to be easier to create, so we’ve built many tools to help us develop these (and many other) apps. We’re happy to announce the open sourcing of these tools, and proud to make them available to the web development community.
Closure Compiler
Closure Compiler is a JavaScript optimizer that compiles web apps down into compact, high-performance JavaScript code. The compiler removes dead code, then rewrites and minimizes what’s left so that it will run fast on browsers’ JavaScript engines. The compiler also checks syntax, variable references, and types, and warns about other common JavaScript pitfalls. These checks and optimizations help you write apps that are less buggy and easier to maintain. You can use the compiler with Closure Inspector, a Firebug extension that makes debugging the obfuscated code almost as easy as debugging the human-readable source.
Because JavaScript developers are a diverse bunch, we’ve set up a number of ways to run the Closure Compiler. We’ve open-sourced a command-line tool. We’ve created a web application that accepts your code for compilation through a text box or a RESTful API. We are also offering a Firefox extension that you can use with Page Speed to conveniently see the performance benefits for your web pages.
Closure Library
Closure Library is a broad, well-tested, modular, and cross-browser JavaScript library. Web developers can pull just what they need from a wide set of reusable UI widgets and controls, as well as lower-level utilities for the DOM, server communication, animation, data structures, unit testing, rich-text editing, and much, much more. (Seriously. Check the docs.)
JavaScript lacks a standard class library like the STL or JDK. At Google, Closure Library serves as our “standard JavaScript library” for creating large, complex web applications. It’s purposely server-agnostic and intended for use with the Closure Compiler. You can make your project big and complex (with namespacing and type checking), yet small and fast over the wire (with compilation). The Closure Library provides clean utilities for common tasks so that you spend your time writing your app rather than writing utilities and browser abstractions.
Closure Templates
Closure Templates grew out of a desire for web templates that are precompiled to efficient JavaScript. Closure Templates have a simple syntax that is natural for programmers. Unlike traditional templating systems, you can think of Closure Templates as small components that you compose to form your user interface, instead of having to create one big template per page.
Closure Templates are implemented for both JavaScript and Java, so you can use the same templates both on the server and client side.
Closure Compiler, Closure Library, Closure Templates, and Closure Inspector all started as 20% projects and hundreds of Googlers have contributed thousands of patches. Today, each Closure Tool has grown to be a key part of the JavaScript infrastructure behind web apps at Google. That’s why we’re particularly excited (and humbled) to open source them to encourage and support web development outside Google. We want to hear what you think, but more importantly, we want to see what you make. So have at it and have fun!
From: Google Code Blog








