In December of 2016, Google launched the Actions on Google developer platform for Google Assistant. (It announced it during the Google Pixel phone launch event, but it wasn't accessible right away.) The platform allows third-party developers to create conversational reply-based actions on Google Assistant. We've seen lots take advantage of the platform, and today, the search giant announced that it is gaining support for seven new languages and better Android application integration.
When Google launched the Actions on Google developer platform, it was fairly barebones. However, over time, the company has expanded its capabilities, allowing people to make payments, adding a British English accent option, and bringing the developer platform to other countries such as Australia. Google even announced a developer challenge for a chance to win $10,000 and a free ticket to Google I/O.
Today, the platform gains support for a total of 16 languages with the addition of the aforementioned seven new ones:
- Hindi
- Thai
- Indonesian
- Danish
- Norwegian
- Swedish
- Dutch
Google also wants to help make it easier for developers to build actions for a global audience, so it's adding support for templates. They currently support French, German, and Japanese, and they allow you to create an Action by filling in a Google Sheet. There's not a single line of code required.
Google's also allowing developers to deep link from their Actions in the Google Assistant to specific intents in Android applications, and to integrate with the Google Places API via a new askForPlace conversation helper. This allows developers to tap the Google Assistant with location-based user queries, which really shines in restaurant recommendation and delivery apps. (A pizza delivery app, for example, will know a user's rough location before they place an order.)
The changes and new features roll out today. If you're wondering where to start, check the source link for a list of handy resources.
Source: Google Developers Blog
from xda-developers http://ift.tt/2GL0pjz
via IFTTT
No comments:
Post a Comment