Les nouveautés et Tutoriels de Votre Codeur | SEO | Création de site web | Création de logiciel

Loading...

seo Introducing Google Browser Size 2013

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 Introducing the Google APIs Terms of Service and an update to Code Labs 2013

Seo Master present to you: Author PictureBy 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 A well earned retirement for the SOAP Search API 2013

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 Another Round of Deprecation Policies for Labs Graduates 2013

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.
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

seo Deprecation policies posted for 5 more APIs 2013

Seo Master present to you: We just posted updated terms of service for 5 more APIs to include transparent deprecation policies. This is part of their increased commitment as graduates of Google Code Labs. As we mentioned in March when we introduced Labs, each of these deprecation policies states that we'll support each version of the API for a guaranteed length of time from when it's deprecated or a newer version is introduced. While it's 3 years for most, it might be less for some. With this batch of updates, for example, the Checkout API has a policy of supporting old versions for 1 year while all of the others will support old versions for 3 years.

You can see the updated terms for all 5 APIs:

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

seo Introducing Labs for Google Code 2013

Seo Master present to you: Tom Stocky, Director, Google Developer Products

As Google's developer program continues to grow -- already over 60 APIs and tools on Google Code today -- we credit much of this growth to a culture of exploration and rapid iteration, and to the invaluable feedback and insights we receive from you about each product as it evolves.

Reflecting this culture, we're pleased to introduce Google Code Labs today as a home for developer products still in their early stages of development. Our hope, of course, is that all of our developer products grow up to be huge successes, but we realize that not every single one will reach that goal. The Labs program offers engineering teams at Google and the developer community a chance to explore ideas and get involved early.

With that background, we're also announcing that several of our best-known and most-used APIs and tools are among the first set of Google Code Labs "graduates" -- including App Engine, Google Web Toolkit, AJAX Search API, Maps API, Earth API, Calendar Data API, YouTube APIs, and more. See the full list of graduates on the Google Code Labs page.

For these graduates, we're increasing our commitment with published deprecation policies and other critical support services. The Visualization API terms, Contacts Data API terms, and Picasa Web Albums Data API terms include good examples of transparent deprecation policies. They state that we'll support each version for at least 3 years from when it's deprecated or a newer version is introduced. We're working to get policies posted for the other graduates as well, though the time period may vary a bit from product to product. It will be 3 years for most, but it might be less for some. The AdWords API, for example, has a policy of supporting old versions for 4 months.

Of course, even established products need a way to experiment with new features. With that in mind, some products will have features labeled "experimental" that could change (or even be removed) at any time, while the rest of the API is covered by a deprecation policy with long-term support.

There are additional hurdles for an API to graduate from Labs. They include requirements like having a dedicated, ongoing engineering team and comprehensive test suite. We also want to do things like the App Engine System Status Dashboard for more products.

Finally, we'd like to bid a fond adieu to one of our first developer products, the venerable SOAP Search API. It has been deprecated since 2006, when we stopped accepting new developers for the API, and it's finally hanging up the gloves and retiring on August 31st. It has been steadily declining in usage over the last couple years and we believe that the majority of use cases are sufficiently handled by the more comprehensive AJAX Search API (which supports not only web search, but local, news, images, video, and more). For those interested in migrating, there are more details in the AJAX APIs blog.

Thank you for making the past five-plus years such a success. We look forward to doing great things together with Google Code Labs and we hope you'll join us in congratulating the new graduates.2013, By: Seo Master
Powered by Blogger.
Design by Dev Nasser