Google Updates the Dictionary OneBox

Google updated the interface of the Dictionary OneBox and added synonyms. They were already available if you clicked "more info" to see the entire list of definitions, but synonyms are useful enough to be displayed in the OneBox.


Another change is that the OneBox includes more definitions for each part of speech:


To trigger the Dictionary OneBox, search for [define word] or [word definition]. In some cases, Google shows the OneBox even if you don't include "define" or "definition". For example, if you search for [obnubilate], Google will show the definitions because it's likely that they're useful for many people.

{ Thanks, Bora and Venkat. }

Google+ Photos Replaces Picasa Web in the Navigation Bar

This is really weird. The "photos" link from Google's navigation bar no longer sends you to Picasa Web Albums if you're logged in. Google decided to send users to the Photos section from Google+ which shows photos from your circles, photos from your Android phone, photos you've been tagged in and your list of Picasa Web albums.





You can still go to Picasa Web Albums, but you have to bookmark the old URL or manually type it in the address bar. Google+ Photos lacks many of the features from Picasa Web Albums: Picnik integration, batch editing, entering an album description, ordering prints, creating album maps, moving photos to a different album and more. The interface is more user friendly, but it's not yet a full-fledged photo sharing app.

{ Thanks, Herin. }

Dart, Google's Programming Language for the Web

Google's alternative to JavaScript is not called Dash, the name has been changed to Dart. Designed as an object-oriented programming language that's both flexible and structured, Dart should be familiar to Java and C++ programmers, while inheriting some advantages of scripting languages like JavaScript.


Dart is "a class-based optionally typed programming language for building web applications" and Google says that it's better suited for large-scale projects. "Developed with the goals of simplicity, efficiency, and scalability, the Dart language combines powerful new language features with familiar language constructs into a clear, readable syntax."

Dart is flexible because it's both static and dynamic, it's both for clients and servers and it's useful for both small scripts and large projects. Dart apps are easier to debug, to maintain and to develop collaboratively. The language is optimized for performance and doesn't allow programmers to use features like defining constants that have to be computed at runtime.

For now, no browser supports Dart, but it's likely that Chrome will address this problem in the near future. The code can be executed "either on a native virtual machine or on top of a JavaScript engine by using a compiler that translates Dart code to JavaScript." Google already provides a simple online IDE called Dartboard that lets you edit a small program using your browser, but Dartboard will evolve into a full-fledged online IDE.

Last year, a Google employee admitted that it will be difficult to convince developers and browser vendors to adopt the new language, but the fact that it's easy to convert Dart code to JavaScript is an important advantage. Google will promote it "as the language for serious web development on the web platform" and will "actively push for its standardization and adoption across the board". After all, "the goal of the Dart effort is ultimately to replace JavaScript as the lingua franca of web development on the open web platform." It's hard to say whether it will succeed, but it's worth trying to fix JavaScript's flaws by starting from the scratch. Google will have standardize the language, build development tools and develop powerful apps that use Dart to make a better case.

{ Thanks, Venkat. }

Chrome Remote Desktop

Chrome Remote Desktop is a new Chrome extension that lets you remotely control a computer from your browser. It's the first software that uses a technology code-named "chromoting" and it's especially useful if you have a Chromebook.

The goal of this beta release is to demonstrate the core Chrome Remoting technology and get feedback from users. This version enables users to share with or get access to another computer by providing a one-time authentication code. Access is given only to the specific person the user identifies for one time only, and the sharing session is fully secured.

One potential use of this version is the remote IT helpdesk case. The helpdesk can use the Chrome Remote Desktop BETA to help another user, while conversely a user can receive help by setting up a sharing session without leaving their desk. Additional use cases such as being able to access your own computer remotely are coming soon.

Chrome Remote Desktop BETA is fully cross-platform, so you can connect any two computers that have a Chrome browser, including Windows, Linux, Mac and Chromebooks.

I've installed the extension on a Dell laptop that runs Windows 7 and on a Samsung Chromebook. The extension has more than 17 MB, so you have to wait a little bit until it's downloaded and installed. After installing the extension on my Dell laptop, I clicked the new icon from the new tab page and Chrome Remote Desktop asked me to "grant extended access permissions" to my computer.


Chrome Remote Desktop is a special extension because it can be used to control your computer. It's interesting that the extension uses Google Talk's technology to send messages.



When you decide to share your computer, Remote Desktop generates a code you need to enter on a second computer.


Here's what happens after installing the extension on my Chromebook:



The performance is pretty good, but it depends on your Internet connection and the computers you're using. The extension is especially useful for businesses and it will make Chromebooks even more attractive for companies.

{ Thanks, Venkat. }

Open Webcal Links Using Google Calendar in Chrome

