MatrixAdapt | Logiciel de gestion d'Entreprise, Création et référencement des sites web

Seo Master present to you: When I started work at Google, I visited the Google Earth team, hoping to find a 20% project on my favorite Google product. There I met Bruno Bowden, who introduced me to a problem I had never thought much about: how to take browser sizes into account when designing a page.

Bruno had noticed that many people who visit the “Download Google Earth” page never actually download, even though, as you can see, the button is pretty hard to miss:



He wondered if a significant number of users might have their browser windows too small to see the button:



To analyze this, Bruno looked at how large people's browser windows were when they visited this page. His first key idea was to measure not the entire browser window, but just the client area -- no toolbars, status bars, or other chrome.

Bruno's second key idea was to render several weeks' worth of page visitor browser sizes in a contour visualization:



Using this visualization, Bruno confirmed that about 10% of users couldn't see the download button without scrolling, and thus never noticed it. 10% may not sound like a lot, but in this context it turns out to mean a significant number of people weren't downloading Google Earth. Using this data, the team was able to redesign the page to good effect.

Bruno and I realized that Web designers might benefit from this information if it could be made more generally available. We constructed a page that could overlay a DIV containing the contour visualization atop an IFRAME containing any other Web page:



This turned out to be a good way to see which controls were and weren't visible at typical browser sizes. The only problem was, the overlay DIV prevented mouse events from getting to the page IFRAME, so it wasn't possible to interact with the page.

To solve this, we split the overlay DIV into four:



Each of the outlines above (red, yellow, blue, green) represents a separate DIV. As the mouse pointer moves, we resize and reposition the DIVs to leave a small window of blank space around the pointer, and adjust background offsets for each DIV to make the overlay look like one seamless graphic. (We originally did this on a timer, but we found a simpler way: when the mouse touches any of the DIVs, resize/reposition all of the DIVs.) End result: a designer can click and otherwise interact with the page with the mouse, and thus interact with the site normally instead of repeatedly typing in URLs.

We are now making this tool available to the public on Google Labs. To try it, simply visit browsersize.googlelabs.com and enter the URL of a page you'd like to examine. The size overlay you see is using latest data from visitors to google.com, so this should give you a pretty good indication of what parts of your UI are generally visible and what aren't.

We look forward to receiving your comments at browser-size-external-feedback!

By Arthur Blume on behalf of the Google Browser Size team2013, By: Seo Master

Seo Master present to you: By Adam Feldman, APIs Product Manager

The Google APIs Terms of Service

Beginning today, most of our APIs use a single Terms of Service. We have rewritten these terms from the ground up with the goals of making them concise and easier to understand.Our intent is to simplify, not to make dramatic functional changes.

For all the APIs that share this single Terms of Service, you won’t need to study a whole new document, although some have brief specific Additional Terms.  In this rewrite, we have removed over 125,000 words from the combined previous terms, resulting in less to read and faster access to your favorite APIs.  Over time, other APIs will be migrated to the new terms.  Please review each API’s documentation to see its terms.

The new Terms of Service is another step in making Google APIs more technically consistent by sharing common infrastructure such as the Discovery service, the APIs Explorer, and the APIs Console.

Removing the Code Labs Label

In order to reduce confusion we're removing the Code Labs label from APIs on code.google.com. The Google Labs program has wound down. APIs formerly in Code Labs will now use the standard header in their documentation. The APIs themselves are unchanged.

Adam Feldman is a Product Manager, focusing on all of Google's APIs and making sure Google provides the best possible platform to developers.

Posted by Ashleigh Rentz, Editor Emerita

2013, By: Seo Master

Seo Master present to you: There’s a time for everything in life: a time for playing, learning & growing up; a time for maturing, working & performing, and a time for retiring, relaxing & handing the reigns over to the next generation. This is true for products too, and this is why, six months ago, we announced our Labs program for Google Code. This program provides clear distinction between graduate developer products where you’ll find mature products with transparent deprecation policies which you can count on for the long run, and labs developer products where you can explore our newest products and get started with them early.

As we also said in that announcement, the time has come for the SOAP Search API to retire – the new generation is around, has graduated, and has largely taken over already as a better and more versatile solution for the vast majority of use cases. In the spirit of our deprecation policies, we’ve continued to support the SOAP Search API since its deprecation in 2006, but we wanted to remind you that it is finally sunsetting. That had been planned for today, but we thought we'd give the few of you still using it another week to be prepared, so we'll be shutting it down on September 7th instead.

By Eric Tholomé, Director, Developer Products2013, By: Seo Master

Seo Master present to you: We recently published deprecation policies for a number of APIs that graduated from Google Code Labs. They state how long we'll support each version from when it's deprecated or a newer version is introduced. It will be 3 years for most, but the time period varies a bit from product to product.

• AdWords API terms
• AdSense API terms
• AJAX Feed API terms
• AJAX Language API terms
• AJAX Libraries API terms
• AJAX Search API terms
• Apps APIs terms
• Calendar Data API terms
• Chart API terms
• Health API terms
• Geo APIs terms (Earth API, Mapplets, Maps API, Maps API for Flash, and Static Maps API)
• Secure Data Connector terms

We still need to update the terms for a couple remaining graduates, but should have them all done within the next couple weeks.

By Neel Kshetramade, Google Developer Programs2013, By: Seo Master