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

Seo Master present to you: The Android intensity at Google I/O 2010 was definitely palpable. The Android presence included all of Day 2’s keynote along with a full session track, office hours, an Android device display of over 50 phones, and (many people’s favorite) the Developer Sandbox.

Vic Gundotra kicked off the Day 2 keynote with over 20 demos of the new features from Android release 2.2, internally called “Froyo” (see this summary on the Android Developers’ Blog). The second half of the keynote was devoted to Google TV. For more details on that announcement, you can read The Google TV Story.

During the conference, there were ten in-depth sessions dedicated to Android, two fireside chats (including one with OEMs), and one session that combined discussion of Android and iPhone issues. The sessions were:

  • A beginner’s guide to Android by Reto Meier - This one featured an amazingly packed, wall-to-wall, no-standing-room-left crowd, and once it became apparent that the crowd was already quite Android-savvy, the session turned into a Best and Worst Practices talk.

  • Writing real-time games for Android, redux by Chris Pruett - A crash course in Android game development: everything you need to know to get started writing 2D and 3D games, as well as tips, tricks, and benchmarks to help your code reach optimal performance. The crowd in this session’s room showed that games are one of the hottest Android application areas.

  • The world of ListView by Romain Guy and Adam Powell - It might seem a bit odd to dedicate an entire session to one UI widget, but Android’s ListView is large, reasonably complex, and very widely used. Romain and Adam had to work hard to fit their material into just one talk.

  • Casting a wide net: how to target all Android devices by Justin Mattson - This session covered an increasingly important subject now that there are over 60 Android devices, with significant variations in their size, shape, and capabilities.

  • Developing Android REST client applications by Virgil Dobjanschi - Virgil discussed the meat and potatoes of fitting Android clients into an increasingly-RESTful Web ecosystem. No user-interface flash here, but totally essential back-end plumbing guidance.

  • A JIT Compiler for Android's Dalvik VM by Ben Cheng and Bill Buzbee - JIT stands for “Just In Time”, and it’s a technique for making compute-heavy Android programs run faster; maybe as much as four times faster. Definitely behind-the-scenes stuff, but a subject nearly everyone cares about.

  • Writing zippy Android apps by Brad Fitzpatrick - Making your code run fast requires combining good design with a large grab-bag of hard-won best practices. For any serious Android developer: this is a must-see session, so I hope you make use of the session video and slides!

  • Advanced Android audio techniques by Dave Sparks - Integrating audio into your apps involves a lot of choices and trade-offs at a bunch of levels. Furthermore, there are new media framework APIs in Android 2.2. Lots of good, detailed drill-down in this session.

  • Building push applications for Android by Debajit Ghosh - What was called “push” while it was being built is now called Cloud To Device Messaging (C2DM), and it’s very nicely integrated into the SDK; we anticipate that a lot of developers will want to use this.

  • Android UI design patterns by Chris Nesladek et al. - The Android User Experience team shared their insights on how to design great Android apps.

There were also two Fireside chats. One with a panel of Android handset manufacturers, and another with a stage full of leading engineers from the Android team. The panelists took questions from the people in the room and from over the Web via Google Moderator and Google Wave.

On Thursday afternoon, a gaggle of Android engineers held office hours; the area was absolutely jam-packed with developers full of questions about everything from low-level hardware interfaces to telephony chips up through the finer points of Live Wallpapers. Everyone had fun and went home tired.

On both days of the conference, there was a large (bright green, of course) display case full of Android devices, surrounded by the app developers and handset manufacturers participating in the Developer Sandbox. This area was crowded from the start of I/O until the security folks eventually chased out the stragglers after closing. Here is quick video of a slow walk past the big display case.

Videos and slides for each session are linked from the titles above, and you can find all the Android session videos from Google I/O 2010 in this YouTube playlist.

The Android team had an amazing time meeting the developer community at this year’s I/O, and we hope you’ll stay up-to-date on Android news by following us on the Android Developers Blog!