If you visit Google Calendar using Chrome, you'll probably notice an infobar that asks you to "allow Google Calendar to open all web calendar links". Chrome has recently added support for protocol handlers, so that you can associate Gmail with mailto: links and Google Calendar with webcal: links. The infobar from Google Calendar requests your permission to associate the webcal: protocol with the application.


According to Wikipedia, "Webcal is an unofficial Uniform Resource Identifier scheme for accessing iCalendar files. Webcal was initiated for use with the Apple iCal application and has become a common de facto standard for accessing iCalendar formatted files via WebDAV. It is not an official URI scheme, such as http and ftp, as registered with IANA. The Webcal protocol prefix is used to trigger an external protocol handler which is passed the URL of the .ics file rather than being passed the downloaded contents of the file, in much the same way feed is sometimes used to trigger external RSS readers. The idea is that with this protocol prefix the target file should be subscribed to rather than imported into the calendar application as would happen with a simple download."

Here's an example of webcal: link that lets you subscribe to a calendar that includes the US holidays. You can find more calendars at iCalWorld and iCalShare.

To edit the protocol handlers in Google Chrome, open a new tab and paste in the address bar: chrome://settings/handlers (you can also go to Settings, click "Show advanced settings" at the bottom of the page, click "Content settings", then "Manage handlers").


Firefox also has this feature and it's even more powerful because it also works for filetypes. Unfortunately, you can only associate them with native apps, not with Web apps.

{ Thanks, Sterling. }

Transliteration Layer in Google Maps

Google Maps has a new layer that "switches between the labels in the local language and transliterated text". It's enabled by default, but you can disable it by mousing over the layer box and unchecking "English". Until now, both versions were displayed and the map looked cluttered.

Google Play Featured-Image Guidelines

By Natascha Bock, a Product Marketing Manager on the Google Play team

Localize your promotional graphics and videos new!

Google Play lets you provide different promotional graphics for each
language you support. Localizing your promotional graphics helps you reach your global user base more effectively. Read more below or go to the Developer Console Preview to get started.

If your app is selected for featuring on Google Play,our editorial team uses your 1024 x 500 “Featured Image” to promote the app on tablets, phones, and the Web. The image can be used on the home page on all versions of Google Play (Web, tablet and phone), on your product page in the Web and tablet versions, and on current and future top-level Google Play pages on phones.

Creating a Featured Image that will do a great job of highlighting your app requires special design consideration.

Not Really Optional

While many promotional assets are listed as “optional” for publishing in Google Play, we strongly recommend treating them as required. To start with, a Featured Image is required if your app is to be featured anywhere within Google Play. They’re a good idea anyhow; they enhance your product page, making your game or app more attractive to end-users (and more likely to be considered for featuring by our editorial team).

There’s nothing optional about the size, either; it has to be 1024 x 500 pixels.

Do’s and Dont’s

Your graphic is not an ad, it’s a teaser. It’s a place for bold, creative promotional images.

Vivid background colors work best. Black and white are problems because those are the backgrounds used by the mobile-device and Web versions of Google Play.

Limit Text to your app name and maybe a few additional descriptive words. Anything else will be unreadable on phones, anyhow.

Do: Make the graphic fun and enticing./td>	Don't: Create a text-heavy advertising-style graphic.
Do: Use colors that stand out on black or white backgrounds.	Don't: Let the graphic fade into the background.
Do: Promote your brand prominently.	Don't: Overload the graphic with details.
Do: Localize your image as needed for different languages.

Scaling

Your image has to be designed to scale; it will need to look good both in a full-size Web browser and on a little handset. You can rely on the aspect ratio being constant, but not the size. Here’s a tip: Try resizing your image down to 1 inch in width. If it still looks good and conveys your brand message, you have a winner.

On the Web:

On a tablet:

On a big phone:

On a small phone:

More Dont’s

• Device imagery is tempting, but becomes dated fast, and may be inappropriate if your user’s device looks entirely different.

• In-app screenshots are inappropriate because your product page already includes a place for these.

• Just using your app icon is a failure of imagination. You have more room; put it to good use!

Consider the Context

Given the size of the form factor, the phone is the most challenging channel for your image. Below we have both the “good” and “bad” sample images in that context:

Localize your Featured Image and other promotional assets

Android's user base is global. To help you reach all of these users effectively, Google Play lets you provide a separate featured image for each language that you support, as well as separate screenshots and promotional videos. You can add your localized images and videos in the Developer Console.

Localizing your featured image is highly recommended as a powerful way to get your message across to users around the world. It goes hand-in-hand with localizing your app's description and other details and it's built-in string resources.

Don’t Forget

A 1024 x 500 Featured Image is required for feature placement consideration. Don't miss out on the opportunity!