2013, By: Seo Master
Seo Master present to you: There was a big focus on developing software for businesses at Google I/O this year, centered around three themes: build and sell apps in the Marketplace, customize and extend Google's apps, and build your own apps for internal use. The news kicked off the day before Google I/O with the announcement of Gmail contextual gadgets and many enhancements for Google Apps Script, including JDBC support. Then during the keynote, we launched Google App Engine for Business and announced our collaboration with VMware, and continued with the announcement of Google Wave (Labs) availability in Google Apps and Exchange support in Android 2.2 (aka Froyo).


Altogether there were more than a dozen technical sessions focused on the enterprise and more than 20 Google Apps Marketplace vendors demoing in the Enterprise Developer Sandbox.

Here’s a recap of a few of the sessions below. You can find the videos and slides for these sessions on the linked session title:


You can also find all videos for Enterprise I/O 2010 sessions in this YouTube playlist.

We’re excited to see the great strides our enterprise developer community has made, and we're looking forward to seeing even more innovation and progress at next year’s I/O. We hope to see you then!

Posted by Ryan Boyd, Google Apps team2013, By: Seo Master
salam every one, this is a topic from google web master centrale blog: Webmaster Level: All

In time for the holiday season, we now support rich snippets for shopping (e-commerce) sites! As many of you know, rich snippets are search results that have been enhanced using structured data from your web pages. Our new format shows price, availability, and product reviews on pages offering a product for sale. Here’s a result for [office lava lamp]:


As a webmaster, there are two ways that you can provide the information needed for product rich snippets to show up for your site, both described on the Product rich snippets help page:

Option 1: Provide a Merchant Center feed.

Many sites already provide Merchant Center feeds for use in Google Product Search, which means that most of the work needed for rich snippets is already done. For Google to make use of Merchant Center feeds for rich snippets, you should also use the rel=”canonical” link element on your product pages. By adding rel=”canonical” to your pages, Google can match the URLs in your feed to the pages found by our crawler.

Update on November 4, 2010: In order to have your product review information in your rich snippets, you can submit your product ratings directly in your feed, or you can work with one of our reviews partners to submit this information. If you work with a partner, your reviews information will appear in rich snippets, and shoppers on Google Product Search will be able to see your full-length reviews on relevant product pages, branded with your logo.

Option 2: Add markup to your site.

If prices for your products tend to change only infrequently, then adding markup is an alternative method to provide product data for rich snippets. We’ve updated our product markup format to allow a variety of different types of shopping sites to participate. In addition to the Google format, we support two other standards: the hProduct microformat and GoodRelations. You can use the rich snippets testing tool to test your markup and make sure it’s being parsed correctly.

This feature is currently available to merchants located in the US, but we will be rolling it out in more markets soon. Additionally, there are a number of rich snippets formats that can be used world-wide in various languages—make your snippets compelling and useful! Should you have any questions about the use of rich snippets, check out our FAQs and feel free to post in our Webmaster Help Forum.

Q&A

Which should I provide -- a Merchant Center feed or markup?

For most merchants, providing a Merchant Center feed is the best bet. That way your product prices and availability are updated quickly, and the data can be shown in rich snippets as well as in other applications like Google Shopping and Product Ads. If prices and availability change only infrequently, and you don’t want to set up a feed, then adding markup is also a valid option.

If I add markup to my site, will Google show product rich snippets for my pages?

We can’t guarantee that providing a feed or adding markup will result in rich snippets being shown. Note also that it may take a few weeks after providing data for rich snippets to be shown. If you mark up your pages, we encourage you to make sure that the data is parsed correctly by Google by using the rich snippets testing tool. The testing tool updates are rolling out over the next few days, so in this interim period the testing tool may not show previews for some types of markup.

I’ve already done reviews markup for my product offer pages. Should I add product/offer markup as well?

Yes, absolutely. Rich snippets are shown if the information provided accurately represents the main focus of the page. Therefore, for product pages you should add markup using the relevant offer/product fields which can include nested reviews.

this is a topic published in 2013... to get contents for your blog or your forum, just contact me at: devnasser@gmail.com
Powered by Blogger.